Data migration route
esiLaw to Centerbase migration
esiLaw is a desktop accounting and billing system, and Centerbase is a cloud practice management system. The financial records lead: balances and open items move, and the matters in Centerbase are built around them.
- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Calendar: Carried across
- Time and expenses: Carried across
- Billing: Carried across
- Trust money: Carried across
- Firm accounts: Carried across
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
- Intake: Confirmed in the analysis
CenterbaseCloud- 8 carried
- 6 to confirm
What moves
What moves from esiLaw to Centerbase
Each row is a kind of record esiLaw holds, whether Centerbase has a place for it, and what is planned. On this route eight kinds of record carry across and six kinds are confirmed in the analysis.
| Record | In esiLaw | What is planned | |
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldClient numbers with optional three-character matter numbers. | Has a placeLoaded under their client, with practice-specific custom fields. | Carried across |
| ContactsClients, other parties and referrers | Held | Has a placeClients, related parties and prospects. | Carried across |
| DocumentsFiles stored in or linked from the system | Held in partThe help centre has a section on documents and document management. | Has a placeInto Document Storage, or left in a connected NetDocuments, iManage or SharePoint store. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partEmails saved to matters; mailboxes stay in Microsoft 365. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partShared calendaring is listed for the product under its Unity name. | Has a place | Carried across |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a place | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime and fees. | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | HeldBilling, payments, receipts and deposits. | Has a placeThe vendor says billing history can be migrated; the depth is set in the analysis. | Carried across |
| Trust moneyTrust or client account ledgers and balances | HeldTrust ledgers by client, including term trust, built to law society rules. | Has a placeMultiple trust and retainer accounts per matter or client. | Carried across |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral ledger, payables, bank reconciliation and payroll cheques. | Has a placeGeneral ledger with chart of accounts; opening trial balance agreed with the accountant. | Carried across |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeCreated and placed on page layouts before records are loaded. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partTemplates are rebuilt to merge Centerbase client and matter data. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a placeEnquiries are held as Potential New Client records; loading open ones is confirmed in the analysis. | Confirmed in the analysis |
What the plans mean
- Carried across
- Centerbase has a place for this kind of record. It is loaded there and checked against esiLaw.
- 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 Centerbase 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. Centerbase 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
Leaving esiLaw
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in Centerbase
Centerbase takes practice, billing, trust and accounting data together, so loading a firm into it is a finance project as much as a matter load. Clients come first because matters inherit from them. The chart of accounts, bank accounts and accounting basis are fixed before balances go in. Because the product is configured per firm, the fields and layouts are designed before the trial load, not after.
Clients carry the billing rules
Billing arrangements, rates and accounting preferences are held on the client and passed to its matters. Source systems that create a fresh client for every matter leave duplicates behind. Those are merged during clean-up, so that each real client exists once and its terms are set in one place.
The ledger comes too
Centerbase has a full general ledger and runs on a cash or accrual basis. A firm arriving from a billing system with QuickBooks beside it is consolidating two sets of records. The accountant decides the basis and the opening date, and the trial balance loaded is agreed to the old books.
Trust and retainers are separate
A matter can hold multiple trust and retainer accounts. Source systems often blur the two, recording an advance on fees as trust or the reverse. Each balance is classified before loading, and client-level funds that were never tied to a matter are assigned to one or held at client level.
Decide the document home
Documents can go into built-in Document Storage, or stay in NetDocuments, iManage or SharePoint and be connected. Centerbase can create a standard folder structure when a matter is opened. That structure is agreed first, so migrated documents are filed into the same folders that new matters will get.
Fields are designed, not assumed
With unlimited custom fields, nearly every source field can have a home. That is a reason for restraint. Each one must be created and placed on a layout, and a page crowded with unused fields slows people down. The firm chooses which fields earn a place and which become a note.
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.
Analysis
We read what esiLaw holds and how its records link, then agree with you, field by field, where each piece will sit in Centerbase. Anything with no place there comes across as a note or stays behind, and you see which before the move.
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.
Trial load
The data is loaded into Centerbase 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.
Cutover
Changes in esiLaw are frozen for an agreed window, the data is collected a final time and Centerbase 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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what esiLaw holds
What is in it, how its records link, and where each piece would sit in Centerbase. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- 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 Centerbase
Loaded data is not yet a working system. This is what NewLaw sets up in Centerbase, beyond the migration, so that people can work in it from the first day.
Setting up Centerbase is largely configuration. Bill templates, rate tables and the pre-bill approval chain have to match how the firm bills today, or the first billing cycle exposes the gaps. The chart of accounts and bank accounts are built with the finance team. Workflows that open matters, create folders and assign first tasks are written last, once the fields they depend on are settled.
Set-up decisions in Centerbase
- Bill templates and billing arrangements for each client type
- Rate tables, timekeepers and the pre-bill approval chain
- Chart of accounts, bank accounts and cash or accrual basis
- Custom fields, page layouts and automated workflows by practice
- Document storage choice and the standard matter folder structure
- Outlook and Microsoft 365 connection for email and calendar
Questions
esiLaw to Centerbase: 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 Centerbase?
Yes. Centerbase keeps trust ledgers. Multiple trust and retainer accounts per matter or client. 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 Centerbase?
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 Centerbase is kept as a readable archive, and you see which before the move.
What has to be decided before esiLaw data is loaded into Centerbase?
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.
Other routes
Other routes from esiLaw and into Centerbase
Other destinations from esiLaw
Other systems that move into Centerbase
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
esiLaw and Centerbase are the names and marks of their owners, used here only to identify the two systems.
Moving from esiLaw to Centerbase?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.