Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

MerusCase to Gladiate migration

MerusCase is a cloud practice management system, and Gladiate is a cloud case management system for personal injury work. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.

FromMerusCaseCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Calendar: Carried across
  5. Tasks: Carried across
  6. Templates: Carried with mapping
  7. Emails: Confirmed in the analysis
  8. Notes: Confirmed in the analysis
  9. Time and expenses: Confirmed in the analysis
  10. Billing: Confirmed in the analysis
  11. Trust money: Confirmed in the analysis
  12. Firm accounts: Confirmed in the analysis
  13. Custom fields: Confirmed in the analysis
  14. Intake: Confirmed in the analysis
ToGladiateCloud
  • 5 carried
  • 1 mapped
  • 8 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from MerusCase to Gladiate

Each row is a kind of record MerusCase holds, whether Gladiate has a place for it, and what is planned. On this route five kinds of record carry across, one kind needs mapping and eight kinds are confirmed in the analysis.

Records in MerusCase and their place in Gladiate
RecordIn MerusCaseIn GladiateWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases, with fields that depend on the case type. Finished cases are archived.Has a placePersonal injury cases.Carried across
ContactsClients, other parties and referrersHeldSeparate contact and company lists, with duplicate removal.Has a placeClients, leads and referral sources.Carried across
DocumentsFiles stored in or linked from the systemHeldUploaded or batch scanned, then linked to the case file.Has a placeFiled to the firm’s folder structure.Carried across
EmailsEmails saved to matters or to the storeHeldEmail accounts sync into the product and messages are linked to cases.To be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesHeldCase notes, which can be merged into forms and documents.To be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldEvents and deadlines, which can be attached to a case.Has a placeEvents sync with Outlook and Google Calendar.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldAssignments delegated to team members, with reminders.Has a placeTasks and task plans.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldTimers and time entries on case ledgers.To be confirmedConfirmed in the analysis
BillingInvoices, payments and debtor balancesHeldInvoices, payments and electronic billing formats including LEDES.To be confirmedConfirmed in the analysis
Trust moneyTrust or client account ledgers and balancesHeld in partDescribed by the vendor as trust accounting tracking, on case ledgers.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeld in partOperating receivables are built in. Payables were not confirmed.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedTo be confirmedConfirmed in the analysis
TemplatesPrecedents, document templates and automationHeldWord templates and PDF court forms that fill from the case.Has a place in partFirm templates are set up again in Gladiate. Old templates are not converted.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeLeads and client sign-up.Confirmed in the analysis

What the plans mean

Carried across
Gladiate has a place for this kind of record. It is loaded there and checked against MerusCase.
Carried with mapping
Gladiate 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

Matters become cases. The ledgers need a home.

Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Gladiate. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.

Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from MerusCase has to be given a case type in Gladiate, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Gladiate is exported as reports and ledgers the firm can open without MerusCase, and kept as the record of what was billed and held.

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 Gladiate are finished.

Where the data is now

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving off MerusCase

Where it is going

Gladiate is a destination for personal injury firms, and what it expects is injury data: a client, an incident, coverage, providers and a case status. Loading a firm into it means shaping the old system’s records into that pattern and preparing the templates, task plans and folder structure that the vendor’s onboarding asks each firm to supply.

  1. Injury fields come first

    Coverage, liability and medical details are what the product is designed to put in front of staff. In the old system they may be in custom fields, notes or a spreadsheet. They are pulled into columns during the analysis, so a loaded case shows its insurer and policy details and not an empty panel.

  2. Templates and task plans

    The vendor’s onboarding has each firm set up its own document templates, task plans, litigation deadlines and questionnaires. These are prepared from what the firm uses now. Merge fields in old templates are replaced with Gladiate’s, and task plans are written down stage by stage before anyone builds them.

  3. A folder structure per case

    Documents are filed in a folder structure the firm defines. The old system’s folders or categories are mapped to it once, and every case is loaded to the same pattern. Files with no clear category go to a holding folder on the case and are listed, not scattered.

  4. What it may not hold

    Time records, invoices and trust ledgers are not described on the vendor’s public pages. A firm that needs those carried over has it confirmed in the analysis. If there is no place for them, balances stay in the accounting package and the detailed history is kept in the old system, read only.

More about moving into Gladiate

How NewLaw runs it

Four steps, in this order.

No financial cutover is planned on this route, so a load can be run again until it is right. If the analysis finds financial records with a place in Gladiate, they get a rehearsed cutover of their own.

  1. Analysis

    We read what MerusCase holds and how it is organised, then agree with you where each kind of record will sit in Gladiate. Anything with no place there stays behind or is archived, and you see which before the move.

  2. 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.

  3. Trial load

    A trial is loaded into Gladiate and checked against MerusCase: 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.

  4. Cutover

    After a short freeze on changes in MerusCase, a final pass over a weekend picks up what changed since the trial. If the analysis found financial records to move, their cutover is rehearsed on a full trial load first. 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

Step 1 of 5: Start with the route

Moving fromMerusCase
Moving toGladiate

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what MerusCase holds

    What is in it, how its records link, and where each piece would sit in Gladiate. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  3. 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 Gladiate

Loaded data is not yet a working system. This is what NewLaw sets up in Gladiate, beyond the migration, so that people can work in it from the first day.

Gladiate is delivered ready for injury work, so set-up is about making it the firm’s own. The vendor’s onboarding covers templates, task plans, folder structure, litigation deadlines and client questionnaires. Each of those is a decision the firm has to make, and it goes faster when current practice has been written down beforehand.

Set-up decisions in Gladiate

  • Set up and test the firm’s document templates
  • Write task plans for each stage of a case
  • Agree one folder structure for case documents
  • Enter litigation deadlines for the firm’s jurisdictions
  • Prepare client questionnaires, surveys and scheduled case updates
  • Connect Outlook or Google calendars for two-way sync

Questions

MerusCase to Gladiate: 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 Gladiate?

That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in MerusCase before the plan is fixed. If Gladiate turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

Does everything in MerusCase have a place in Gladiate?

Most of it does on paper. Emails, notes, time entries, billing records, trust ledgers, the firm’s accounts, 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 Gladiate is kept as a readable archive, and you see which before the move.

What has to be decided before MerusCase data is loaded into Gladiate?

Templates are carried with mapping, so each mapping is agreed with you first. Emails, notes, time entries, billing records, trust ledgers, the firm’s accounts, custom fields and intake records are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.

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.

How we do itDiscovery to rollout, step by step

MerusCase and Gladiate are the names and marks of their owners, used here only to identify the two systems.

Moving from MerusCase to Gladiate?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.