Data migration route
CARET Legal to Litify migration
CARET Legal is a cloud practice management system, and Litify is a cloud case management system. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.
CARET LegalCloud- 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
- Firm accounts: Confirmed in the analysis
LitifyCloud- 7 carried
- 4 mapped
- 3 to confirm
What moves
What moves from CARET Legal to Litify
Each row is a kind of record CARET Legal 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 three kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldMatter fields include status, date opened, primary clients and three separate attorney roles. | Has a placeMatters, by case type. | Carried across |
| ContactsClients, other parties and referrers | Held | Has a placeLoaded as parties and connected by roles. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldNative store with folders and version history; NetDocuments or Worldox can be linked instead. | Has a placeLoaded to the document component and attached to matters. | Carried across |
| EmailsEmails saved to matters or to the store | HeldBuilt-in email client syncs with Google, Office 365 or IMAP and copies messages to the matter. | 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 | HeldIncludes rules-based court deadlines. | Has a placeCalendar events on the matter. | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldA timer can run while an email is written and save the entry on send. | Has a placeTime entries on the matter. | Carried across |
| BillingInvoices, payments and debtor balances | HeldIncludes pre-billing, batch billing, LEDES and split billing. | 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 | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral ledger, profit and loss, balance sheet and vendor bills are built in. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields can be defined for each practice area. | Has a placeCustom fields are created before loading. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument automation is built in, with a HotDocs-based option for complex documents. | Has a place in partTemplates are rebuilt in Litify’s document generation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldCRM with lead sources, intake forms and conversion of a lead to a matter. | 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 CARET Legal.
- 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
Matters become cases. The ledgers need a home.
Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Litify. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.
Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from CARET Legal has to be given a case type in Litify, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Litify is exported as reports and ledgers the firm can open without CARET Legal, and kept as the record of what was billed and held.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of CARET Legal 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 CARET Legal is kept running until the checks on Litify are finished.
Where the data is now
Leaving CARET Legal
CARET Legal keeps email, documents, leads and the firm’s books inside one product, so leaving it usually means replacing several things at once. Matters and documents are the familiar part. The firm also has to decide where its general ledger goes, what happens to years of email filed against matters, and whether the destination can hold the lead records that sit in the CRM.
Email is part of it
The built-in email client copies messages into each matter’s Communications tab, and it attaches inbound mail from known matter contacts automatically. A firm can end up with far more filed email than staff ever filed by hand. The analysis counts it per matter, and the firm decides whether it moves as documents or stays in the mail provider.
The firm’s books are inside
There is no separate accounting package to leave running. The general ledger, the profit and loss, the balance sheet and vendor bills are all in CARET Legal. If the destination has no general ledger, an accounting system is chosen and opened first, and the cutover date is set at the end of an accounting period.
Three attorneys per matter
Each matter records a responsible, an originating and a billing attorney. Plenty of systems hold one or two of those. Origination often drives partner compensation reports, so where the destination has no field for it, a custom field is created and tested against a known report before the final load.
Fields differ by practice area
Custom fields are set up per practice area, so a family law matter and a personal injury matter carry different sets. The mapping is done one practice area at a time. Fields that feed intake forms or document automation are marked, because their names matter to templates in the new system.
Leads that never became matters
The CRM holds prospects with their source, practice area and expected value, and only some were converted to matters. A destination without a lead pipeline has nowhere obvious to put the rest. They are exported as a list for the firm to keep, or loaded as contacts with a tag.
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 CARET Legal and checking each trial against CARET Legal.
Analysis
We read what CARET Legal 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 CARET Legal, 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 CARET Legal: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in CARET Legal 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 CARET Legal as at the cutover date. CARET Legal 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 CARET Legal 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 CARET Legal 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
CARET Legal to Litify: what firms ask
We used to be on Zola Suite. Is that data separate from CARET Legal?
No. Zola Suite was renamed CARET Legal, and the firm’s account carried on under the new name. Everything entered in the Zola years is in the same database as what was entered last week, so there is one extraction to plan.
Our documents are in NetDocuments, linked to CARET Legal. Do they need to move?
Not necessarily. Where NetDocuments or Worldox holds the documents, the files can stay there. What has to be rebuilt is the link between each matter and its workspace, if the new practice management system supports one. Documents saved in CARET Legal’s own store do move, with their folders.
Can we move part-way through a financial year?
Yes, but the general ledger makes the date matter more than it does for a system that only bills. Opening balances are taken at a period end that the accountant has closed, and the trust cutover is rehearsed on a full trial load before the real one.
Do trust balances in CARET Legal 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 CARET Legal 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 CARET Legal have a place in Litify?
Most of it does on paper. Notes, trust ledgers and the firm’s accounts 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 CARET Legal 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, trust ledgers and the firm’s accounts 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 CARET Legal and into Litify
Other destinations from CARET Legal
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.
CARET Legal and Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from CARET Legal 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.