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

Data migration route

MerusCase to Smokeball migration

MerusCase is a cloud practice management system, and Smokeball is one that runs on the desktop and keeps its data in its maker’s cloud. Both run a whole practice, so this is a full move, and the financial records set the timetable.

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

What moves

What moves from MerusCase to Smokeball

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

Records in MerusCase and their place in Smokeball
RecordIn MerusCaseIn SmokeballWhat 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 placeEach needs a Smokeball matter type; leads import alongside matters.Carried across
ContactsClients, other parties and referrersHeldSeparate contact and company lists, with duplicate removal.Has a placeMatter roles import on the Grow and Prosper+ plans only.Carried across
DocumentsFiles stored in or linked from the systemHeldUploaded or batch scanned, then linked to the case file.Has a placeFiles and folders import into a matter with the folder structure kept.Carried across
EmailsEmails saved to matters or to the storeHeldEmail accounts sync into the product and messages are linked to cases.Has a placeKept in the matter with other files.Carried across
NotesFile notes, matter notes and contact notesHeldCase notes, which can be merged into forms and documents.Has a placeAs memos; not importable on the Bill plan.Carried across
CalendarAppointments, court dates and deadlinesHeldEvents and deadlines, which can be attached to a case.Has a placeCalendar events and critical dates; plan limits apply.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldAssignments delegated to team members, with reminders.Has a placeNot importable on the Bill plan.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldTimers and time entries on case ledgers.Has a placeUnbilled time, fee and expense entries, with activity codes.Carried across
BillingInvoices, payments and debtor balancesHeldInvoices, payments and electronic billing formats including LEDES.Has a placeInvoices and billed invoice entries are on the import list.Carried across
Trust moneyTrust or client account ledgers and balancesHeld in partDescribed by the vendor as trust accounting tracking, on case ledgers.Has a place in partMatter account balances load as opening balances; past transactions are not on the import list.Carried with mapping
Firm accountsGeneral ledger, office account and payablesHeld in partOperating receivables are built in. Payables were not confirmed.No placeNo general ledger; the firm’s books stay in an accounting package.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a place in partValues need a matching field in the matter type’s layouts.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldWord templates and PDF court forms that fill from the case.Has a placeFirm precedents are rebuilt as Smokeball templates.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeLeads are a record type of their own and can be converted to matters.Confirmed in the analysis

What the plans mean

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

The whole practice moves, accounts included.

A move between two practice management systems is the widest kind there is. MerusCase and Smokeball 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 Smokeball 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

Smokeball has a data import tool that reads spreadsheets of staff, contacts, matters, balances, unbilled time, invoices, memos, tasks and calendar events. Some of those are only available on the higher plans. Documents are brought in separately, with their folders. Before the first trial, every incoming matter is given a Smokeball matter type, since nothing else about the matter can be placed without one.

  1. Every matter needs a type

    Smokeball’s matter types are specific to an area of law and a state or jurisdiction, and each brings its own fields. The old system’s matter types are mapped to them one by one. It is worth getting right the first time: changing a matter’s type later can drop the details held in layouts the new type does not have.

  2. The plan decides what loads

    Matter roles, tags, critical dates and archive details import only on the Grow and Prosper+ plans. Memos, tasks and calendar events do not import on the Bill plan. The firm’s plan is confirmed before the mapping is written, so nobody maps the other side’s solicitor to a role that the subscription cannot hold.

  3. Leave auto-numbering until after

    Smokeball’s guidance for firms still bringing matters in is to wait before setting up automatic Internal References. Imported matters arrive with the numbers they already had. Once the load is accepted, the reference format and the counter’s starting number are set so the first new matter follows on from the last old one.

  4. Documents arrive by folder

    Importing a folder into a matter keeps its subfolders, and default folders can also be defined per matter type. The firm decides which wins where they differ: the old structure as it was, or its new standard layout with old folders mapped into it.

  5. An opening balance per matter

    Matter account balances are on the import list, along with unbilled time and expenses, invoices and billed invoice entries. Past trust transactions are not on that list. The trust position is therefore loaded as an opening balance for each matter and rehearsed on a full trial, with the transaction history kept in the old system.

More about moving into Smokeball

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.

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

  4. Cutover

    Changes in MerusCase are frozen for an agreed window, the data is collected a final time and Smokeball 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

Step 1 of 5: Start with the route

Moving fromMerusCase
Moving toSmokeball

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

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

A Smokeball set-up is partly on the firm’s PCs and partly in firm settings. The desktop app and its Word and Outlook add-ins go on each Windows machine. In settings, the firm chooses the matter types it will use, defines default folders for each and sets its numbering. Trust accounts and the accounting connection are configured before the first invoice is raised.

Set-up decisions in Smokeball

  • Matter types in use, with default document folders for each
  • Internal Reference format and the starting number for new matters
  • Trust account details and the link to the accounting package
  • Staff roles and permissions, including who sees billing and trust
  • Firm precedents and letterhead rebuilt as Smokeball templates
  • Desktop app, Word and Outlook add-ins on every PC

Questions

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

In part. Matter account balances load as opening balances; past transactions are not on the import list. The analysis sets out which trust records have a place in Smokeball and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.

What happens to records Smokeball 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 Smokeball?

Trust ledgers 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.

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

Moving from MerusCase to Smokeball?

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

We reply within one business day.