Data migration route
Lawmatics to Litify migration
Lawmatics is a cloud CRM and intake system, and Litify is a cloud case management system. Contacts and intake history move, and open enquiries become leads or cases in Litify.
LawmaticsCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Intake: Carried across
- Emails: Carried with mapping
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
- Trust money: Confirmed in the analysis
LitifyCloud- 7 carried
- 4 mapped
- 2 to confirm
What moves
What moves from Lawmatics to Litify
Each row is a kind of record Lawmatics holds, whether Litify has a place for it, and what is planned. On this route seven kinds of record carry across, four kinds need mapping and two kinds are 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 placeMatters, by case type. | Carried across |
| ContactsClients, other parties and referrers | HeldContacts and companies; other parties link to a matter as relationships. | Has a placeLoaded as parties and connected by roles. | 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 placeLoaded to the document component and attached to matters. | Carried across |
| 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 partShown on the activity timeline. How old email is loaded is confirmed in the analysis. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | Held | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldAppointments with event types, synced with Google, Outlook or iCloud calendars. | Has a placeCalendar events on the matter. | 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 placeTime entries on the matter. | Carried across |
| BillingInvoices, payments and debtor balances | Held in partInvoices and payments, in the Time & Billing module. | Has a place in partBilling is part of the product. Loading past invoices is scoped 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. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields on matters, contacts and companies. | Has a placeCustom fields are created before loading. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument templates, email templates, custom forms and automations. | Has a place in partTemplates are rebuilt in Litify’s document generation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldPipelines, custom forms, booking links, marketing sources and campaigns. | Has a placeLoaded as intakes. | Carried across |
What the plans mean
- Carried across
- Litify has a place for this kind of record. It is loaded there and checked against Lawmatics.
- Carried with mapping
- Litify 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
Intake history moves. The pipeline is rebuilt.
Intake data is the front end of a case. A lead in Lawmatics carries the first conversation, the screening answers, the referrer and often a signed retainer. Many case management systems have an intake stage of their own, so a lead can land as a prospective case with that history attached. Where Litify has no such stage, open enquiries are loaded as contacts with their status in a note, and the firm decides which to open as cases.
Screening questions are the mapping work. Each intake form is a set of fields, and each field has to find a place on the case or be kept as a note. Referral sources are tidied into one list first, because they are usually typed by hand and reporting depends on them. Marketing automations, email sequences and web forms do not move as data. They are set up again in Litify or in the tool that feeds it.
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 Litify 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 Litify
Loading a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.
The design comes first
Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.
One party, many roles
Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.
Open enquiries load as intakes
Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.
Documents load after records
Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.
Validation rules reject bad rows
A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of Litify says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Lawmatics and checking each trial against Lawmatics.
Analysis
We read what Lawmatics holds and how its records link, then agree with you, field by field, where each piece will sit in Litify. 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 Litify as a trial and checked against Lawmatics: record counts, financial 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 Litify goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in Lawmatics as at the cutover date. 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 Litify. 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 Litify
Loaded data is not yet a working system. The maker of Litify runs or arranges the set-up of its product, so this is what has to be decided and put in place in Litify, whoever does the work, before people rely on it from the first day.
A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.
Set-up decisions in Litify
- Define intake questionnaires and the rules for conversion
- Set case types, matter stages and page layouts
- Build matter plans that create tasks at each stage
- Design document folders and generation templates per case type
- Configure user roles and sharing for restricted matters
- Decide on timekeeping, billing and accounting integrations
Questions
Lawmatics to Litify: 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 Litify?
That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in Lawmatics before the plan is fixed. If Litify turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
Does everything in Lawmatics have a place in Litify?
Most of it does on paper. Notes and trust ledgers 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 Litify is kept as a readable archive, and you see which before the move.
What has to be decided before Lawmatics data is loaded into Litify?
Emails, billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Notes and trust ledgers 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 Litify
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 Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from Lawmatics to Litify?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.