Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

Time59 to SharePoint migration

Time59 is a cloud accounting and billing system, and SharePoint is cloud file storage. What moves is the files, plus a readable export of everything else the old system holds.

FromTime59Cloud
  1. Matters: Carried with mapping
  2. Contacts: Carried with mapping
  3. Templates: Carried with mapping
  4. Notes: Confirmed in the analysis
  5. Custom fields: Confirmed in the analysis
ToSharePointCloud
  1. Time and expenses: Kept as a readable archive
  2. Billing: Kept as a readable archive
  3. Trust money: Kept as a readable archive
Readable archiveNo place in SharePoint
  • 3 mapped
  • 2 to confirm
  • 3 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Time59 to SharePoint

Each row is a kind of record Time59 holds, whether SharePoint has a place for it, and what is planned. On this route three kinds need mapping, three kinds have no place in SharePoint and are archived and two kinds are confirmed in the analysis.

Records in Time59 and their place in SharePoint
RecordIn Time59In SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partNo matter record as such: a client, optionally split into projects, stands in for one.Has a place in partAs a site, library, folder or list row the firm designs; no built-in matter record.Carried with mapping
ContactsClients, other parties and referrersHeld in partClients only, with billing details and an optional client group code.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a place in partAs documents, or as rows in a notes list if one is built.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTime and expense records by timekeeper code, with UTBMS codes available.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldInvoices, payments, interest profiles, fixed fee projects and LEDES output.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldClient trust balances, with evergreen replenishment settings.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeColumns and content types on libraries and lists.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partInvoice formats and footers only.Has a place in partPrecedents as files; templates can be offered from a library.Carried with mapping

What the plans mean

Carried with mapping
SharePoint holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
Confirmed in the analysis
We could not confirm this from the two products’ own material, so it is checked against your data before the plan is fixed.
Kept as a readable archive
SharePoint has no place for it. It is exported in a format that opens without Time59 and handed to the firm as a read-only archive.

The table states what the two products hold and what NewLaw plans for. It is not a promise that every record moves: that is settled against your own data in the analysis.

This kind of move

An export the firm can open without the system.

SharePoint holds files, and most of what Time59 holds is records. This route is therefore an export job. Each kind of record is written out in a format that opens without the system it came from: lists as spreadsheets, statements and invoices as PDFs, attachments as the files they were. The export is laid out in folders that make sense to someone who never used Time59, by client or by year, with a short index file saying what is where.

Firms do this when a subscription is ending, when a system is being retired, or to meet a retention rule. The test of the result is whether a question can still be answered from it years later: what was this client invoiced, who signed this agreement and when. So the trial export is checked by asking those questions of it. Totals are agreed to the system’s own reports, and access to the folder in SharePoint is limited before the export is copied in.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Time59 depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to Time59 is kept running until the checks on SharePoint are finished.

Where the data is now

A Time59 account holds a small, tidy set of records: clients, projects, timekeepers, time, expenses, invoices, payments and trust. There are no documents or calendars to worry about. The thinking goes into structure. Time59 has clients and projects where the next system will have clients and matters, and the two do not line up one to one.

  1. Is each client a matter?

    Many firms use the two name lines on a client record for the client and the matter, so that John Smith has one Time59 client for his divorce and another for his will. Others put matters in projects. The firm’s habit is confirmed first, and Time59 clients are then merged into real clients with matters beneath.

  2. One login for everyone

    The whole firm signs in with a single shared username, so there are no individual user records to map across. Who did the work is recorded by timekeeper code on each time entry. Each code is matched to a named user in the new system, including the codes of people who have since left the firm.

  3. Beginning balances

    Time59 does not import billing data from other software, so a firm that came to it from another system started each client with a beginning balance. That figure has no invoices behind it. Clients still carrying a beginning balance are listed, and the firm decides how the amount is described in the new system.

  4. Projects set the rate

    Hourly rates and fixed fees are set through projects under a client, and fixed fee projects can recur up to a limit. In the destination those become rate arrangements or fee schedules on a matter. Recurring fixed fees are identified one by one, since a missed one means a client is not billed next month.

  5. Evergreen trust settings

    Each client can have a trust replenishment trigger, a minimum required balance and wording that appears on the invoice. The balances move as opening trust balances. Trigger amounts are settings, and they are re-entered in the new system for the clients who rely on them, checked against the Time59 list.

More about moving off Time59

Where it is going

