Data migration route
MerusCase data to Full data export
MerusCase is a cloud practice management system, and Full data export is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what MerusCase holds and keeps it readable and open to queries.
MerusCaseCloud- Matters: Exported in full
- Contacts: Exported in full
- Documents: Exported in full
- Notes: Exported in full
- Calendar: Exported in full
- Tasks: Exported in full
- Time and expenses: Exported in full
- Billing: Exported in full
- Trust money: Exported in full
- Emails: Exported with mapping
- Firm accounts: Exported with mapping
- Templates: Exported with mapping
- Custom fields: Confirmed in the analysis
- Intake: Confirmed in the analysis
Full data exportFiles- 9 carried
- 3 mapped
- 2 to confirm
What moves
What moves from MerusCase to Full data export
Each row is a kind of record MerusCase holds, whether Full data export has a place for it, and what is planned. On this route nine kinds of record carry across, three kinds need mapping and two kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldCases, with fields that depend on the case type. Finished cases are archived. | Has a placeA matters table keyed by the original matter number. | Exported in full |
| ContactsClients, other parties and referrers | HeldSeparate contact and company lists, with duplicate removal. | Has a placeA contacts table and a table of each contact’s role on each matter. | Exported in full |
| DocumentsFiles stored in or linked from the system | HeldUploaded or batch scanned, then linked to the case file. | Has a placeFiles under their original names, in client and matter folders. | Exported in full |
| EmailsEmails saved to matters or to the store | HeldEmail accounts sync into the product and messages are linked to cases. | Has a place in partFiled emails as message files in the matter’s folder, if the source exposes them. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | HeldCase notes, which can be merged into forms and documents. | Has a placeA notes table with matter, author and date for each note. | Exported in full |
| CalendarAppointments, court dates and deadlines | HeldEvents and deadlines, which can be attached to a case. | Has a placeA table of appointments and key dates; nothing shows it as a diary. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | HeldAssignments delegated to team members, with reminders. | Has a placeA table of tasks with assignee, due date and status. | Exported in full |
| Time and expensesTime and expense entries, billed and unbilled | HeldTimers and time entries on case ledgers. | Has a placeA time entries table with fee earner, matter, units, rate and billed status. | Exported in full |
| BillingInvoices, payments and debtor balances | HeldInvoices, payments and electronic billing formats including LEDES. | Has a placeInvoice, line and receipt tables; invoice PDFs can be kept beside them. | Exported in full |
| Trust moneyTrust or client account ledgers and balances | Held in partDescribed by the vendor as trust accounting tracking, on case ledgers. | Has a placeA trust transactions table; ledger reports can be kept as PDF beside it. | Exported in full |
| Firm accountsGeneral ledger, office account and payables | Held in partOperating receivables are built in. Payables were not confirmed. | Has a place in partJournals and account balances, where the source held a general ledger. | Exported with mapping |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeExtra columns under their original field names. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldWord templates and PDF court forms that fill from the case. | Has a place in partTemplate files only; the merge fields in them will not run. | Exported with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a place in partAn enquiries table, where the source tracked leads. | Confirmed in the analysis |
What the plans mean
- Exported in full
- Full data export has a place for this kind of record. It is loaded there and checked against MerusCase.
- Exported with mapping
- Full data export 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
Not a new system. A complete copy the firm can query.
Writing MerusCase out to Full data export is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.
What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in MerusCase as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.
MerusCase is hosted by its maker and Full data export sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What MerusCase will release depends on its export tools, and that is confirmed in the analysis.
Where the data is now
Leaving MerusCase
MerusCase keeps a good deal inside one system: the firm’s email, scanned post, court forms and ledgers as well as the cases. A move off it has to account for each. The case data and documents are the bulk of the work. Email and the books need decisions, because the destination may expect those to live somewhere else.
The Activity tab
A case’s documents and other activity are listed together on its Activity tab, each entry with a type and a date. That list is the file. It is extracted in full and split by type, so documents go to the document store and notes to file notes, each keeping its original date and description.
Email inside the product
Staff can run their mailboxes through MerusCase and link messages to cases as they go. Linked messages are case records and move with the case. Messages never linked remain in the underlying mail account. The firm is told which is which, so nobody expects an unlinked email to appear in the new system.
Batch-scanned documents
Post is scanned in batches, separated into individual documents by the system and then linked to case files. Any pages still unlinked at cutover belong to no case. That queue is cleared before the final extraction, or exported as a folder for someone to file by hand afterwards.
Case types change the fields
The fields on a case depend on its case type, so a workers’ compensation case and an immigration case do not share a layout. Each case type is mapped on its own. Fields that exist for only one type are easy to miss in a general mapping, and are checked against sample cases of every type.
Ledgers and trust tracking
Time, charges, invoices, payments and trust entries are kept on case ledgers in the Books area. Unbilled time and outstanding invoices are reconciled per case before loading. Trust balances are agreed to the bank statement first, and that part of the cutover is rehearsed in a full trial load.
Where it is going
Arriving in Full data export
A full export is judged by whether a stranger can use it. In five years the question will be something like: what was the trust balance on this matter the day it closed, and where is the signed agreement. The export is planned backwards from questions of that kind, and it is checked against the live system while the live system can still be opened.
Tables that still join up
Each kind of record becomes its own table: matters, contacts, time entries, invoices, trust transactions. The identifiers that link them are kept in every table, so a time entry can still be traced to its matter and its fee earner. An export that keeps the rows and drops the keys cannot be rejoined later.
Documents with an index
Documents are written to folders by client and matter under their original names. On their own they can be found only by name. An index listing each file with its matter number, title, author, dates and path is what lets someone find the right version of a lease among forty thousand files without the old system’s search. What the index records is settled in the analysis.
Reports a person can read
Raw tables do not satisfy an auditor or a former client. The firm decides which reports are also printed to PDF from the old system as at the final date: trust ledgers, matter ledgers, debtor lists and issued invoices are the usual candidates. They cannot be regenerated once the licence ends.
What an export does not keep
Screens, workflows, document automation, saved searches and user permissions belong to the software and stay with it. Figures the system calculated on the fly, such as a matter’s unbilled total, exist in an export only if they were captured as a report. The firm is told which of these are being let go.
Checked while the source is open
Record counts and financial totals in the export are reconciled to the live system: number of matters, sum of trust balances, total debtors, document count per matter on a sample. This is done before the subscription lapses or the server is turned off, because afterwards there is nothing left to compare against.
How NewLaw runs it
Four steps, in this order.
This route produces an archive, not a working system, so the steps are about completeness and proof.
Analysis
We read what MerusCase holds, table by table, and agree with you what the copy in Full data export must be able to answer later. Everything MerusCase holds is in scope unless you take it out.
Clean-up, if you want it
An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.
Trial export
The data is written to Full data export as a trial and checked against MerusCase: record counts, totals where MerusCase holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.
Final export
After the last day of work in MerusCase, the export is run a final time and checked again. There is nothing to go live. MerusCase is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.
Fixed price, agreed after the analysis. How NewLaw moves legal data
Start
Start this migration
Tell us what is in MerusCase 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 MerusCase holds
What is in it, how its records link, and where each piece would sit in Full data export. 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
Full data export is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.
With no product to configure, the set-up is custody, and the decisions are the firm’s. Someone there owns the export, knows where it is kept and can open it. Access needs restricting, because it contains every client’s affairs in one place with none of the old system’s security. The firm sets a destruction date from its retention obligations and decides how the next custodian will learn to use it.
What is agreed and set up
- Folder layout for tables, documents and reports
- What the key to tables, columns and identifiers records
- Where the copies are stored and who is custodian
- Who may open it, as approved by a partner
- Which look-ups staff must be able to do unaided
- Retention period and the date it is next reviewed
Questions
MerusCase to Full data export: what firms ask
Our court forms are built into MerusCase. What happens to them?
Forms already completed are saved on the case as PDFs and move as documents. The form library itself belongs to MerusCase, with its jurisdiction settings and merge fields. In the new system the firm uses that system’s forms or a forms service, and its own Word templates are rebuilt there.
Can archived cases come across?
Yes. Archived cases are still in the system and can be extracted with their documents and activity. They are kept out of the active lists in the new system by loading them as closed. The firm sets a cut-off if it does not want every year, and the count on each side is checked.
What about emails our staff never linked to a case?
Those are not part of any case, so they do not move with the case data. They remain in the mail account that was connected to MerusCase. If the firm wants old correspondence on the file, the time to link it is before the freeze, and fee earners are asked to do so for their open cases.
Does the copy in Full data export hold trust ledgers from MerusCase?
Yes. A trust transactions table; ledger reports can be kept as PDF beside it. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in MerusCase as at the export date.
Does everything in MerusCase have a place in Full data export?
Most of it does on paper. Custom fields and intake records 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 Full data export is kept as a readable archive, and you see which before the move.
What has to be decided before MerusCase is written out to Full data export?
Emails, the firm’s accounts and templates are exported with mapping, so each mapping is agreed with you first. Custom fields and intake records are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.
Other routes
Other routes from MerusCase and into Full data export
Other destinations from MerusCase
Other systems that move into Full data export
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.
MerusCase and Full data export are the names and marks of their owners, used here only to identify the two systems.
Moving from MerusCase to Full data export?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.