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

Data migration route

esiLaw to Clio Manage migration

esiLaw is a desktop accounting and billing system, and Clio Manage is a cloud practice management system. The financial records lead: balances and open items move, and the matters in Clio Manage 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 with mapping
  6. Billing: Carried with mapping
  7. Trust money: Carried with mapping
  8. Emails: Confirmed in the analysis
  9. Notes: Confirmed in the analysis
  10. Tasks: Confirmed in the analysis
  11. Custom fields: Confirmed in the analysis
  12. Templates: Confirmed in the analysis
  13. Intake: Confirmed in the analysis
ToClio ManageCloud
  1. Firm accounts: Kept as a readable archive
Readable archiveNo place in Clio Manage
  • 4 carried
  • 3 mapped
  • 6 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from esiLaw to Clio Manage

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

Records in esiLaw and their place in Clio Manage
RecordIn esiLawIn Clio ManageWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClient numbers with optional three-character matter numbers.Has a placeImported from a matters template, after contacts.Carried across
ContactsClients, other parties and referrersHeldHas a placePeople and companies, with related contacts linked to matters by a separate template.Carried across
DocumentsFiles stored in or linked from the systemHeld in partThe help centre has a section on documents and document management.Has a placeFiled under the matter; Clio scopes document migration separately from data.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeHeld as communications on the matter, with phone logs.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeMatter notes and contact notes each have a template.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partShared calendaring is listed for the product under its Unity name.Has a placeCalendar events have a migration template.Carried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeTasks have a migration template.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTime and fees.Has a place in partUnbilled time entries load; billed time entries do not, by Clio’s migration guide.Carried with mapping
BillingInvoices, payments and debtor balancesHeldBilling, payments, receipts and deposits.Has a place in partAn outstanding balance loads as one line per matter; past invoices do not.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldTrust ledgers by client, including term trust, built to law society rules.Has a place in partA trust balance loads as one line per matter or contact; past transactions do not.Carried with mapping
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger, payables, bank reconciliation and payroll cheques.No placeNot in Clio Manage. Books sit in a linked accounting package, or in Clio Accounting where Clio offers it.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCreated first, then filled from the custom field templates.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a placeRebuilt as Clio document templates with its merge fields.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeLeads and intake forms belong in Clio Grow.Confirmed in the analysis

What the plans mean

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

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 Clio Manage 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. Clio Manage 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

Clio Manage is loaded through its migration templates, one spreadsheet per kind of record, imported in a fixed order with contacts first. Clio’s own migration guide is plain about the limit: balances come across, financial history does not. So a load into Clio is planned as records plus opening positions, with the old system kept for the history behind them.

  1. Matters link by client name

    The matters template ties each matter to its client by an exact match on first name, last name or company name. A client spelt two ways in the old system becomes two contacts, or a matter assigned to an unknown client. This is why contact clean-up is finished before the first trial load, not after it.

  2. Decide the numbering scheme first

    Clio numbers imported matters itself unless the account is set to manual numbering, in which case the old number is supplied in the template. That setting and the firm’s preferred scheme are decided before any matter is loaded. The Client Reference field is available for an old file number the firm still wants to see.

  3. Balances, one line each

    Under Clio’s standard migration, an outstanding balance arrives as one line per matter and a trust balance as one line per matter or contact. Past invoices, billed time, payments and trust transactions are listed as data that cannot be migrated. The trust total is reconciled against the old system’s closing report on the trial load.

  4. Custom fields must exist

    Matter and contact custom fields are created in Clio before their values are imported, each with a field type. Accounts set up for a particular practice area come with preconfigured fields and matter templates, which affects the mapping. We compare those with the old system’s fields and add only what is missing.

  5. Rates and permissions by hand

    Billable rates for users, clients and matters are not part of an import. Neither are user permissions or settings. They are entered in Clio during set-up from a schedule the firm confirms, and a sample of imported unbilled time is checked against that schedule before the trial load is signed off.

More about moving into Clio Manage

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 Clio Manage. 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 Clio Manage 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 Clio Manage 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 toClio Manage

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 Clio Manage. 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 Clio Manage

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

Much of a Clio Manage set-up is firm-wide settings. The numbering scheme, practice areas, matter stages, billing preferences and trust accounts apply to everyone, so they are agreed once and early. Trust and accounting features are not the same in every country Clio sells in, so the firm’s own region is checked first. Document templates and custom fields follow. Email and document integrations are then installed for each user and tested on a real matter.

Set-up decisions in Clio Manage

  • Matter numbering scheme, practice areas and matter stages
  • Custom fields for matters and contacts, by practice area
  • Document templates with merge fields, uploaded from Word or PDF
  • Billing settings, user and client rates, and trust accounts
  • Roles and permissions for each user
  • Outlook add-in, Clio Drive and the accounting connection

Questions

esiLaw to Clio Manage: 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 Clio Manage?

In part. A trust balance loads as one line per matter or contact; past transactions do not. The analysis sets out which trust records have a place in Clio Manage 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 Clio Manage has no place for?

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

Time entries, billing records and trust ledgers 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 Clio Manage are the names and marks of their owners, used here only to identify the two systems.

Moving from esiLaw to Clio Manage?

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

We reply within one business day.