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

Data migration route

esiLaw to Google Drive migration

esiLaw is a desktop accounting and billing system, and Google Drive is cloud file storage. What moves is the files, plus a readable export of everything else the old system holds.

FromesiLawDesktop
  1. Documents: Carried across
  2. Emails: Confirmed in the analysis
  3. Notes: Confirmed in the analysis
  4. Tasks: Confirmed in the analysis
  5. Custom fields: Confirmed in the analysis
  6. Templates: Confirmed in the analysis
  7. Intake: Confirmed in the analysis
ToGoogle DriveCloud
  1. Matters: Kept as a readable archive
  2. Contacts: Kept as a readable archive
  3. Calendar: Kept as a readable archive
  4. Time and expenses: Kept as a readable archive
  5. Billing: Kept as a readable archive
  6. Trust money: Kept as a readable archive
  7. Firm accounts: Kept as a readable archive
Readable archiveNo place in Google Drive
  • 1 carried
  • 6 to confirm
  • 7 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from esiLaw to Google Drive

Each row is a kind of record esiLaw holds, whether Google Drive has a place for it, and what is planned. On this route one kind of record carries across, seven kinds have no place in Google Drive and are archived and six kinds are confirmed in the analysis.

Records in esiLaw and their place in Google Drive
RecordIn esiLawIn Google DriveWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClient numbers with optional three-character matter numbers.No placeA matter is a folder inside a shared drive.Kept as a readable archive
ContactsClients, other parties and referrersHeldNo placeContacts belong in Google Contacts, not Drive.Kept as a readable archive
DocumentsFiles stored in or linked from the systemHeld in partThe help centre has a section on documents and document management.Has a placeAny file type, stored as uploaded or converted to Google formats.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs .eml or .msg files in the matter folder; not as Gmail messages.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a place in partAs a Doc or Word file in the matter’s folder.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partShared calendaring is listed for the product under its Unity name.No placeCalendar entries belong in Google Calendar.Kept as a readable archive
TasksTo-dos and workflow steps assigned to peopleTo be confirmedNo placeConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTime and fees.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldBilling, payments, receipts and deposits.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldTrust ledgers by client, including term trust, built to law society rules.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger, payables, bank reconciliation and payroll cheques.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedNo placeConfirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partPrecedents load as files; the load does not rebuild Word automation in Docs.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeConfirmed in the analysis

What the plans mean

Carried across
Google Drive 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
Google Drive 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.

Google Drive 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 Google Drive 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. Google Drive 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

Putting a firm’s matter files into Google Drive means choosing shared drives over personal ones and then deciding how many shared drives there should be. That second decision is driven by Google’s limits and by who is allowed to see what, since access is granted mainly at the level of the whole shared drive.

  1. Shared drives, not My Drive

    Files loaded into a shared drive belong to the firm and remain when the person who loaded them leaves. Anything loaded into someone’s My Drive belongs to that person. Matter files therefore go to shared drives, and My Drive is left for personal working papers.

  2. One drive cannot hold everything

    Google caps a shared drive at 500,000 items, counting folders, shortcuts and anything in the trash, and at 100 levels of nested folders. A firm with twenty years of matters can pass the item cap in a single drive. The split is planned up front, commonly by practice group, or by open and closed matters.

  3. Membership is the main control

    Every member of a shared drive can see all of it unless a Manager restricts a particular folder. Matters that only certain people may open are simpler to protect in a shared drive of their own. The firm supplies the list of restricted matters and partners’ private folders before the drives are created.

  4. The daily upload limit

    Each user can upload 750 GB to Drive in 24 hours, and then has to wait. For a large document set that limit sets the shortest time the load can take. The total size is measured in the analysis, so the firm knows before the freeze whether its documents fit inside a weekend.

  5. Keep Office files as Office files

    Word and Excel files can be stored in Drive as they are or converted to Google formats. Unless the firm asks otherwise they are loaded unconverted, so court documents and automated precedents arrive as they left. The firm decides afterwards which templates are worth rebuilding as Google Docs.

More about moving into Google Drive

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Google Drive on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what esiLaw holds and how it is organised, then agree with you where each kind of record will sit in Google Drive. Anything with no place there stays behind or is archived, and you see which before the move.

  2. 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.

  3. Trial load

    A trial is loaded into Google Drive 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.

  4. 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

Step 1 of 5: Start with the route

Moving fromesiLaw
Moving toGoogle Drive

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 Google Drive. 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

Structure, permissions and handover

Google Drive 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.

A Drive set-up for a law firm is a small number of deliberate choices made in the Workspace Admin console and then left alone. Which shared drives exist, who manages each, whether staff may share outside the firm, and whether people work from the browser or from Drive for desktop. Staff also need to be shown where a new matter folder goes.

What is agreed and set up

  • Shared drives by practice group, with a naming pattern
  • Managers and member access levels for each shared drive
  • External sharing rules set in the Admin console
  • Drive for desktop on PCs that need Explorer access
  • A standard subfolder set copied into every new matter
  • Transfer of leavers’ My Drive files as a standing procedure

Questions

esiLaw to Google Drive: 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 Google Drive?

No. Google Drive 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 Google Drive 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 Google Drive?

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.

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 Google Drive are the names and marks of their owners, used here only to identify the two systems.

Moving from esiLaw to Google Drive?

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

We reply within one business day.