Data migration route
esiLaw to Gladiate migration
esiLaw is a desktop accounting and billing system, and Gladiate is a cloud case management system for personal injury work. Only part of what esiLaw holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.
- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Calendar: Carried across
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Time and expenses: Confirmed in the analysis
- Billing: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
- Intake: Confirmed in the analysis
GladiateCloud- 4 carried
- 10 to confirm
What moves
What moves from esiLaw to Gladiate
Each row is a kind of record esiLaw holds, whether Gladiate has a place for it, and what is planned. On this route four kinds of record carry across and ten 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 placePersonal injury cases. | Carried across |
| ContactsClients, other parties and referrers | Held | Has a placeClients, leads and referral sources. | 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 placeFiled to the firm’s folder structure. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partShared calendaring is listed for the product under its Unity name. | Has a placeEvents sync with Outlook and Google Calendar. | Carried across |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a placeTasks and task plans. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime and fees. | To be confirmed | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | HeldBilling, payments, receipts and deposits. | To be confirmed | Confirmed in the analysis |
| Trust moneyTrust or client account ledgers and balances | HeldTrust ledgers by client, including term trust, built to law society rules. | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral ledger, payables, bank reconciliation and payroll cheques. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | To be confirmed | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partFirm templates are set up again in Gladiate. Old templates are not converted. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a placeLeads and client sign-up. | Confirmed in the analysis |
What the plans mean
- Carried across
- Gladiate 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
Clients and jobs move. The books stay books.
An accounting or billing system and a case management system overlap less than firms expect. esiLaw knows clients, jobs, time and invoices. Gladiate knows cases, parties, documents and deadlines. The client list moves well, and jobs can seed the case list. Time and invoice history has a place only where the case system has a billing side, and the table above shows whether this one does. A general ledger does not belong in a case system.
So the plan has two halves. Records with a place in Gladiate are loaded and checked there. The rest is exported from esiLaw as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If esiLaw is staying as the accounting system, nothing financial needs to move at all, and the job is to line up client and case numbers so the two can be reconciled.
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. Gladiate 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 Gladiate
Gladiate is a destination for personal injury firms, and what it expects is injury data: a client, an incident, coverage, providers and a case status. Loading a firm into it means shaping the old system’s records into that pattern and preparing the templates, task plans and folder structure that the vendor’s onboarding asks each firm to supply.
Injury fields come first
Coverage, liability and medical details are what the product is designed to put in front of staff. In the old system they may be in custom fields, notes or a spreadsheet. They are pulled into columns during the analysis, so a loaded case shows its insurer and policy details and not an empty panel.
Templates and task plans
The vendor’s onboarding has each firm set up its own document templates, task plans, litigation deadlines and questionnaires. These are prepared from what the firm uses now. Merge fields in old templates are replaced with Gladiate’s, and task plans are written down stage by stage before anyone builds them.
A folder structure per case
Documents are filed in a folder structure the firm defines. The old system’s folders or categories are mapped to it once, and every case is loaded to the same pattern. Files with no clear category go to a holding folder on the case and are listed, not scattered.
What it may not hold
Time records, invoices and trust ledgers are not described on the vendor’s public pages. A firm that needs those carried over has it confirmed in the analysis. If there is no place for them, balances stay in the accounting package and the detailed history is kept in the old system, read only.
How NewLaw runs it
Four steps, in this order.
No financial cutover is planned on this route, so a load can be run again until it is right. If the analysis finds financial records with a place in Gladiate, they get a rehearsed cutover of their own.
Analysis
We read what esiLaw holds and how it is organised, then agree with you where each kind of record will sit in Gladiate. Anything with no place there stays behind or is archived, and you see which before the move.
Clean-up
Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.
Trial load
A trial is loaded into Gladiate and checked against esiLaw: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.
Cutover
After a short freeze on changes in esiLaw, a final pass over a weekend picks up what changed since the trial. If the analysis found financial records to move, their cutover is rehearsed on a full trial load first. 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 Gladiate. 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 Gladiate
Loaded data is not yet a working system. This is what NewLaw sets up in Gladiate, beyond the migration, so that people can work in it from the first day.
Gladiate is delivered ready for injury work, so set-up is about making it the firm’s own. The vendor’s onboarding covers templates, task plans, folder structure, litigation deadlines and client questionnaires. Each of those is a decision the firm has to make, and it goes faster when current practice has been written down beforehand.
Set-up decisions in Gladiate
- Set up and test the firm’s document templates
- Write task plans for each stage of a case
- Agree one folder structure for case documents
- Enter litigation deadlines for the firm’s jurisdictions
- Prepare client questionnaires, surveys and scheduled case updates
- Connect Outlook or Google calendars for two-way sync
Questions
esiLaw to Gladiate: 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 Gladiate?
That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in esiLaw before the plan is fixed. If Gladiate turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
Does everything in esiLaw have a place in Gladiate?
Most of it does on paper. Emails, notes, tasks, time entries, billing records, trust ledgers, the firm’s accounts, 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 Gladiate is kept as a readable archive, and you see which before the move.
What has to be decided before esiLaw data is loaded into Gladiate?
Emails, notes, tasks, time entries, billing records, trust ledgers, the firm’s accounts, custom fields, templates and intake records are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from esiLaw and into Gladiate
Other destinations from esiLaw
Other systems that move into Gladiate
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 Gladiate are the names and marks of their owners, used here only to identify the two systems.
Moving from esiLaw to Gladiate?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.