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

Data migration route

esiLaw to Rocket Matter migration

esiLaw is a desktop accounting and billing system, and Rocket Matter is a cloud practice management system. The financial records lead: balances and open items move, and the matters in Rocket Matter are built around them.

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

What moves

What moves from esiLaw to Rocket Matter

Each row is a kind of record esiLaw holds, whether Rocket Matter has a place for it, and what is planned. On this route six kinds of record carry across, two kinds need mapping and six kinds are confirmed in the analysis.

Records in esiLaw and their place in Rocket Matter
RecordIn esiLawIn Rocket MatterWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClient numbers with optional three-character matter numbers.Has a placeMatter File # and matter name are required on import.Carried across
ContactsClients, other parties and referrersHeldHas a placeImported as clients or as other contact types.Carried across
DocumentsFiles stored in or linked from the systemHeld in partThe help centre has a section on documents and document management.Has a placeNative storage, or a linked OneDrive, Dropbox, Box or NetDocuments account.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partEmails can be filed to matters; it does not hold whole mailboxes.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partShared calendaring is listed for the product under its Unity name.Has a placeCarried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTime and fees.Has a placeUnbilled time and expenses load from a financial import sheet, keyed to the matter.Carried across
BillingInvoices, payments and debtor balancesHeldBilling, payments, receipts and deposits.Has a place in partOpen balances are supported; how much invoice history loads is confirmed in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldTrust ledgers by client, including term trust, built to law society rules.Has a placeBank accounts are created first; ledger history depth is agreed in the analysis.Carried across
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger, payables, bank reconciliation and payroll cheques.Has a place in partNextGen has a chart of accounts and journals; prior-year ledger detail is confirmed first.Carried with mapping
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCustom fields and custom pages on contacts and matters.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partWord merge templates are rebuilt with the product’s own merge fields.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a place in partIntake forms exist; loading open leads is confirmed in the analysis.Confirmed in the analysis

What the plans mean

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

Time, bills and balances move. How much history is a decision.

Coming from an accounting or billing system, the records that count are balances: unbilled time, unpaid invoices, client funds, the ledger. A practice management system takes these as opening positions on a matter. So every client and job in esiLaw needs a matter to land on, and the first piece of work is building that matter list, often from client and project codes that were never meant to be matter numbers.

How much history to bring is the main choice. Paid invoices from years ago can be loaded as records, kept as PDF copies on the matter, or left in a read-only copy of esiLaw. Most firms bring open items and a period of history, and keep the rest as reports. Opening balances in Rocket Matter are agreed to the trial balance and aged debtors from esiLaw as at the cutover date, and that load is rehearsed before it is done for real.

esiLaw runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Rocket Matter is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.

Where the data is now

esiLaw is the firm’s books, so leaving it is a trust and general ledger cutover with client and matter records attached. Canadian law society rules decide what must reconcile on the day: the trust listing, the bank reconciliation and the client ledgers. Those three are agreed in esiLaw at a month end, then loaded and checked in the new system before anyone posts to it.

  1. Matters are optional here

    A firm can run esiLaw with client numbers only, or with a three-character matter number after a client number of up to nine characters. Without matters, each new job gets a new client number, so one person may hold several. On the way out those are grouped under one client where they can be identified, with a matter for each.

  2. Closing needs a zero balance

    A client cannot be closed while it has a balance or unposted transactions, and closing records a date of destruction. Files that are finished but held open by a few cents are worth looking for. They are listed during clean-up so the firm can clear them before the data is taken.

  3. Term trust sits apart

    Money placed on term deposit for a client has its own listing report in esiLaw. It is still client money and still has to agree at cutover. Each term deposit is loaded against the right client and its own bank account, not mixed into the pooled trust account.

  4. Three names, one product

    The same product has been ESILAW, esiLaw 360 and, since December 2023, Unity Accounting. A firm that stopped updating before the rename is still on an esiLaw release. The version is recorded first, because it tells us where the company data is kept and how a copy can be taken.

  5. Payroll and cheques

    Payroll cheques and vendor payments are posted in the general side of the program. Practice management systems rarely take payroll. If the destination has no general ledger, payables and payroll history go to the firm’s accounting package as balances, and the accountant signs off the opening position.

More about moving off esiLaw

Where it is going

