Data migration route
Lawmatics data to Microsoft SQL Server
Lawmatics is a cloud CRM and intake 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 Lawmatics holds and keeps it readable and open to queries.
LawmaticsCloud- 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
- Intake: Exported in full
- Documents: Exported with mapping
- Emails: Exported with mapping
- Custom fields: Exported with mapping
- Templates: Exported with mapping
Microsoft SQL ServerServer- 9 carried
- 4 mapped
What moves
What moves from Lawmatics to Microsoft SQL Server
Each row is a kind of record Lawmatics holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route nine kinds of record carry across and four kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldA matter is a lead, a client or a lost enquiry, with a status of PNC, Hired or Lost. | Has a placeA table of matters linked to clients, parties and fee earners. | Exported in full |
| ContactsClients, other parties and referrers | HeldContacts and companies; other parties link to a matter as relationships. | Has a placePeople and companies, with their roles on each matter. | Exported in full |
| DocumentsFiles stored in or linked from the system | Held in partA Files tab with folders on each matter. Files download one matter at a time. | 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 | Held in partMail sync logs emails with known contacts on the matter timeline. | Has a place in partAs message files with an index table, or as rows of header fields. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | Held | Has a placeRows of text linked to matters and contacts. | Exported in full |
| CalendarAppointments, court dates and deadlines | HeldAppointments with event types, synced with Google, Outlook or iCloud calendars. | 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 | HeldTasks with custom statuses and tags. | Has a placeRows with assignee, due date and status. | Exported in full |
| Time and expensesTime and expense entries, billed and unbilled | Held in partTime entries and expenses, in the Time & Billing module. | Has a placeTime and expense rows with rates and billed status. | Exported in full |
| BillingInvoices, payments and debtor balances | Held in partInvoices 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 partA trust account with a running balance per matter, in the Time & Billing module. | 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 | HeldCustom fields on matters, contacts and companies. | Has a placeAs added columns, or a table of field names and values. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument templates, email templates, custom forms and automations. | Has a place in partPrecedent files can be stored; automation does not run here. | Exported with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldPipelines, custom forms, booking links, marketing sources and campaigns. | Has a placeEnquiry rows, where the source recorded them. | Exported in full |
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 Lawmatics.
- 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.
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 Lawmatics 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 Lawmatics 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.
Lawmatics 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 Lawmatics will release depends on its export tools, and that is confirmed in the analysis.
Where the data is now
Leaving Lawmatics
Lawmatics will export matters, contacts and companies as CSV files with every field, custom fields included. Files are different: they cannot be exported for all matters at once. So a move off it runs in two streams, a quick one for the structured records and a slower one that collects each matter’s files, notes and timeline.
Three statuses, one record type
Leads, clients and lost enquiries are all matters, told apart by a status of PNC, Hired or Lost and any sub-statuses the firm added. A practice system usually wants only the hired ones as matters. The others go to its intake side if it has one, or are kept as contacts with a note of the enquiry.
Files come out matter by matter
The bulk export covers records and fields. Files saved on matters, the vendor’s help centre says plainly, cannot be exported for all matters at once in the app, only downloaded matter by matter. The API also exposes files and folders, which is the other route for any real volume. Either way the result is checked against a count for each matter.
Relationships are separate contacts
A spouse, a co-defendant or a referring lawyer is linked to a matter through a relationship type the firm defined, and each is a full contact in the CRM. Those links are exported with the matter and mapped to the destination’s party roles. Where a role has no equivalent, the firm chooses the nearest one.
Often already synced elsewhere
Plenty of firms have Lawmatics pushing hired matters into Clio Manage or another practice system. That sync runs mostly one way, and notes, files or fields added in Lawmatics afterwards cross only when someone presses Sync again. Before a move the two systems are compared, so the later additions are not lost.
Automations and forms
Intake forms, email campaigns and automations do the daily work in this product, and none of them export as something another system can run. Each live automation is documented with its trigger and steps. Forms embedded in the firm’s website are replaced at cutover so enquiries stop arriving in the old account.
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 Lawmatics holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything Lawmatics 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 Lawmatics: record counts, totals where Lawmatics 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 Lawmatics, the export is run a final time and checked again. There is nothing to go live. Lawmatics 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 Lawmatics 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 Lawmatics 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
Lawmatics to Microsoft SQL Server: what firms ask
Can we move from Lawmatics into a full practice management system?
Yes. Hired matters and their contacts map naturally onto clients and matters, and the custom fields come out in the same export. What needs thought is the enquiries that never became clients. A destination with an intake module can take them as leads. Otherwise they are kept as contacts, or left in the export file.
Do the files on each matter come with it?
They do, but not through the bulk export, which covers records only. Files are downloaded per matter or pulled through the API with their folder names. Signed engagement documents and completed intake forms are saved to the Files tab automatically, so those are included. The trial load compares file counts matter by matter.
What happens to our trust balances in Lawmatics?
The trust account table exports to CSV as filtered on screen, showing deposits, payments and a running balance. Balances per matter are rebuilt in the destination from that table and agreed to the bank statement before cutover. The trust cutover is rehearsed on a full trial load first, because it cannot simply be run again.
Does the copy in Microsoft SQL Server hold trust ledgers from Lawmatics?
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 Lawmatics as at the export date.
Does everything in Lawmatics have a place in Microsoft SQL Server?
On paper, yes: each kind of record Lawmatics holds has a place in Microsoft SQL Server. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.
What has to be decided before Lawmatics is written out to Microsoft SQL Server?
Documents, emails, custom fields and templates are exported with mapping, so each mapping is agreed with you first. The firm also decides who may open the archive and how long it is kept.
Other routes
Other routes from Lawmatics and 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.
Lawmatics and Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.
Moving from Lawmatics 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.