Data migration route
ProLaw to Server drives migration
ProLaw is a server-based practice 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.
ProLawServer- Documents: Carried across
- Emails: Carried with mapping
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Templates: Confirmed in the analysis
Server drivesFiles- Matters: Kept as a readable archive
- Contacts: Kept as a readable archive
- Calendar: 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
- Firm accounts: Kept as a readable archive
- Custom fields: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 1 mapped
- 3 to confirm
- 9 archived
What moves
What moves from ProLaw to Server drives
Each row is a kind of record ProLaw holds, whether Server drives have a place for it, and what is planned. On this route one kind of record carries across, one kind needs mapping, nine kinds have no place in Server drives and are archived and three kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held | No placeA matter becomes a folder; its details survive only in an index file. | Kept as a readable archive |
| ContactsClients, other parties and referrers | HeldOne database of clients, prospects and relationships, also used for conflict checks. | No placeCan be kept only as an exported spreadsheet. | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldDocuments are reached from the matter, with Word, Outlook and Adobe integration. | Has a placeFiles in folders, named and dated during the load. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partThrough the Outlook integration. | 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 | HeldRules-based docketing and calendaring. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | No place | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | Held | No placeOnly as exported reports or spreadsheets. | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | HeldBilling history and invoicing status are held with the matter. | Has a place in partInvoices as PDF files; no ledger. | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | HeldPart of the back office accounting. | No placeOnly as exported ledger reports kept as files. | Kept as a readable archive |
| Firm accountsGeneral ledger, office account and payables | HeldFinancial accounting, budgeting and cost recovery, including contingency case accounting. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | HeldCustom tabs, which can also link to other applications. | No place | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partPrecedents as Word files; merge fields tied to the old system stop working. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partProspects are kept in the same contact database as clients. | 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 ProLaw.
- 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 ProLaw 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 ProLaw 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 ProLaw.
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 ProLaw stays untouched until the copy in Server drives has been checked.
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 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 ProLaw 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 ProLaw: 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 ProLaw, a final pass over a weekend picks up what changed since the trial. 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 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
ProLaw to Server drives: 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 Server drives?
No. Server drives do not keep trust ledgers. Only as exported ledger reports kept as files. Trust records from ProLaw 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, time entries, billing records, trust ledgers, the firm’s accounts, custom fields and intake records. They are exported from ProLaw 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 ProLaw data is loaded into Server drives?
Emails are carried with mapping, so each mapping is agreed with you first. Notes, tasks and templates 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 ProLaw and into Server drives
Other destinations from ProLaw
Other systems that move 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.
ProLaw and Server drives are the names and marks of their owners, used here only to identify the two systems.
Moving from ProLaw 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.