Data migration route
esiLaw to Dropbox migration
esiLaw is a desktop accounting and billing system, and Dropbox is cloud file storage. What moves is the files, plus a readable export of everything else the old system holds.
- Documents: 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
DropboxCloud- Matters: Kept as a readable archive
- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Trust money: Kept as a readable archive
- Firm accounts: Kept as a readable archive
- 1 carried
- 6 to confirm
- 7 archived
What moves
What moves from esiLaw to Dropbox
Each row is a kind of record esiLaw holds, whether Dropbox has a place for it, and what is planned. On this route one kind of record carries across, seven kinds have no place in Dropbox and are archived 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. | No placeA matter is a folder named by the firm’s convention. | Kept as a readable archive |
| ContactsClients, other parties and referrers | Held | No place | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | Held in partThe help centre has a section on documents and document management. | Has a placeFiles in folders; the folder path is the only index. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partAs .msg or .eml files filed in the matter folder. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place in partAs documents saved to the matter folder. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partShared calendaring is listed for the product under its Unity name. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | No place | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime and fees. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | HeldBilling, payments, receipts and deposits. | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | HeldTrust ledgers by client, including term trust, built to law society rules. | No place | Kept as a readable archive |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral ledger, payables, bank reconciliation and payroll cheques. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | To be confirmed | No place | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partPrecedents load as ordinary files in a precedents folder. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | No place | Confirmed in the analysis |
What the plans mean
- Carried across
- Dropbox 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.
- Kept as a readable archive
- Dropbox 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
An export the firm can open without the system.
Dropbox holds files, and most of what esiLaw holds is records. This route is therefore an export job. Each kind of record is written out in a format that opens without the system it came from: lists as spreadsheets, statements and invoices as PDFs, attachments as the files they were. The export is laid out in folders that make sense to someone who never used esiLaw, by client or by year, with a short index file saying what is where.
Firms do this when a subscription is ending, when a system is being retired, or to meet a retention rule. The test of the result is whether a question can still be answered from it years later: what was this client invoiced, who signed this agreement and when. So the trial export is checked by asking those questions of it. Totals are agreed to the system’s own reports, and access to the folder in Dropbox is limited before the export is copied in.
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. Dropbox 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 Dropbox
Loading matter files into Dropbox is a matter of getting the tree right, since the tree is all there is. No field holds a matter number or a client name. The folder names carry that, so the naming rule is agreed first: what a client folder is called, what a matter folder is called, and which subfolders every matter gets.
Team folders before files
Team folders are shared with groups, and each group is given an editor or view-only role. The groups and the top-level folders are created before the load so that files arrive already restricted. Loading first and sharing afterwards leaves a period in which the wrong people can see everything.
Keep paths under 260 characters
Dropbox’s naming guidance asks for full paths shorter than 260 characters. Matter trees from document systems often exceed that once the client name, matter description and subfolders are joined. Long paths are measured early and cut back by rule, usually by trimming the matter description and keeping the number.
Characters that get swapped
On Windows, the desktop app replaces restricted characters in names with an underscore. A file called Smith v Jones: Affidavit becomes something slightly different on some machines. Names are cleaned before loading so that the file has one name everywhere and matches the index kept from the old system.
Matter data has nowhere to go
Parties, matter type, responsible lawyer, open and closed dates: none of it has a field here. If the firm is leaving a practice management system and keeping only documents, that data can be kept as an exported spreadsheet beside the folders, so they can still be read against it. Whether one is produced is decided in the analysis.
History starts on loading day
Version history in Dropbox begins when a file arrives. Earlier versions from the old system come across as separately named files in the matter folder, or stay behind. The firm sees a sample matter loaded with its earlier versions as named copies before choosing.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Dropbox on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what esiLaw holds and how it is organised, then agree with you where each kind of record will sit in Dropbox. 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 Dropbox 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
There is no financial cutover on this route. After a short freeze on changes in esiLaw, a final pass over a weekend picks up what changed since the trial. 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 Dropbox. 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
Structure, permissions and handover
Dropbox is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.
Beyond the load, a firm on Dropbox needs the account arranged so the files belong to the firm and not to individuals. That means a team plan with an administrator, groups that match how the firm works, and a decision about which folders sync to every computer. A written filing rule tells staff where each new matter folder goes.
What is agreed and set up
- Team folders for clients, precedents and administration
- Groups by team, each with an editor or viewer role
- Which folders sync to PCs and which stay online-only
- Rules for sharing links and folders with clients
- A written naming rule for client and matter folders
- Steps for removing a leaver without losing their folders
Questions
esiLaw to Dropbox: 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 Dropbox?
No. Dropbox does not keep trust ledgers. Trust records from esiLaw are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.
What happens to records Dropbox has no place for?
On this route that is matters, contacts, calendar entries, time entries, billing records, trust ledgers and 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 Dropbox?
Emails, notes, tasks, 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 Dropbox
Other destinations from esiLaw
Other systems that move into Dropbox
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 Dropbox are the names and marks of their owners, used here only to identify the two systems.
Moving from esiLaw to Dropbox?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.