This describes loading into Rocket Matter NextGen, the platform the vendor’s website now presents. Its import runs in a fixed order: contacts, then matters, then time, expenses and balances. The vendor’s import sheets show what each record must carry. Most of the preparation is giving every matter a file number and getting the accounting set-up finished before any financial record goes in.

  1. A file number on every matter

    Matter File # and matter name are the two required fields. The file number is also the key that time, expenses and balances are matched to on the way in. Source matters with no number, or with numbers reused across clients, are given clean ones before the trial load and the old value is kept in a custom field.

  2. Clients and address-book contacts

    A contact is either a client, who can have matters, or an address-book contact such as an opposing lawyer or an expert. Source systems that hold everyone in one list need each record classified. A person who is a client on one matter and a witness on another is loaded once, as a client.

  3. Accounting set-up comes first

    Timekeepers, matter owners, bank accounts and the chart of accounts must exist before financial data is imported, and the client and matter records must already be in place. The trial load follows that order. Time recorded by people who have left still needs a timekeeper to belong to, so former staff are added before their entries are loaded.

  4. Pick the document store early

    Documents can sit in native storage or in a linked OneDrive, Dropbox, Box or NetDocuments account. With a linked account, the system creates a folder for each matter, named from the file number, client and matter name. Changing that pattern later only affects new matters, so it is settled before the load.

  5. One ledger of record

    NextGen has its own chart of accounts, journal entries and bank reconciliation, and it can also sync with QuickBooks Online from a chosen start date. A firm should run one of them as its books. That decision shapes how opening trust and debtor balances are entered, and the accountant is part of it.

More about moving into Rocket Matter

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 esiLaw holds and how its records link, then agree with you, field by field, where each piece will sit in Rocket Matter. 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 esiLaw, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Rocket Matter as a trial and checked against esiLaw: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in esiLaw are frozen for an agreed window, the data is collected a final time and Rocket Matter 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. esiLaw 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 esiLaw 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 fromesiLaw
Moving toRocket Matter

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 esiLaw holds

    What is in it, how its records link, and where each piece would sit in Rocket Matter. 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 Rocket Matter

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

Beyond the data, a firm starting on Rocket Matter has a set of choices that are awkward to change once people are billing. Who the timekeepers and matter owners are, how matters are numbered, which bank accounts exist and whether the books run inside the product or in QuickBooks Online all need an answer before go-live. Matter templates and Word merge documents are then built on top.

Set-up decisions in Rocket Matter

  • Timekeepers, matter owners and the rates each one bills at
  • Matter File number format and matter templates by work type
  • Bank accounts, chart of accounts and the QuickBooks Online decision
  • Custom fields and custom pages for contacts and matters
  • Document storage choice and the matter folder naming pattern
  • Word merge templates, invoice layouts and intake forms

Questions

esiLaw to Rocket Matter: what firms ask

Is esiLaw the same as Unity Accounting?

Yes. Dye & Durham renamed esiLaw to Unity Accounting on 9 December 2023 and said the features stayed the same. An installed copy that was updated after that date shows the Unity name. A copy that was not still says esiLaw. The name on the screen does not change what kind of records the firm holds.

Will our trust records satisfy the law society after the move?

The records have to show an unbroken trail, so the cutover is done at a month end with a completed reconciliation. Client by client, the closing trust listing in esiLaw must match the opening listing in the new system. Afterwards the old company file is kept read only so earlier months can still be produced.

Can unbilled time and disbursements come across?

Yes, as unbilled items against the matter, so the next bill can pick them up. Time carries the lawyer, date, hours, rate and description. Disbursements carry their tax treatment, which is checked with care for Canadian firms because GST, HST and provincial tax codes are set up differently in each system.

Do trust balances in esiLaw have a place in Rocket Matter?

Yes. Rocket Matter keeps trust ledgers. Bank accounts are created first; ledger history depth is agreed in the analysis. Balances are loaded by matter and agreed to the trust report from esiLaw 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 esiLaw have a place in Rocket Matter?

Most of it does on paper. Emails, notes, tasks, custom fields, templates 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 Rocket Matter is kept as a readable archive, and you see which before the move.

What has to be decided before esiLaw data is loaded into Rocket Matter?

Billing records and the firm’s accounts are carried with mapping, so each mapping is agreed with you first. Emails, notes, tasks, custom fields, templates 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

esiLaw and Rocket Matter are the names and marks of their owners, used here only to identify the two systems.

Moving from esiLaw to Rocket Matter?

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

We reply within one business day.