Data migration route
PracticeEvolve to Litify migration
PracticeEvolve 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.
PracticeEvolveCloud- 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 PracticeEvolve to Litify
Each row is a kind of record PracticeEvolve 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 | Held | Has a placeMatters, by case type. | Carried across |
| ContactsClients, other parties and referrers | HeldIncludes a conflict search across the system. | Has a placeLoaded as parties and connected by roles. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldIndexed for searching, including image-based PDFs. | Has a placeLoaded to the document component and attached to matters. | Carried across |
| EmailsEmails saved to matters or to the store | HeldMatter emails are filed and saved centrally. | 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 | To be confirmed | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partEvents are held on the matter. | Has a placeCalendar events on the matter. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTo-do lists, recurring tasks and workflows. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldAutomatic activity tracking converts to time entries. | Has a placeTime entries on the matter. | Carried across |
| BillingInvoices, payments and debtor balances | HeldFlexible billing with approval flows. | 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 | HeldClient funds management within the legal accounts. | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | HeldLegal accounts with balance sheet, debtors, cash flow and budget reporting. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | Held in partEvolvePlus is described as fully customisable; the extent is confirmed in the analysis. | Has a placeCustom fields are created before loading. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldA supplied library of automated forms and precedents, plus the firm’s own. | Has a place in partTemplates are rebuilt in Litify’s document generation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldLead tracking for prospective clients. | 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 PracticeEvolve.
- 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 PracticeEvolve 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 PracticeEvolve, 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 PracticeEvolve 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 PracticeEvolve is kept running until the checks on Litify are finished.
Where the data is now
Leaving PracticeEvolve
PracticeEvolve keeps a firm’s data in the vendor’s Azure hosting, so extraction is arranged with the vendor. Which product the firm is on comes first, EvolveGo or EvolvePlus, because the two differ in how much has been customised. The accounts are inside the system, so client funds and office ledgers form part of every move.
EvolveGo or EvolvePlus
The vendor sells two cloud products. EvolveGo is the one built for quick implementation. EvolvePlus allows full customisation and workflows built without code. An EvolvePlus firm is likely to have fields, screens and processes of its own, and the analysis has to find them. An EvolveGo firm is closer to the product as supplied.
Supplied precedents versus yours
PracticeEvolve provides a large library of automated forms and precedents and keeps it up to date. Those belong to the vendor’s library. Precedents the firm added or adapted are the firm’s. We separate the two lists early, because only the second is rebuilt in the new system, and it is usually much shorter than staff expect.
Where the documents are held
Documents and filed emails are saved centrally and indexed for search. We confirm whether they are held by PracticeEvolve itself or by a separate document management product connected to it, as that decides who supplies the files and how each one is tied back to its matter.
Messages in Communicate
The built-in Communicate platform carries secure messages and shared files between the firm and its clients. Those conversations are part of the file for some matters. We check whether they are exported with the matter. If not, the messages for open matters are saved to the file as documents before cutover.
Accounts in the same system
Legal accounts, billing and client funds run inside PracticeEvolve, with its own reports for debtors, cash flow and budgets, and the UK site lists Making Tax Digital among its features. Leaving means choosing where office accounting goes next, and closing a tax period in the old system before balances are taken.
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 PracticeEvolve and checking each trial against PracticeEvolve.
Analysis
We read what PracticeEvolve 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 PracticeEvolve, 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 PracticeEvolve: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in PracticeEvolve 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 PracticeEvolve as at the cutover date. PracticeEvolve 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 PracticeEvolve 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 PracticeEvolve 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
PracticeEvolve to Litify: what firms ask
How do we get our data out of a hosted system?
Through the vendor, at the firm’s request. We specify what is needed: the database or a full export, every document with its matter reference, and closing accounts reports taken at the same time. How it is delivered is confirmed with PracticeEvolve during the analysis, and the first copy is tested before a cutover date is set.
Do the automated forms come with us?
The supplied forms stay with PracticeEvolve. Documents already produced from them are on the matters and move as files. The firm’s own precedents are exported and their merge fields replaced with the destination’s. If the new system has its own forms library, we compare it with the forms the firm uses most.
Is the Australian version different from the UK one?
The vendor publishes separate UK and Australian sites, and each edition follows its own country’s rules for client money and tax. Our method is the same for both. The checks on the financial cutover are written against the rules of the jurisdiction the firm practises in.
Do trust balances in PracticeEvolve 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 PracticeEvolve 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 PracticeEvolve 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 PracticeEvolve 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 PracticeEvolve and into Litify
Other destinations from PracticeEvolve
Other systems that move 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.
PracticeEvolve and Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from PracticeEvolve 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.