Data migration route
ProLaw to Litify migration
ProLaw is a server-based 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.
ProLawServer- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Calendar: Carried across
- Time and expenses: Carried across
- Intake: Carried across
- Emails: Carried with mapping
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Templates: Confirmed in the analysis
LitifyCloud- 6 carried
- 3 mapped
- 5 to confirm
What moves
What moves from ProLaw to Litify
Each row is a kind of record ProLaw holds, whether Litify has a place for it, and what is planned. On this route six kinds of record carry across, three kinds need mapping and five 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 | HeldOne database of clients, prospects and relationships, also used for conflict checks. | Has a placeLoaded as parties and connected by roles. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldDocuments are reached from the matter, with Word, Outlook and Adobe integration. | Has a placeLoaded to the document component and attached to matters. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partThrough the Outlook integration. | 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 | HeldRules-based docketing and calendaring. | Has a placeCalendar events on the matter. | Carried across |
| 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 | Held | Has a placeTime entries on the matter. | Carried across |
| BillingInvoices, payments and debtor balances | HeldBilling history and invoicing status are held with the matter. | 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 | HeldPart of the back office accounting. | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | HeldFinancial accounting, budgeting and cost recovery, including contingency case accounting. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldCustom tabs, which can also link to other applications. | Has a placeCustom fields are created before loading. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partTemplates are rebuilt in Litify’s document generation. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partProspects are kept in the same contact database as 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 ProLaw.
- 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 ProLaw 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 ProLaw, and kept as the record of what was billed and held.
ProLaw runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Litify is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.
Where the data is now
Leaving ProLaw
A firm that runs both halves of ProLaw has a wide scope to move: matters, a shared contact database, documents, docket entries, records management, time, billing and the ledgers. Having it all in one system on the firm’s server helps. The effort goes into custom tabs, rules-based docket entries and deciding where the back office goes if the destination has no general ledger.
Front office and back office
The front office holds matters, contacts, documents, events and conflicts, and the back office holds billing and the firm’s accounts. A firm may have licensed one half and run another product for the rest. Which halves are in use, and what the other product is, sets the shape of the whole move.
Custom tabs
ProLaw lets a firm add its own tabs and connect them to other applications. Years of practice-specific data end up there. Each tab is listed with its fields and how many matters use them, and the firm chooses which become fields in the new system and which become a note.
Docket entries from rules
Deadlines can be generated from court rules, so one trigger date produces a set of related events. The dates come across as calendar entries, but the tie back to the rule does not, so a changed hearing date will not recalculate the old set. Open matters with rule-based deadlines are flagged for the lawyers to review.
One contact, many uses
A single contact database serves clients, prospects, other parties and marketing lists, and the conflict check reads the same people. Duplicates therefore distort conflict results as well as mailings. They are merged in ProLaw before extraction where they can be identified, and each relationship type is mapped.
Physical file records
Records management tracks paper files and where they are kept. It is easy to forget until someone needs a file from storage. The location recorded for each matter’s paper file is carried to a field or note on the matter in the destination.
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 ProLaw and checking each trial against ProLaw.
Analysis
We read what ProLaw 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 ProLaw, 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 ProLaw: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in ProLaw 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 ProLaw as at the cutover date. ProLaw 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 ProLaw 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 ProLaw 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
ProLaw to Litify: what firms ask
Who makes ProLaw now?
Elite. ProLaw was sold under the Thomson Reuters name for years, and Elite, once a Thomson Reuters business, now publishes it as a separate company. Elite’s own site carries ProLaw customer news and a ProLaw summit for 2026. Your support contract shows which entity you deal with.
Do documents keep their matter links?
Documents saved through ProLaw are recorded against a matter. The record and the file are brought together again in the destination, under the same matter and with the original dates. Files saved outside ProLaw, on desktops or shared drives, are a separate source that the firm identifies during the analysis.
Can contingency matters and their costs move?
Yes, but they need more care than hourly matters. Advanced costs and expected fees are extracted per matter and agreed to ProLaw’s reports. Where the destination handles contingency work differently, the firm’s accounts staff decide how each balance is to be shown before the trial load.
Do trust balances in ProLaw 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 ProLaw 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 ProLaw have a place in Litify?
Most of it does on paper. Notes, tasks, trust ledgers, the firm’s accounts and templates 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 ProLaw data is loaded into Litify?
Emails, billing records and custom fields are carried with mapping, so each mapping is agreed with you first. Notes, tasks, trust ledgers, the firm’s accounts and templates 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 ProLaw and into Litify
Other destinations from ProLaw
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.
ProLaw and Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from ProLaw 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.