Data migration route
esiLaw to Neos migration
esiLaw is a desktop accounting and billing system, and Neos 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
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
- Intake: Confirmed in the analysis
NeosCloud- Firm accounts: Kept as a readable archive
- 4 carried
- 2 mapped
- 7 to confirm
- 1 archived
What moves
What moves from esiLaw to Neos
Each row is a kind of record esiLaw holds, whether Neos has a place for it, and what is planned. On this route four kinds of record carry across, two kinds need mapping, one kind has no place in Neos and is archived and seven 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 placeCases by case type. | Carried across |
| ContactsClients, other parties and referrers | Held | Has a placeParties, providers and case contacts. Contacts can be imported from CSV. | 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 placeCase Docs tab, organised in sub-tabs. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partEmails tagged to a case are held. Loading old mail is scoped in the analysis. | 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 placeCase calendar entries. | Carried across |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a placeLoaded as checklist items. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime and fees. | Has a place in partTime can be held as value items. The treatment of old entries is confirmed in the analysis. | Carried with mapping |
| BillingInvoices, payments and debtor balances | HeldBilling, payments, receipts and deposits. | Has a place in partInvoices exist in Neos. Loading past invoices is confirmed in the analysis. | Carried with mapping |
| 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. | No placeThe general ledger stays in QuickBooks. | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeUser-defined fields are created on the relevant tab first. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partTemplates are rebuilt for Neos document generation. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a placeIntakes tab. Simple intake imports from CSV are supported. | Confirmed in the analysis |
What the plans mean
- Carried across
- Neos has a place for this kind of record. It is loaded there and checked against esiLaw.
- Carried with mapping
- Neos 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
- Neos 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
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. Neos 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 Neos 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. Neos 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 Neos
Neos expects personal injury data in its own tab structure, so loading a firm means deciding which tab each old record belongs on. Parties, insurance and counsel map directly from most injury systems. Money maps to value items. Anything the standard tabs lack becomes a user-defined field, which has to be created before the load.
Every figure needs a value code
Costs, medical bills, fees and settlement amounts are loaded as value items, and each carries a value code. The code list is agreed with the firm’s accounts staff first. A figure loaded under the wrong code is reported in the wrong place, so the list is tested on real cases before the bulk load.
Lists are set up first
Cases are loaded against case types, statuses and staff assignments that already exist in Neos. Those lists are set up, and the old system’s values tidied to match, before the trial load. Misspelt attorney names and unused case types in the source are cleaned out at the same stage.
Documents go to sub-tabs
Files land on the Case Docs tab under sub-tabs, which staff can view as a list or as folders. The old system’s folders or categories are mapped to a fixed set of sub-tabs. Without that, every personal habit of naming folders is reproduced and the folder view becomes hard to read.
Reminders split two ways
Neos fills its dashboards from checklists and case calendars. Old diary entries and tasks are sorted between them: dated appointments and court events to the calendar, and to-dos to the checklist. An item assigned to several people in the old system may need one named owner, and the firm chooses who.
Assembly runs its own conversions
Assembly migrates firms into Neos with its own team and tooling, and offers routes from self-service templates to a full conversion. Where the firm uses that service, outside help goes on the work around it: cleaning the source, checking the converted cases against the old system, and listing exceptions.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of Neos says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in esiLaw and checking each trial against esiLaw.
Analysis
We read what esiLaw holds and how its records link, then agree with you, field by field, where each piece will sit in Neos. 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 Neos as a trial and checked against esiLaw: record counts, financial 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 Neos goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in esiLaw as at the cutover date. 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 Neos. 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 Neos
Loaded data is not yet a working system. The maker of Neos runs or arranges the set-up of its product, so this is what has to be decided and put in place in Neos, whoever does the work, before people rely on it from the first day.
Neos comes set up for injury work, so implementation is mostly choosing among its options and connecting the firm’s other tools. The lists that drive reporting are decided first, then checklists, then documents. Assembly provides its own implementation team, and the firm’s internal lead still has to make the decisions listed below.
Set-up decisions in Neos
- Set case types, statuses and staff roles
- Agree the value code list with accounts staff
- Build checklists for each case type and stage
- Create user-defined fields for data the tabs lack
- Prepare document templates for the generation wizard
- Connect Microsoft 365, QuickBooks and the phone system
Questions
esiLaw to Neos: 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 Neos?
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 Neos turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
What happens to records Neos 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 Neos?
Time entries and billing records are carried with mapping, so each mapping is agreed with you first. Emails, notes, tasks, trust ledgers, 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 Neos
Other destinations from esiLaw
Other systems that move into Neos
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 Neos are the names and marks of their owners, used here only to identify the two systems.
Moving from esiLaw to Neos?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.