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

Data migration route

MerusCase to Neos migration

MerusCase is a cloud practice management system, and Neos 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. Notes: Carried across
  5. Calendar: Carried across
  6. Tasks: Carried across
  7. Emails: Carried with mapping
  8. Time and expenses: Carried with mapping
  9. Billing: Carried with mapping
  10. Templates: Carried with mapping
  11. Trust money: Confirmed in the analysis
  12. Custom fields: Confirmed in the analysis
  13. Intake: Confirmed in the analysis
ToNeosCloud
  1. Firm accounts: Kept as a readable archive
Readable archiveNo place in Neos
  • 6 carried
  • 4 mapped
  • 3 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from MerusCase to Neos

Each row is a kind of record MerusCase holds, whether Neos has a place for it, and what is planned. On this route six kinds of record carry across, four kinds need mapping, one kind has no place in Neos and is archived and three kinds are confirmed in the analysis.

Records in MerusCase and their place in Neos
RecordIn MerusCaseIn NeosWhat 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 placeCases by case type.Carried across
ContactsClients, other parties and referrersHeldSeparate contact and company lists, with duplicate removal.Has a placeParties, providers and case contacts. Contacts can be imported from CSV.Carried across
DocumentsFiles stored in or linked from the systemHeldUploaded or batch scanned, then linked to the case file.Has a placeCase Docs tab, organised in sub-tabs.Carried across
EmailsEmails saved to matters or to the storeHeldEmail accounts sync into the product and messages are linked to cases.Has a place in partEmails tagged to a case are held. Loading old mail is scoped in the analysis.Carried with mapping
NotesFile notes, matter notes and contact notesHeldCase notes, which can be merged into forms and documents.Has a placeCarried across
CalendarAppointments, court dates and deadlinesHeldEvents and deadlines, which can be attached to a case.Has a placeCase calendar entries.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldAssignments delegated to team members, with reminders.Has a placeLoaded as checklist items.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldTimers and time entries on case ledgers.Has a place in partTime can be held as value items. The treatment of old entries is confirmed in the analysis.Carried with mapping
BillingInvoices, payments and debtor balancesHeldInvoices, payments and electronic billing formats including LEDES.Has a place in partInvoices exist in Neos. Loading past invoices is confirmed in the analysis.Carried with mapping
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.No placeThe general ledger stays in QuickBooks.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeUser-defined fields are created on the relevant tab first.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldWord templates and PDF court forms that fill from the case.Has a place in partTemplates are rebuilt for Neos document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeIntakes tab. Simple intake imports from CSV are supported.Confirmed in the analysis

What the plans mean

Carried across
Neos has a place for this kind of record. It is loaded there and checked against MerusCase.
Carried with mapping
Neos 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
Neos has no place for it. It is exported in a format that opens without MerusCase 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

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 Neos. 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 Neos, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Neos 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 Neos 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

Neos expects personal injury data in its own tab structure, so loading a firm means deciding which tab each old record belongs on. Parties, insurance and counsel map directly from most injury systems. Money maps to value items. Anything the standard tabs lack becomes a user-defined field, which has to be created before the load.

  1. Every figure needs a value code

    Costs, medical bills, fees and settlement amounts are loaded as value items, and each carries a value code. The code list is agreed with the firm’s accounts staff first. A figure loaded under the wrong code is reported in the wrong place, so the list is tested on real cases before the bulk load.

  2. Lists are set up first

    Cases are loaded against case types, statuses and staff assignments that already exist in Neos. Those lists are set up, and the old system’s values tidied to match, before the trial load. Misspelt attorney names and unused case types in the source are cleaned out at the same stage.

  3. Documents go to sub-tabs

    Files land on the Case Docs tab under sub-tabs, which staff can view as a list or as folders. The old system’s folders or categories are mapped to a fixed set of sub-tabs. Without that, every personal habit of naming folders is reproduced and the folder view becomes hard to read.

  4. Reminders split two ways

    Neos fills its dashboards from checklists and case calendars. Old diary entries and tasks are sorted between them: dated appointments and court events to the calendar, and to-dos to the checklist. An item assigned to several people in the old system may need one named owner, and the firm chooses who.

  5. Assembly runs its own conversions

    Assembly migrates firms into Neos with its own team and tooling, and offers routes from self-service templates to a full conversion. Where the firm uses that service, outside help goes on the work around it: cleaning the source, checking the converted cases against the old system, and listing exceptions.

More about moving into Neos

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of Neos says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in MerusCase and checking each trial against MerusCase.

  1. Analysis

    We read what MerusCase holds and how its records link, then agree with you, field by field, where each piece will sit in Neos. Anything with no place there comes across as a note or stays behind, and you see which before the move.

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

  3. Trial load

    The data is loaded into Neos as a trial and checked against MerusCase: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in MerusCase are frozen for an agreed window, the data is collected a final time and Neos goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in MerusCase as at the cutover date. 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 toNeos

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

Loaded data is not yet a working system. The maker of Neos runs or arranges the set-up of its product, so this is what has to be decided and put in place in Neos, whoever does the work, before people rely on it from the first day.

Neos comes set up for injury work, so implementation is mostly choosing among its options and connecting the firm’s other tools. The lists that drive reporting are decided first, then checklists, then documents. Assembly provides its own implementation team, and the firm’s internal lead still has to make the decisions listed below.

Set-up decisions in Neos

  • Set case types, statuses and staff roles
  • Agree the value code list with accounts staff
  • Build checklists for each case type and stage
  • Create user-defined fields for data the tabs lack
  • Prepare document templates for the generation wizard
  • Connect Microsoft 365, QuickBooks and the phone system

Questions

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

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 Neos turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

What happens to records Neos has no place for?

On this route that is the firm’s accounts. They are exported from MerusCase 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 MerusCase data is loaded into Neos?

Emails, time entries, billing records and templates are carried with mapping, so each mapping is agreed with you first. Trust ledgers, 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.

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 Neos are the names and marks of their owners, used here only to identify the two systems.

Moving from MerusCase to Neos?

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

We reply within one business day.