SharePoint will take a firm’s documents in almost any arrangement, which is the difficulty. The structure has to be chosen before the load: what a client is, what a matter is, and where security is applied. Changing it afterwards means moving every file again. Most of the effort goes into that design and into the columns that describe each document.

  1. Site, library or folder per matter

    A matter can be a site, a library within a client site, or a folder in one large library. Each choice has consequences for permissions, for search and for how a new matter is opened. The firm makes that decision, and the people who open matters every day should be part of it.

  2. Columns are built before content

    If documents are to carry matter number, client, document type or author as columns, those columns and any content types exist before loading, so each file can be tagged as it arrives. Tagging hundreds of thousands of documents afterwards is a second project that seldom gets finished.

  3. The 400 character path

    SharePoint limits the full decoded path, site and library and folders and file name, to 400 characters. A deep tree copied from a server drive under a long site name can cross it. Path lengths are calculated against the planned structure, not the old one, before any file moves.

  4. Large libraries and the view threshold

    A library can hold millions of files, but a view that tries to show more than 5,000 items at once runs into the list view threshold. One flat library with a folder per matter needs indexed columns and filtered views from the start, or views begin to fail as the library fills.

  5. Security by library, not by file

    Microsoft supports up to 50,000 unique permissions in a library and recommends staying under 5,000. Restricting matters one folder at a time reaches that sooner than firms expect. Restricted work is better grouped into its own site or library, so the permission is set once.

More about moving into SharePoint

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in SharePoint on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what Time59 holds and how it is organised, then agree with you where each kind of record will sit in SharePoint. Anything with no place there stays behind or is archived, and you see which before the move.

  2. Clean-up

    Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.

  3. Trial load

    A trial is loaded into SharePoint and checked against Time59: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in Time59, a final pass over a weekend picks up what changed since the trial. Time59 is kept read only as the fall-back record.

Fixed price, agreed after the analysis. How NewLaw moves legal data

Start

Start this migration

Tell us what is in Time59 and roughly how much of it. The first step is the analysis, and the price is fixed once it is done.

Step 1 of 5

Step 1 of 5: Start with the route

Moving fromTime59
Moving toSharePoint

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what Time59 holds

    What is in it, how its records link, and where each piece would sit in SharePoint. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  3. A fixed price in writing

    Set after the analysis, so it reflects what is in your data. You have it before any work starts.

Beyond the data

Structure, permissions and handover

SharePoint is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.

Making SharePoint work as a firm’s document store is a design and build job in its own right. The sites, libraries, columns and permission groups are created, a way of opening a new matter is put in place so the structure repeats itself, and the Outlook and Teams habits around it are agreed. Search is tested with real questions from fee earners.

What is agreed and set up

  • Site and library structure for clients and matters
  • Columns and content types for matter number and document type
  • Permission groups, with restricted matters in their own libraries
  • A repeatable way to create each new matter’s workspace
  • Version history limits and retention labels for closed matters
  • Views, indexed columns and search tested on loaded data

Questions

Time59 to SharePoint: what firms ask

How does data come out of Time59?

The vendor describes a Microsoft Excel export for downloading data from the account. Invoices can also be downloaded as PDFs. Between the two, the clients, time, expenses, invoices and payments can be reassembled. What the export contains for trust transactions is checked in the analysis before a destination is mapped.

Time59 gave us no matter numbers. What do we do about that?

It becomes a decision, not an obstacle. A new system will usually want a number on each matter. Numbers are generated during the trial load in whatever format the firm prefers, and the Time59 client name is kept on the matter so staff can still find things the way they used to.

Our case files are on paper and in Outlook. What moves?

From Time59, only the billing side: who the clients are, what was billed, what is owed and what is held in trust. The rest was never in it. If the firm wants documents and emails in the new system too, those are gathered from folders and mailboxes as a separate piece of work.

Do trust balances in Time59 have a place in SharePoint?

No. SharePoint does not keep trust ledgers. Trust records from Time59 are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.

What happens to records SharePoint has no place for?

On this route that is time entries, billing records and trust ledgers. They are exported from Time59 in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.

What has to be decided before Time59 data is loaded into SharePoint?

Matters, contacts and templates are carried with mapping, so each mapping is agreed with you first. Notes and custom fields are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.

Where to start

Before and after the move.

Choosing the system comes before a migration. Setting it up and putting AI to work come after.

How we do itDiscovery to rollout, step by step

Time59 and SharePoint are the names and marks of their owners, used here only to identify the two systems.

Moving from Time59 to SharePoint?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.