Data migration route
LeanLaw to Lawmatics migration
LeanLaw is a cloud accounting and billing system, and Lawmatics is a cloud CRM and intake system. Lawmatics is built around people and enquiries, so the contact list leads this move, and the table shows what else has a place.
LeanLawCloud- Matters: Carried across
- Contacts: Carried across
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Trust money: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Intake: Confirmed in the analysis
LawmaticsCloud- 2 carried
- 4 mapped
- 4 to confirm
What moves
What moves from LeanLaw to Lawmatics
Each row is a kind of record LeanLaw holds, whether Lawmatics has a place for it, and what is planned. On this route two kinds of record carry across, four kinds need mapping and four kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldClients and matters as billing records, with budgets, rates and fee arrangements. | Has a placeLoaded from CSV with a status of PNC, Hired or Lost and a pipeline stage. | Carried across |
| ContactsClients, other parties and referrers | Held in partClients and billing contacts only. | Has a placeContacts and companies load from CSV; relationships link further parties to a matter. | Carried across |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeNotes on matters, contacts and companies. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a place | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime and expenses tied to client and matter. | Has a place in partTime entries and expenses, where the Time & Billing module is enabled. | Carried with mapping |
| BillingInvoices, payments and debtor balances | HeldHourly, flat fee and recurring fixed fees; LEDES on some plans. | Has a place in partInvoices and payments; a past invoice is entered as sent, then marked paid. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | HeldClient and matter trust ledgers, with the trust bank account kept in QuickBooks Online. | Has a place in partA trust account with a running balance; deposits are allocated to a contact and matter. | Carried with mapping |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeMatter, contact and company fields. A field must exist before data is imported into it. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | Held in partInvoice templates. | Has a place in partDocument and email templates are rebuilt with Lawmatics merge fields. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a placePipelines and stages, marketing sources and campaigns. | Confirmed in the analysis |
What the plans mean
- Carried across
- Lawmatics has a place for this kind of record. It is loaded there and checked against LeanLaw.
- Carried with mapping
- Lawmatics 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
Mostly a contact list, cleaned before it lands.
Lawmatics is built for contacts, leads and the conversations around them. What LeanLaw can offer it first is a list of people and companies, and sometimes a history that can be attached as notes. Whether anything else it holds has a place depends on what Lawmatics keeps besides contacts, and the table above shows that kind by kind. What has no place stays where it is or is archived.
A contact list taken from a system that was never a CRM needs work before it is useful. Names are split or joined differently, the same client appears under several spellings, and there is no record of who agreed to be contacted. The list is cleaned and de-duplicated, matched against what Lawmatics already holds, and loaded with a source tag, so the firm can tell these contacts from the ones that came through intake.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of LeanLaw 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 LeanLaw is kept running until the checks on Lawmatics are finished.
Where the data is now
Leaving LeanLaw
LeanLaw and QuickBooks Online hold two halves of the same financial record, kept in step by a live sync. A firm leaving LeanLaw is usually keeping QuickBooks, at least at first. So the question is less what to extract than how to change the system feeding QuickBooks without posting anything twice, and where the matter-level detail that only LeanLaw holds will live afterwards.
QuickBooks keeps the ledger
Every invoice, payment and trust transaction entered in LeanLaw is also in QuickBooks Online. If the destination connects to the same QuickBooks company, it must start from an agreed date and recognise what is already there. Where the destination has its own general ledger, QuickBooks is closed off at a period end and balances are carried in.
Matter detail lives in LeanLaw
QuickBooks knows the totals. LeanLaw knows which timekeeper did what on which matter, at what rate, and against what budget. That is the part to extract: time and expense entries with their narratives, and the invoice lines they became. The sums are checked back to the QuickBooks figures client by client.
Trust in two places
The trust bank account is an account in QuickBooks Online, and the ledger for each client and matter is in LeanLaw. Both have to agree with the bank statement. The three-way reconciliation is completed and saved for the last period before cutover, and opening trust balances are taken from it.
Compensation and origination
LeanLaw tracks attorney compensation and origination credit as time is billed and collected, and partners may be paid on those reports. Not every system records origination against a matter. The firm checks early whether the destination can, and saves the historic compensation reports whatever the answer.
It was never the case file
Parties, deadlines, documents and correspondence were never in LeanLaw. Some firms pair it with Clio or MyCase for those, and others use folders and Outlook. A move to an all-in-one system therefore draws on several sources, and the matter list from LeanLaw is used as the index that ties them together.
Where it is going
Arriving in Lawmatics
Lawmatics takes matters, contacts and companies from CSV files, and its API accepts notes, tasks, appointments, files, time entries and invoices. It is an intake and client relationship system, so a firm arriving from full practice management has to decide what it is for. People and matters load well. There is no general ledger, and years of billing history have no natural home.
Contacts and matters load separately
The import expects two spreadsheets: one for contacts or companies with no case, such as referrers and other lawyers, and one for matters. A matter import creates the matter and its primary contact together. Every matter has exactly one primary contact, so joint clients are loaded as one primary and one relationship.
Set up before loading
Owner, stage, practice area, source and campaign are matched by name. A value on the spreadsheet that does not match one in Lawmatics exactly creates a new one, which is how a firm ends up with two spellings of the same practice area. Users, pipelines, practice areas and marketing sources are set up first, and custom fields must exist before data is loaded into them.
Statuses and matter numbers
Each imported matter must be PNC (potential new client), Hired or Lost, with open and closed handled as sub-statuses the firm creates. The case number is a system field assigned by an auto-numbering pattern and cannot be edited by hand afterwards. Whether old matter numbers can be loaded into it, or belong in a custom field, is tested in the trial load.
Duplicates are matched by email
With Match Contacts by Email switched on, a contact whose email already exists is skipped or updated, never doubled. Names and phone numbers are not checked. Matters are not deduplicated at all, so two rows with one email create two matters on one contact. Clean-up therefore happens in the spreadsheet, and automations are switched off for every load.
What has no place
There is no general ledger. The Time & Billing module holds time entries, expenses, invoices and a trust account with a running balance per matter, and past invoices are entered as already sent and then marked paid. A firm that needs its full accounting history keeps the old system read only or carries the books in an accounting package.
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 LeanLaw holds and how its records link, then agree with you, field by field, where each piece will sit in Lawmatics. 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 LeanLaw, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Lawmatics as a trial and checked against LeanLaw: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in LeanLaw are frozen for an agreed window, the data is collected a final time and Lawmatics 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. LeanLaw 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 LeanLaw 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 LeanLaw holds
What is in it, how its records link, and where each piece would sit in Lawmatics. 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 Lawmatics
Loaded data is not yet a working system. This is what NewLaw sets up in Lawmatics, beyond the migration, so that people can work in it from the first day.
In Lawmatics the design comes before the data. The pipeline stages, practice areas, custom fields and relationship types decide what the import can hold, and the forms and automations decide what the firm’s intake looks like from the first day. If a practice system sits behind it, the field mapping between the two is part of the same job.
Set-up decisions in Lawmatics
- Pipelines and stages for intake and for open matters
- Practice areas, sub-statuses, relationship types and the matter numbering pattern
- Custom fields on matters, contacts and companies
- Intake forms, booking links and e-signature document templates
- Follow-up automations, with marketing sources and campaigns
- Mail and calendar sync, user roles and practice system integration
Questions
LeanLaw to Lawmatics: what firms ask
If we stop using LeanLaw, do we lose our QuickBooks Online data?
No. QuickBooks Online is a separate subscription in the firm’s own name, and the invoices, payments and trust entries that synced into it stay there. What goes when LeanLaw goes is the legal layer on top: time narratives, matter ledgers and the reports built from them, which is why those are extracted.
Can the new system take over the same QuickBooks company?
Often, yes. It needs to be told which customers and open invoices already exist so that it links to them and does not create a second set. The switch is made at an agreed date, with LeanLaw’s sync turned off first and the receivables total compared on both sides.
We use LeanLaw with Clio for case management. Which is the source for matters?
Both, for different things. Clio would hold the case detail, documents and calendar, and LeanLaw the time, bills and trust ledgers. The two matter lists are compared in the analysis. A matter that appears in one and not the other is traced and resolved before anything is loaded.
Do trust balances in LeanLaw have a place in Lawmatics?
In part. A trust account with a running balance; deposits are allocated to a contact and matter. The analysis sets out which trust records have a place in Lawmatics 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 LeanLaw have a place in Lawmatics?
Most of it does on paper. Notes, tasks, custom fields 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 Lawmatics is kept as a readable archive, and you see which before the move.
What has to be decided before LeanLaw data is loaded into Lawmatics?
Time entries, billing records, trust ledgers and templates are carried with mapping, so each mapping is agreed with you first. Notes, tasks, custom fields and intake records 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 LeanLaw and into Lawmatics
Other destinations from LeanLaw
Other systems that move into Lawmatics
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.
LeanLaw and Lawmatics are the names and marks of their owners, used here only to identify the two systems.
Moving from LeanLaw to Lawmatics?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.