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

Data migration route

MerusCase data to Microsoft SQL Server

MerusCase is a cloud practice management system, and Microsoft SQL Server is a database on a server the firm runs. 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.

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

What moves

What moves from MerusCase to Microsoft SQL Server

Each row is a kind of record MerusCase holds, whether Microsoft SQL Server 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.

Records in MerusCase and their place in Microsoft SQL Server
RecordIn MerusCaseIn Microsoft SQL ServerWhat 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 placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeldSeparate contact and company lists, with duplicate removal.Has a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeldUploaded or batch scanned, then linked to the case file.Has a place in partAs files in folders with an index table; storing files in the database is possible.Exported with mapping
EmailsEmails saved to matters or to the storeHeldEmail accounts sync into the product and messages are linked to cases.Has a place in partAs message files with an index table, or as rows of header fields.Exported with mapping
NotesFile notes, matter notes and contact notesHeldCase notes, which can be merged into forms and documents.Has a placeRows of text linked to matters and contacts.Exported in full
CalendarAppointments, court dates and deadlinesHeldEvents and deadlines, which can be attached to a case.Has a placeRows of appointments and key dates; nothing displays them as a calendar.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldAssignments delegated to team members, with reminders.Has a placeRows with assignee, due date and status.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldTimers and time entries on case ledgers.Has a placeTime and expense rows with rates and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeldInvoices, payments and electronic billing formats including LEDES.Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesHeld in partDescribed by the vendor as trust accounting tracking, on case ledgers.Has a placeTransactions and balances for look-up; it is not a trust accounting system.Exported in full
Firm accountsGeneral ledger, office account and payablesHeld in partOperating receivables are built in. Payables were not confirmed.Has a placeGeneral ledger journals and balances, where the source held them.Exported in full
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeAs added columns, or a table of field names and values.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldWord templates and PDF court forms that fill from the case.Has a place in partPrecedent files can be stored; automation does not run here.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeEnquiry rows, where the source recorded them.Confirmed in the analysis

What the plans mean

Exported in full
Microsoft SQL Server has a place for this kind of record. It is loaded there and checked against MerusCase.
Exported with mapping
Microsoft SQL Server 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 Microsoft SQL Server 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 Microsoft SQL Server 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

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

There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.

  1. Restored copy or rebuilt schema

    Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.

  2. No screens come with it

    A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.

  3. Documents sit beside the database

    Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.

  4. The edition follows the size

    A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.

  5. Backups and a test restore

    An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.

More about moving into Microsoft SQL Server

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.

  1. Analysis

    We read what MerusCase holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything MerusCase holds is in scope unless you take it out.

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

  3. Trial export

    The data is written to Microsoft SQL Server 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.

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

Step 1 of 5: Start with the route

Moving fromMerusCase
Moving toMicrosoft SQL Server

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 Microsoft SQL Server. 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

Structure, permissions and handover

Microsoft SQL Server 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.

Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.

What is agreed and set up

  • Server, instance and edition agreed with the IT provider
  • Read-only logins and roles for named staff
  • Views for matter, ledger, time and document look-ups
  • Backup schedule and who tests a restore
  • Plain names and descriptions for tables and columns
  • Excel or Power BI connected for reporting

Questions

MerusCase to Microsoft SQL Server: 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 Microsoft SQL Server hold trust ledgers from MerusCase?

Yes. Transactions and balances for look-up; it is not a trust accounting system. 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 Microsoft SQL Server?

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 Microsoft SQL Server is kept as a readable archive, and you see which before the move.

What has to be decided before MerusCase is written out to Microsoft SQL Server?

Documents, emails 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.

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

Moving from MerusCase to Microsoft SQL Server?

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

We reply within one business day.