Data migration route
Prevail to SimpleLaw migration
Prevail is a server-based case management system, and SimpleLaw is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in SimpleLaw, often from a separate accounts package.
- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Intake: Carried across
- Billing: Carried with mapping
- Trust money: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
SimpleLawCloud- 7 carried
- 3 mapped
- 4 to confirm
What moves
What moves from Prevail to SimpleLaw
Each row is a kind of record Prevail holds, whether SimpleLaw 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 place | Carried across |
| ContactsClients, other parties and referrers | HeldA central record for clients, providers, counsel, courts and experts. | Has a placeAs leads, clients or other contacts in the CRM. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldLetters and forms generated from the matter, plus evidence management. | Has a placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive. | 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. | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldTasks and calendaring. | Has a place | 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 | Carried across |
| BillingInvoices, payments and debtor balances | Held in partA matter ledger records financial and cost activity. | Has a place in partInvoices are created in the product; loading invoice history is confirmed 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. | Has a place in partTrust balances are supported; history depth is confirmed in the analysis. | Carried with mapping |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | No placeGeneral ledger stays in QuickBooks or another accounting package. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a place | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldMatter-based letters and forms. | Has a place in partTemplates are rebuilt using SimpleLaw’s own automation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldA configurable intake questionnaire and lead management. | Has a placeLeads and intake forms. | Carried across |
What the plans mean
- Carried across
- SimpleLaw has a place for this kind of record. It is loaded there and checked against Prevail.
- Carried with mapping
- SimpleLaw 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
Cases come across. The accounts are set up new.
A case management system holds the working file: parties, notes, deadlines, documents and the fields a practice area needs. It is not usually the firm’s ledger, so time, invoices and trust often sit in an accounting package beside it. Moving to SimpleLaw brings those two sources together. The case records come from Prevail. Opening balances for debtors and trust, where they move at all, come from the accounts package and are agreed to its reports.
Case systems are heavy with custom fields, and that is where the mapping work is. A personal injury or immigration file can carry dozens of fields that a general practice system has no standard place for. Each one is matched to a field in SimpleLaw, created there as a custom field, or written into a note on the matter. The firm sees which before the load. Workflows and task templates are rebuilt, not copied.
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. SimpleLaw 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 SimpleLaw
Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.
Lead, client or contact
A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.
Billing type on each matter
Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.
Storage chosen before loading
If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.
Custom fields named for templates
Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.
Portal access client by client
The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.
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 SimpleLaw. 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 SimpleLaw 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 SimpleLaw 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 SimpleLaw. 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 SimpleLaw
Loaded data is not yet a working system. This is what NewLaw sets up in SimpleLaw, beyond the migration, so that people can work in it from the first day.
The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.
Set-up decisions in SimpleLaw
- Labels for documents, activities, expenses and contact IDs
- Custom fields and intake forms for each practice area
- Document templates and the attorney-client agreement
- Workflows for case types that follow a standard process
- User permission sets and client portal visibility
- QuickBooks connection and the online payment processor
Questions
Prevail to SimpleLaw: 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 SimpleLaw?
In part. Trust balances are supported; history depth is confirmed in the analysis. The analysis sets out which trust records have a place in SimpleLaw 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 SimpleLaw?
Most of it does on paper. Emails, 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 SimpleLaw is kept as a readable archive, and you see which before the move.
What has to be decided before Prevail data is loaded into SimpleLaw?
Billing records, trust ledgers and templates are carried with mapping, so each mapping is agreed with you first. Emails, 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 SimpleLaw
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 SimpleLaw are the names and marks of their owners, used here only to identify the two systems.
Moving from Prevail to SimpleLaw?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.