Data migration route
Prevail to Litify migration
Prevail is a server-based case management system, and Litify is a cloud one. The records line up case for case, and the detail is in the fields and stages.
- 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
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
LitifyCloud- 7 carried
- 3 mapped
- 4 to confirm
What moves
What moves from Prevail to Litify
Each row is a kind of record Prevail holds, whether Litify has a place for it, and what is planned. On this route seven kinds of record carry across, three kinds need mapping and four kinds are confirmed in the analysis.
| Record | In Prevail | What is planned | |
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldMatters with related parties. Stages are configured by the firm. | Has a placeMatters, by case type. | Carried across |
| ContactsClients, other parties and referrers | HeldA central record for clients, providers, counsel, courts and experts. | Has a placeLoaded as parties and connected by roles. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldLetters and forms generated from the matter, plus evidence management. | Has a placeLoaded to the document component and attached to matters. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partAn Outlook integration is offered. What is stored per matter was not confirmed. | 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 | HeldTasks and calendaring. | Has a placeCalendar events on the matter. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTasks, including those set by Process Builder stages. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | Held in partListed by the vendor under time, billing and trust. Detail is not published. | Has a placeTime entries on the matter. | Carried across |
| BillingInvoices, payments and debtor balances | Held in partA matter ledger records financial and cost activity. | 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 partListed by the vendor under time, billing and trust. Detail is not published. | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeCustom fields are created before loading. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldMatter-based letters and forms. | Has a place in partTemplates are rebuilt in Litify’s document generation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldA configurable intake questionnaire and lead management. | 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 Prevail.
- 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
Case to case, field by field.
Two case management systems look alike from a distance and differ in almost every detail. Each has its own idea of a case type, a stage, a party role and a deadline. Prevail and Litify may both hold a limitation date, yet one calculates it and the other stores what was typed. The mapping goes field by field and status by status, and the trial load is checked by opening real cases in both systems side by side.
Custom fields hold most of what the firm has built up. Years of intake answers, injury details or visa histories sit in fields the firm added itself. Each is matched to a field in Litify, and anything unmatched is kept as a note on the case so that it can still be searched. Workflows and document templates are rebuilt in the new system’s own tools. Open tasks come across with their owners and due dates.
Prevail 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 Prevail
Prevail is used for claimant work in which each matter follows set stages and produces many letters and forms. The data is on a Windows server that either the firm or the vendor runs. Planning starts with where that server is, and with which practice areas the firm actually uses the program for, since each has its own fields.
Stages set by the firm
Application, reconsideration, hearing and review stages are configured by each firm, and the Process Builder attaches tasks, appointments and document actions to them. The stage a matter has reached is the fact staff look for first. That list is mapped before anything else, and every open matter is checked to arrive at the right stage.
Social Security detail
Disability matters carry claim identifiers, representation details, work history, medical providers and the status of each evidence request. A destination not built for this work needs custom fields for most of it. Evidence requests still outstanding are loaded as tasks against the provider, so the follow-up continues without a gap.
Own server or vendor hosting
The program can run on the firm’s Windows server or in the vendor’s managed hosting. How the data is reached differs between the two. On the firm’s own server a backup is taken locally. In the hosted service, how a copy is provided is arranged with the firm at the start of the analysis.
Generated letters and forms
Letters and forms are produced from matter data and saved or printed. Over years this becomes the larger part of the file. Each document is extracted with its matter and date. The templates behind them use Prevail’s own merge fields and are rebuilt in the destination, most used first.
The matter ledger
Costs and financial activity are recorded on a ledger connected to the matter. For practices paid on the outcome, the figures that count are costs advanced and fees received. Those are reconciled against the accounting records before loading, and where the destination has no ledger the balance is carried as a figure with a note.
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 Prevail and checking each trial against Prevail.
Analysis
We read what Prevail 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 Prevail, 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 Prevail: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Prevail 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 Prevail as at the cutover date. Prevail 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 Prevail 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 Prevail 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
Prevail to Litify: what firms ask
Is Prevail a desktop program or a cloud system?
It is Windows software that works against a server. Some firms run that server themselves and others use the vendor’s managed hosting, where staff connect remotely. Both hold the same kind of data. The difference for a migration is only in how a copy of the database and documents is obtained.
Can a general practice system cope with Social Security disability matters?
It needs building out. Claim numbers, hearing offices, appeal stages and evidence tracking are not standard fields in a general system. They are added as custom fields with a workflow per stage. The analysis shows the firm a sample disability matter laid out in the destination before it decides.
Will the client portal carry over?
The portal belongs to Prevail, so client logins do not transfer as a working portal. Messages and documents exchanged through it can be filed to each matter if they can be extracted. If the destination has its own portal, clients are invited to it at go-live with a short notice explaining the change.
Do trust balances in Prevail 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 Prevail 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 Prevail have a place in Litify?
Most of it does on paper. Notes, trust ledgers, the firm’s accounts and custom fields 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 Prevail data is loaded into Litify?
Emails, billing records and templates are carried with mapping, so each mapping is agreed with you first. Notes, trust ledgers, the firm’s accounts and custom fields 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 Prevail 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.
Prevail and Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from Prevail 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.