Data migration route
Firm Central data to Microsoft SQL Server
Firm Central is a cloud practice management 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 Firm Central holds and keeps it readable and open to queries.
Firm CentralCloud- Matters: Exported in full
- Contacts: Exported in full
- Notes: Exported in full
- Calendar: Exported in full
- Tasks: Exported in full
- Time and expenses: Exported in full
- Billing: Exported in full
- Trust money: Exported in full
- Firm accounts: Exported in full
- Documents: Exported with mapping
- Emails: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
- Intake: Confirmed in the analysis
Microsoft SQL ServerServer- 9 carried
- 1 mapped
- 4 to confirm
What moves
What moves from Firm Central to Microsoft SQL Server
Each row is a kind of record Firm Central holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route nine kinds of record carry across, one kind needs mapping and four kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldOpen and closed matters with practice area, client group, permissions and primary attorney. | Has a placeA table of matters linked to clients, parties and fee earners. | Exported in full |
| ContactsClients, other parties and referrers | HeldClients, contacts and client groups. | Has a placePeople and companies, with their roles on each matter. | Exported in full |
| DocumentsFiles stored in or linked from the system | HeldMatter folders that could be layered freely, plus a My Documents area for each user. | Has a place in partAs files in folders with an index table; storing files in the database is possible. | Exported with mapping |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partAs message files with an index table, or as rows of header fields. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | HeldMatter notes. | Has a placeRows of text linked to matters and contacts. | Exported in full |
| CalendarAppointments, court dates and deadlines | HeldCalendar events, and Deadline Assistant events for firms that had that add-on. | Has a placeRows of appointments and key dates; nothing displays them as a calendar. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | HeldMatter tasks. | Has a placeRows with assignee, due date and status. | Exported in full |
| Time and expensesTime and expense entries, billed and unbilled | Held in partThrough the Time & Billing module, which was supplied by eBillity. | Has a placeTime and expense rows with rates and billed status. | Exported in full |
| BillingInvoices, payments and debtor balances | Held in partPre-bills, invoices and payments in the Time & Billing module. | Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files. | Exported in full |
| Trust moneyTrust or client account ledgers and balances | Held in partThe Time & Billing module had a Trusts & Retainers tab. | Has a placeTransactions and balances for look-up; it is not a trust accounting system. | Exported in full |
| Firm accountsGeneral ledger, office account and payables | Held in partEditions sold with Accounting had a chart of accounts and accounts payable. | Has a placeGeneral ledger journals and balances, where the source held them. | 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 | To be confirmed | Has a place in partPrecedent files can be stored; automation does not run here. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a placeEnquiry rows, where the source recorded them. | Confirmed in the analysis |
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 Firm Central.
- 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 Firm Central 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 Firm Central 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.
Firm Central 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 Firm Central will release depends on its export tools, and that is confirmed in the analysis.
Where the data is now
Leaving Firm Central
Firm Central was discontinued in 2024, so a move from it today starts with whatever the firm saved before the shutdown. Thomson Reuters’ extraction guide had firms download their data as a set of CSV files and zipped document bundles. The job is to find those files, work out what each contains, and rebuild matters from the pieces in a system the firm now uses.
The source is an export
What survives is a collection of downloads: contact and matter lists, document bundles and calendar files, saved by whoever ran the export in 2024. They may sit on one person’s computer. The analysis begins with an inventory of those files, including their dates, since an export taken weeks before the shutdown misses later work.
One file per kind of record
Matter lists, matter notes, matter tasks, billing rates, permissions and primary attorneys were each exported as their own CSV, and separately for open and closed matters. Each file is a flat list. The pieces are joined back together on the matter and client they name, and rows that match nothing are listed for the firm.
Documents came out as zips
Bulk document extraction produced zipped bundles holding each matter’s folders, with files in the format they were uploaded in. Firm Central allowed folders to be layered freely, so structures vary from matter to matter. Each user’s My Documents came out as a separate set and has no matter attached until someone assigns one.
Billing sat with eBillity
Time entries, invoices, payments and trust records were in the Time & Billing module, which eBillity supplied. Thomson Reuters told firms they could carry on with those eBillity products under a new billing arrangement. A firm that did so has its billing history in eBillity, not in the Firm Central export.
What the export left out
The guide notes that client portal messages could not be exported, and that links to Westlaw research saved in matter folders do not include the documents themselves. Neither can be recovered from the files. If either mattered to a particular matter, the firm’s email and Westlaw folders are the places to look.
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 Firm Central holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything Firm Central 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 Firm Central: record counts, totals where Firm Central 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 Firm Central, the export is run a final time and checked again. There is nothing to go live. Firm Central 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 Firm Central 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 Firm Central 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
Firm Central to Microsoft SQL Server: what firms ask
Firm Central has shut down. Is it too late to move our data?
Not if the firm ran the exports. Thomson Reuters gave firms a way to download contacts, matters, notes, tasks, calendar events and documents before the product ended. Those files can be cleaned and loaded into a current system. If no export was taken, what remains is whatever was also saved elsewhere.
We exported everything in 2024 but never loaded it anywhere. What can be done with it?
Quite a lot. The CSV files are joined back into matters with their contacts, notes and tasks, and the document bundles are unzipped and filed against the right matter. Before anything is made final, the firm sees a trial load and a list of whatever could not be matched.
Where did our time and billing records go?
They were never in the main Firm Central database. Time & Billing was an eBillity product offered through Thomson Reuters. Firms that kept it moved to a direct arrangement with eBillity. Those that did not would have downloaded invoices and reports before the end, and those downloads are the record.
Does the copy in Microsoft SQL Server hold trust ledgers from Firm Central?
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 Firm Central as at the export date.
Does everything in Firm Central have a place in Microsoft SQL Server?
Most of it does on paper. Emails, custom fields, templates and intake records 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 Firm Central is written out to Microsoft SQL Server?
Documents are exported with mapping, so each mapping is agreed with you first. Emails, custom fields, templates and intake records 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 Firm Central and into Microsoft SQL Server
Other destinations from Firm Central
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.
Firm Central and Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.
Moving from Firm Central 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.