Data migration route
MerusCase to Actionstep migration
MerusCase and Actionstep are each a cloud practice management system. Both run a whole practice, so this is a full move, and the financial records set the timetable.
MerusCaseCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Emails: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Trust money: Carried across
- Firm accounts: Carried across
- Billing: Carried with mapping
- Templates: Carried with mapping
- Custom fields: Confirmed in the analysis
- Intake: Confirmed in the analysis
ActionstepCloud- 10 carried
- 2 mapped
- 2 to confirm
What moves
What moves from MerusCase to Actionstep
Each row is a kind of record MerusCase holds, whether Actionstep has a place for it, and what is planned. On this route ten kinds of record carry across, two 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 placeImported with a matter type, a status and the old number as File Reference. | Carried across |
| ContactsClients, other parties and referrers | HeldSeparate contact and company lists, with duplicate removal. | Has a placeImported first, then linked to matters through a parties import. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldUploaded or batch scanned, then linked to the case file. | Has a placeFiled in matter folders; not part of the spreadsheet import tool. | Carried across |
| EmailsEmails saved to matters or to the store | HeldEmail accounts sync into the product and messages are linked to cases. | Has a placeSaved emails sit on the matter they were filed to. | Carried across |
| NotesFile notes, matter notes and contact notes | HeldCase notes, which can be merged into forms and documents. | Has a placeThe import tool has a file notes template. | Carried across |
| CalendarAppointments, court dates and deadlines | HeldEvents and deadlines, which can be attached to a case. | Has a placeAppointments have a place; the standard import templates do not cover them. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldAssignments delegated to team members, with reminders. | Has a placeThe import tool has a tasks template. | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTimers and time entries on case ledgers. | Has a placeTime entries and disbursements each have an import template. | Carried across |
| BillingInvoices, payments and debtor balances | HeldInvoices, payments and electronic billing formats including LEDES. | Has a place in partUnpaid invoices load as accounts receivable; older invoice history is confirmed in the analysis. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | Held in partDescribed by the vendor as trust accounting tracking, on case ledgers. | Has a placeTrust balances load per matter through the trust accounts import. | Carried across |
| Firm accountsGeneral ledger, office account and payables | Held in partOperating receivables are built in. Payables were not confirmed. | Has a placeOpening balances are entered against the general ledger, or the books stay in Xero. | Carried across |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeData collections are built per matter type before values are loaded. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldWord templates and PDF court forms that fill from the case. | Has a placeRebuilt as Actionstep templates with its merge fields. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a place | Confirmed in the analysis |
What the plans mean
- Carried across
- Actionstep has a place for this kind of record. It is loaded there and checked against MerusCase.
- Carried with mapping
- Actionstep 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
The whole practice moves, accounts included.
A move between two practice management systems is the widest kind there is. MerusCase and Actionstep each keep matters, contacts, documents, time and money in one place, but no two systems link those records the same way. In one, a client is a contact with a role on the matter. In another, every matter carries its own client card. Most of the analysis goes into those links, because a matter that arrives without its client or its documents is the first thing staff find.
The financial side decides the dates. Unbilled time, debtor balances and trust ledgers have to agree with MerusCase’s own reports as at one day, and a new system usually wants them as opening balances, not as years of transactions. So the firm decides early how much history comes across as live records and how much is kept as reports. Matter and document loads can be repeated until they are right. The money is loaded once.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of MerusCase depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to MerusCase is kept running until the checks on Actionstep are finished.
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 Actionstep
Actionstep has its own import tool, which takes spreadsheets in a set order: contacts, then matters, then the parties that join them. Tasks, time entries, trust balances, disbursements, unpaid invoices and file notes follow once the matters exist. None of it can start until the matter types, participant types and data collections have been built, because every imported row refers to them.
Matter types before any data
A matter’s type decides its workflow steps, its document folders, which party roles are available and which custom data it carries. So the first job is deciding how the old system’s matter types map to Actionstep’s, and building any that are missing. An imported matter also needs a step to sit at, usually the one closest to its old status.
Old numbers go to File Reference
Actionstep assigns its own Matter ID to each imported matter. The number the firm has always used goes into the File Reference field, which the quick search reads from the start of the reference. Staff can keep finding matters by the number printed on old letters and file covers.
Check before anyone edits
The import tool can roll back a load, but only while the imported records are untouched. Once someone edits them, the rollback no longer works. Trial loads are therefore checked straight away against the old system, and nobody outside the project works in the new records until the counts and balances agree.
Folders come from the matter type
Default document folders are set per matter type. There is no single folder list that applies across all matters. Before documents are loaded, the old folder names are mapped to the folders each matter type will have, so a conveyancing file and a litigation file each open with the layout the firm designed for them.
Opening balances can be locked
Trust balances load against matters, unpaid invoices load as accounts receivable, and general ledger opening balances are entered on the accounts list. An opening balance that has been locked cannot be edited afterwards. The figures are rehearsed on a trial load and agreed with the firm’s accountant before the lock is applied in the live system.
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 MerusCase holds and how its records link, then agree with you, field by field, where each piece will sit in Actionstep. 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 MerusCase, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Actionstep as a trial and checked against MerusCase: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in MerusCase are frozen for an agreed window, the data is collected a final time and Actionstep 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. MerusCase 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 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 Actionstep. 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 Actionstep
Loaded data is not yet a working system. This is what NewLaw sets up in Actionstep, beyond the migration, so that people can work in it from the first day.
Most of the work in an Actionstep set-up is design. The firm decides what its matter types are, what steps each one moves through and what happens at each step. Templates, billing and trust settings are then built around those matter types. People are trained on their own workflows, since a generic demonstration looks little like the firm’s finished system.
Set-up decisions in Actionstep
- Matter types, with workflow steps and default document folders
- Participant types and data collections for each matter type
- Document and email templates rebuilt with Actionstep merge fields
- Trust accounts, chart of accounts and the optional Xero link
- System roles and data permissions for each group of staff
- Outlook add-in, divisions and the firm’s billing preferences
Questions
MerusCase to Actionstep: 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.
Do trust balances in MerusCase have a place in Actionstep?
Yes. Actionstep keeps trust ledgers. Trust balances load per matter through the trust accounts import. Balances are loaded by matter and agreed to the trust report from MerusCase as at the cutover date. That load cannot be re-run the way a document load can, so it is rehearsed on a full trial load first.
Does everything in MerusCase have a place in Actionstep?
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 Actionstep is kept as a readable archive, and you see which before the move.
What has to be decided before MerusCase data is loaded into Actionstep?
Billing records and templates are carried with mapping, so each mapping is agreed with you first. Custom fields and intake records 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 MerusCase and into Actionstep
Other destinations from MerusCase
Other systems that move into Actionstep
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 Actionstep are the names and marks of their owners, used here only to identify the two systems.
Moving from MerusCase to Actionstep?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.