Data migration route
Lawmatics to SimpleLaw migration
Lawmatics is a cloud CRM and intake system, and SimpleLaw is a cloud practice management system. Contacts and intake history move, and the matters themselves start life in SimpleLaw.
LawmaticsCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Intake: Carried across
- Billing: Carried with mapping
- Trust money: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
SimpleLawCloud- 8 carried
- 4 mapped
- 1 to confirm
What moves
What moves from Lawmatics to SimpleLaw
Each row is a kind of record Lawmatics holds, whether SimpleLaw has a place for it, and what is planned. On this route eight kinds of record carry across, four kinds need mapping and one kind is confirmed in the analysis.
| 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 place | Carried across |
| ContactsClients, other parties and referrers | HeldContacts and companies; other parties link to a matter as relationships. | Has a placeAs leads, clients or other contacts in the CRM. | Carried across |
| 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 placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partMail sync logs emails with known contacts on the matter timeline. | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | Held | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | HeldAppointments with event types, synced with Google, Outlook or iCloud calendars. | Has a place | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTasks with custom statuses and tags. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | Held in partTime entries and expenses, in the Time & Billing module. | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | Held in partInvoices and payments, in the Time & Billing module. | Has a place in partInvoices are created in the product; loading invoice history is confirmed in the analysis. | Carried with mapping |
| 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 place in partTrust balances are supported; history depth is confirmed in the analysis. | Carried with mapping |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields on matters, contacts and companies. | Has a place | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument templates, email templates, custom forms and automations. | Has a place in partTemplates are rebuilt using SimpleLaw’s own automation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldPipelines, custom forms, booking links, marketing sources and campaigns. | Has a placeLeads and intake forms. | Carried across |
What the plans mean
- Carried across
- SimpleLaw has a place for this kind of record. It is loaded there and checked against Lawmatics.
- Carried with mapping
- SimpleLaw 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
Contacts and enquiries move. Matters begin in the new system.
A CRM knows people: who enquired, who referred them, what was sent and when. It does not know matters the way a practice system does. So the move from Lawmatics to SimpleLaw is mostly a contacts job, and contacts are where duplicates live. The same person appears as a lead, a client and a referrer, sometimes under three email addresses. They are merged before extraction where they can be identified, because SimpleLaw will invoice and receipt against these records.
Pipelines, campaigns and automations seldom have a direct equivalent in a practice system. Open enquiries can be loaded as contacts with a note of their stage, or opened as matters if the firm wants them worked from the first day. Intake forms and email sequences are set up again in whatever SimpleLaw or its intake tool provides. Past correspondence is kept as notes or documents on the contact, so the history of a relationship can still be read.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Lawmatics 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 Lawmatics is kept running until the checks on SimpleLaw are finished.
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 SimpleLaw
Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.
Lead, client or contact
A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.
Billing type on each matter
Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.
Storage chosen before loading
If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.
Custom fields named for templates
Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.
Portal access client by client
The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.
How NewLaw runs it
Four steps, in this order.
Trust money moves on this route, so the trust cutover gets a rehearsal of its own.
Analysis
We read what Lawmatics holds and how its records link, then agree with you, field by field, where each piece will sit in SimpleLaw. Anything with no place there comes across as a note or stays behind, and you see which before the move.
Clean-up
Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Lawmatics, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into SimpleLaw as a trial and checked against Lawmatics: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Lawmatics are frozen for an agreed window, the data is collected a final time and SimpleLaw goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. Lawmatics 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 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 SimpleLaw. 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
Setting up SimpleLaw
Loaded data is not yet a working system. This is what NewLaw sets up in SimpleLaw, beyond the migration, so that people can work in it from the first day.
The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.
Set-up decisions in SimpleLaw
- Labels for documents, activities, expenses and contact IDs
- Custom fields and intake forms for each practice area
- Document templates and the attorney-client agreement
- Workflows for case types that follow a standard process
- User permission sets and client portal visibility
- QuickBooks connection and the online payment processor
Questions
Lawmatics to SimpleLaw: 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.
Do trust balances in Lawmatics have a place in SimpleLaw?
In part. Trust balances are supported; history depth is confirmed in the analysis. The analysis sets out which trust records have a place in SimpleLaw and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.
Does everything in Lawmatics have a place in SimpleLaw?
Most of it does on paper. Emails 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 SimpleLaw is kept as a readable archive, and you see which before the move.
What has to be decided before Lawmatics data is loaded into SimpleLaw?
Billing records, trust ledgers, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from Lawmatics and into SimpleLaw
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 SimpleLaw are the names and marks of their owners, used here only to identify the two systems.
Moving from Lawmatics to SimpleLaw?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.