Data migration route
Time59 data to Microsoft SQL Server
Time59 is a cloud accounting and billing system, and Microsoft SQL Server is a database on a server the firm runs. This is not a move to a new working system: the route writes out what Time59 holds and keeps it readable and open to queries.
Time59Cloud- Matters: Exported in full
- Contacts: Exported in full
- Time and expenses: Exported in full
- Billing: Exported in full
- Trust money: Exported in full
- Templates: Exported with mapping
- Notes: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
Microsoft SQL ServerServer- 5 carried
- 1 mapped
- 2 to confirm
What moves
What moves from Time59 to Microsoft SQL Server
Each row is a kind of record Time59 holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route five kinds of record carry across, one kind needs mapping and two kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partNo matter record as such: a client, optionally split into projects, stands in for one. | Has a placeA table of matters linked to clients, parties and fee earners. | Exported in full |
| ContactsClients, other parties and referrers | Held in partClients only, with billing details and an optional client group code. | Has a placePeople and companies, with their roles on each matter. | Exported in full |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeRows of text linked to matters and contacts. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime and expense records by timekeeper code, with UTBMS codes available. | Has a placeTime and expense rows with rates and billed status. | Exported in full |
| BillingInvoices, payments and debtor balances | HeldInvoices, payments, interest profiles, fixed fee projects and LEDES output. | Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files. | Exported in full |
| Trust moneyTrust or client account ledgers and balances | HeldClient trust balances, with evergreen replenishment settings. | Has a placeTransactions and balances for look-up; it is not a trust accounting system. | Exported in full |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeAs added columns, or a table of field names and values. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | Held in partInvoice formats and footers only. | Has a place in partPrecedent files can be stored; automation does not run here. | Exported with mapping |
What the plans mean
- Exported in full
- Microsoft SQL Server has a place for this kind of record. It is loaded there and checked against Time59.
- Exported with mapping
- Microsoft SQL Server 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.
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
Not a new system. A complete copy the firm can query.
Writing Time59 out to Microsoft SQL Server is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.
What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Time59 as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.
Time59 is hosted by its maker and Microsoft SQL Server sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What Time59 will release depends on its export tools, and that is confirmed in the analysis.
Where the data is now
Leaving Time59
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in Microsoft SQL Server
There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.
Restored copy or rebuilt schema
Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.
No screens come with it
A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.
Documents sit beside the database
Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.
The edition follows the size
A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.
Backups and a test restore
An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.
How NewLaw runs it
Four steps, in this order.
This route produces an archive, not a working system, so the steps are about completeness and proof.
Analysis
We read what Time59 holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything Time59 holds is in scope unless you take it out.
Clean-up, if you want it
An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.
Trial export
The data is written to Microsoft SQL Server as a trial and checked against Time59: record counts, totals where Time59 holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.
Final export
After the last day of work in Time59, the export is run a final time and checked again. There is nothing to go live. Time59 is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.
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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what Time59 holds
What is in it, how its records link, and where each piece would sit in Microsoft SQL Server. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- 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
Microsoft SQL Server is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.
Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.
What is agreed and set up
- Server, instance and edition agreed with the IT provider
- Read-only logins and roles for named staff
- Views for matter, ledger, time and document look-ups
- Backup schedule and who tests a restore
- Plain names and descriptions for tables and columns
- Excel or Power BI connected for reporting
Questions
Time59 to Microsoft SQL Server: 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.
Does the copy in Microsoft SQL Server hold trust ledgers from Time59?
Yes. Transactions and balances for look-up; it is not a trust accounting system. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in Time59 as at the export date.
Does everything in Time59 have a place in Microsoft SQL Server?
Most of it does on paper. Notes and custom fields could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Microsoft SQL Server is kept as a readable archive, and you see which before the move.
What has to be decided before Time59 is written out to Microsoft SQL Server?
Templates are exported with mapping, so each mapping is agreed with you first. Notes and custom fields are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.
Other routes
Other routes from Time59 and into Microsoft SQL Server
Other destinations from Time59
Other systems that move into Microsoft SQL Server
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
Time59 and Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.
Moving from Time59 to Microsoft SQL Server?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.