Data migration route
Prevail to Filevine migration
Prevail is a server-based case management system, and Filevine 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
- Emails: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Trust money: Carried with mapping
- Templates: Carried with mapping
- Intake: Carried with mapping
- Notes: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
FilevineCloud- 6 carried
- 5 mapped
- 3 to confirm
What moves
What moves from Prevail to Filevine
Each row is a kind of record Prevail holds, whether Filevine has a place for it, and what is planned. On this route six kinds of record carry across, five kinds need mapping and three 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 placeLoaded as projects of a defined project type. | Carried across |
| ContactsClients, other parties and referrers | HeldA central record for clients, providers, counsel, courts and experts. | Has a placeContact cards, linked to projects. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldLetters and forms generated from the matter, plus evidence management. | Has a placeDocs section with folders. Templated project folders can be set per type. | 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 placeHeld in the activity feed of the project. | Carried across |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeHeld as notes in the activity feed. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldTasks and calendaring. | Has a placeDeadlines and calendar events. | 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 place in partNeeds the Billing product enabled. | Carried with mapping |
| BillingInvoices, payments and debtor balances | Held in partA matter ledger records financial and cost activity. | Has a place in partNeeds the Billing product enabled. | 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. | Has a place in partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis. | Carried with mapping |
| 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 sections and fields per project type. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldMatter-based letters and forms. | Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldA configurable intake questionnaire and lead management. | Has a place in partLeads belong in Lead Docket, which passes signed clients to Filevine. | Carried with mapping |
What the plans mean
- Carried across
- Filevine has a place for this kind of record. It is loaded there and checked against Prevail.
- Carried with mapping
- Filevine 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 Filevine 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 Filevine, 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. Filevine 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 Filevine
Loading a firm into Filevine depends on the project types being built first. Until the sections and fields exist there is nowhere for the data to go, so configuration and migration are planned together. The old system’s parties, insurers, providers and key dates are mapped to sections, and its notes and emails are loaded into each project’s activity feed.
Project types before data
Each area of practice needs a project type with its sections, fields and phases defined in the Customs Editor. Changes made there apply to every project of that type. The types are drafted from the old system’s data, tested with a few real cases, and only then is the bulk load run.
One contact card per person
Contacts are held as contact cards. A doctor or adjuster who appears on many projects is best loaded as one card, not one for each project. Duplicates in the old system are merged before loading where they can be identified. Loading them as they are produces several cards for the same person, and staff then pick the wrong one when adding a party.
Lists become collection items
Anything the old system held as a list against a matter, such as providers, liens, insurance policies or expenses, is loaded as items in a collection section. Each column needs a matching field. Totals per project are compared with the old system afterwards, since those figures feed the settlement and disbursal sheets.
History goes into the feed
File notes, emails and completed tasks from the old system are loaded into the activity feed with their original dates and authors. Authors must exist as users or be recorded in the text. The feed is long on an old case, so staff are shown how to filter it before go-live.
Billing is a separate switch
The Billing section only appears once Billing is enabled for the firm. Time entries, invoices and trust balances from the old system need that in place before they can be loaded. A firm that leaves it off can still record case costs in a collection section built for the purpose.
How NewLaw runs it
Four steps, in this order.
Trust money moves on this route, so the trust cutover gets a rehearsal of its own.
Analysis
We read what Prevail holds and how its records link, then agree with you, field by field, where each piece will sit in Filevine. 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 Filevine as a trial and checked against Prevail: record counts, trust and debtor 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 Filevine goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. 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 Filevine. 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 Filevine
Loaded data is not yet a working system. This is what NewLaw sets up in Filevine, beyond the migration, so that people can work in it from the first day.
Filevine arrives as a platform to be configured, and most of the implementation is design. Someone has to decide what a project looks like for each kind of work the firm does, what moves it from one phase to the next, and who can see what. Those decisions are made with the people who run the files, then built and tested.
Set-up decisions in Filevine
- Design project types, sections and fields for each practice area
- Define phases and the tasks each phase should trigger
- Build document templates that fill from project fields
- Set teams, permissions and protected sections for restricted matters
- Decide whether Billing and Payments are switched on
- Connect Lead Docket so signed leads become projects
Questions
Prevail to Filevine: 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 Filevine?
In part. Trust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis. The analysis sets out which trust records have a place in Filevine and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.
Does everything in Prevail have a place in Filevine?
Most of it does on paper. Notes, 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 Filevine is kept as a readable archive, and you see which before the move.
What has to be decided before Prevail data is loaded into Filevine?
Time entries, billing records, trust ledgers, templates and intake records are carried with mapping, so each mapping is agreed with you first. Notes, 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 Filevine
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 Filevine are the names and marks of their owners, used here only to identify the two systems.
Moving from Prevail to Filevine?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.