Data migration route
Prevail to Server drives migration
Prevail is a server-based case management system, and Server drives are plain files on equipment the firm controls. Documents move into a folder for each client and matter, and the data behind them is kept as an export.
- Documents: Carried across
- Emails: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
Server drivesFiles- Matters: Kept as a readable archive
- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Tasks: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Trust money: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 2 mapped
- 3 to confirm
- 8 archived
What moves
What moves from Prevail to Server drives
Each row is a kind of record Prevail holds, whether Server drives have a place for it, and what is planned. On this route one kind of record carries across, two kinds need mapping, eight kinds have no place in Server drives and are archived 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. | No placeA matter becomes a folder; its details survive only in an index file. | Kept as a readable archive |
| ContactsClients, other parties and referrers | HeldA central record for clients, providers, counsel, courts and experts. | No placeCan be kept only as an exported spreadsheet. | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldLetters and forms generated from the matter, plus evidence management. | Has a placeFiles in folders, named and dated during the load. | 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 partAs .msg or .eml files in each matter’s correspondence folder. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place in partAs a text or PDF file per matter, not as separate records. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldTasks and calendaring. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | HeldTasks, including those set by Process Builder stages. | No place | Kept as a readable archive |
| Time and expensesTime and expense entries, billed and unbilled | Held in partListed by the vendor under time, billing and trust. Detail is not published. | No placeOnly as exported reports or spreadsheets. | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | Held in partA matter ledger records financial and cost activity. | Has a place in partInvoices as PDF files; no ledger. | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | Held in partListed by the vendor under time, billing and trust. Detail is not published. | No placeOnly as exported ledger reports kept as files. | Kept as a readable archive |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | No place | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | No place | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldMatter-based letters and forms. | Has a place in partPrecedents as Word files; merge fields tied to the old system stop working. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldA configurable intake questionnaire and lead management. | No place | Kept as a readable archive |
What the plans mean
- Carried across
- Server drives has a place for this kind of record. It is loaded there and checked against Prevail.
- Carried with mapping
- Server drives 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.
- Kept as a readable archive
- Server drives has no place for it. It is exported in a format that opens without Prevail and handed to the firm as a read-only archive.
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
Out of the system, into folders the firm can read.
File storage has folders and files and nothing else. Moving from Prevail into Server drives means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters Server drives do not allow in a name.
Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in Prevail.
Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in Prevail stays untouched until the copy in Server drives has been checked.
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 Server drives
Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.
Agree the tree and the names
A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.
Budget the path length
Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.
Dates have to be set deliberately
A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.
Emails become message files
Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.
Keep an index beside the files
A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Server drives on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Prevail holds and how it is organised, then agree with you where each kind of record will sit in Server drives. Anything with no place there stays behind or is archived, and you see which before the move.
Clean-up
Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.
Trial load
A trial is loaded into Server drives and checked against Prevail: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.
Cutover
There is no financial cutover on this route. After a short freeze on changes in Prevail, a final pass over a weekend picks up what changed since the trial. 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 Server drives. 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
Structure, permissions and handover
Server drives are storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.
A server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.
What is agreed and set up
- Share and top-level folders for clients, precedents and administration
- Security groups and folder permissions, with restricted matters separate
- Drive letter mapped for every user at sign-in
- Backup schedule and shadow copies for earlier versions
- Written naming rule for client, matter and document names
- Read-only area for closed matters and archived system exports
Questions
Prevail to Server drives: 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 Server drives?
No. Server drives do not keep trust ledgers. Only as exported ledger reports kept as files. Trust records from Prevail are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.
What happens to records Server drives have no place for?
On this route that is matters, contacts, calendar entries, tasks, time entries, billing records, trust ledgers and intake records. They are exported from Prevail in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.
What has to be decided before Prevail data is loaded into Server drives?
Emails and templates 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 decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from Prevail and into Server drives
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 Server drives are the names and marks of their owners, used here only to identify the two systems.
Moving from Prevail to Server drives?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.