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

Data migration route

Unity Accounting to NetDocuments migration

Unity Accounting is a cloud accounting and billing system, and NetDocuments is a cloud document management system. Only files and their details have a place there, so this route carries the documents and archives the rest.

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

What moves

What moves from Unity Accounting to NetDocuments

Each row is a kind of record Unity Accounting holds, whether NetDocuments has a place for it, and what is planned. On this route one kind of record carries across, one kind needs mapping, six kinds have no place in NetDocuments and are archived and six kinds are confirmed in the analysis.

Records in Unity Accounting and their place in NetDocuments
RecordIn Unity AccountingIn NetDocumentsWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClients and matters.Has a place in partAs a client and matter value with its workspace. Other matter details stay in practice management.Carried with mapping
ContactsClients, other parties and referrersHeldClient and contact management.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeld in partDocuments can be managed with clients and matters.Has a placeImported with profile values, folder, dates and access set per document.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeLoaded as email items profiled to the matter.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedNo placeFile notes are loaded as documents in the matter workspace.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldShared calendar with email and SMS reminders.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleTo be confirmedTo be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldNo placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldIncludes flat-fee and contingency billing, card payments and a client payment portal.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldRegular and interest-bearing trust, built to provincial law society rules.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeldFull general accounting; no third-party package required.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeAs custom profile attributes, created in the repository before the load.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeConfirmed in the analysis

What the plans mean

Carried across
NetDocuments has a place for this kind of record. It is loaded there and checked against Unity Accounting.
Carried with mapping
NetDocuments 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
NetDocuments has no place for it. It is exported in a format that opens without Unity Accounting 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

Only the documents have a place here.

NetDocuments is a document management system: it takes files and the details that describe them. Most of what Unity Accounting holds is not files. Entries, balances, settings and lists have no place in a document store, and the table above is short for that reason. What can move is any document Unity Accounting produced or stored: invoices as PDFs, signed agreements, attachments, exported reports. Each is filed under the client or matter it relates to.

The useful version of this job is often an archive. A firm retiring a system wants its records readable later without keeping the subscription or the old PC. The data is exported in open formats, spreadsheets and PDFs, and filed in NetDocuments in a workspace set aside for it, with access limited to the people who need it. That gives the firm one place to look, under the same retention rules as the rest of its documents.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Unity Accounting depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to Unity Accounting is kept running until the checks on NetDocuments are finished.

Where the data is now

A firm on Unity Accounting has its trust ledgers and its own books in the same program. Leaving means moving both, or moving one and re-homing the other. Canadian trust rules are set province by province, so the destination has to satisfy the same law society. It also matters whether the firm is on the hosted version, the desktop version or an older esiLaw installation.

  1. Trust and general in one

    Unity Accounting does full legal accounting, trust and general, with no outside package. Many practice management systems expect the general ledger to live in QuickBooks or similar. A firm moving to one of those is splitting its books in two: client ledgers and billing go one way, the firm’s ledger another, and both opening positions are agreed together.

  2. Provincial law society rules

    The software is built to provincial law society requirements, and the firm’s trust reports follow its own province’s format. Before a destination is chosen, we confirm that it produces the trust records that province’s law society asks for. The closing trust reconciliation from Unity Accounting is kept as the audit record of the old system.

  3. Interest-bearing trust accounts

    As well as regular trust, the software handles interest-bearing trust. Money held that way for a client is tracked apart from the pooled account. Each such holding is listed at cutover with its balance, since a system that expects only one pooled trust account needs them set up separately before the figures are loaded.

  4. esiLaw, desktop or hosted

    The product was esiLaw until late 2023, and the vendor offers a cloud version in Canadian data centres as well as a desktop one. Dye & Durham treats a move from esiLaw to the current product as a migration in its own right. We confirm which one the firm runs, because that decides where its database is.

  5. Cheques not yet cleared

    Cheque writing and electronic transactions run from the accounting program. Outstanding cheques at cutover are the usual trap. They are listed with the final bank reconciliation, so each one clears against the right ledger in whichever system is then holding the trust account.

More about moving off Unity Accounting

Where it is going

Loading into NetDocuments means every document arrives with a profile. The cabinet, its profile attributes and the client and matter lookup tables are built first. Documents are then imported with an instruction file that says, line by line, which file gets which client, matter, author, document type, folder and access. Preparing that file from the old system’s data is most of the work.

  1. Lookup tables before documents

    Client and matter are validated attributes, with matter the child of client. A value missing from the lookup table cannot be used to profile a document. The tables are loaded from the practice management system first, closed matters included, and each matter is flagged open or closed so old ones stay out of pick lists.

  2. Workspaces come from the profile

    A workspace shows whatever is profiled to its matter. So the question is not where to put a folder tree but how to profile each file. Old folder names are often turned into a document type attribute, or kept as a workspace folder, and the mapping decides which for each one.

  3. Import files are unforgiving

    The import file is comma-separated text, and NetDocuments itself warns that opening one in Excel can strip leading zeros from numbers and alter dates. A matter number of 00123 that becomes 123 will not match its lookup value. The files are kept as plain text from start to finish and are not opened in a spreadsheet.

  4. Folder limits and depth

    A folder can hold any number of documents but no more than 500 subfolders. Deep trees copied from a file server also work against the way the system is searched. Where a matter arrives with hundreds of nested folders, the plan flattens them and keeps the lost path in the document name or an attribute.

  5. Security at the right level

    Access can be set on the cabinet, by profile value, on a workspace or on a single document. Restricted matters are best carried as workspace or profile-based security, so that new documents pick it up. Document-by-document access lists copied from an old system are loaded only where the restriction was real.

More about moving into NetDocuments

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

    We read what Unity Accounting holds and how it is organised, then agree with you where each kind of record will sit in NetDocuments. 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 NetDocuments and checked against Unity Accounting: 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 Unity Accounting, a final pass over a weekend picks up what changed since the trial. Unity Accounting 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 Unity Accounting 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 fromUnity Accounting
Moving toNetDocuments

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 Unity Accounting holds

    What is in it, how its records link, and where each piece would sit in NetDocuments. 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

Setting up NetDocuments

Loaded data is not yet a working system. This is what NewLaw sets up in NetDocuments, beyond the migration, so that people can work in it from the first day.

Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.

Set-up decisions in NetDocuments

  • Cabinet design: one for the firm, or several by purpose
  • Profile attributes, lookup tables and the client and matter hierarchy
  • Workspace layout with default folders, filters and saved searches
  • User groups, cabinet membership and security for restricted matters
  • A feed of new clients and matters from practice management
  • ndOffice, ndMail and Outlook filing on every desk, with training

Questions

Unity Accounting to NetDocuments: what firms ask

We only want to replace practice management. Can the accounting stay?

It can. Some firms keep Unity Accounting for trust and general ledgers and put a practice management system beside it. Then little data moves out of it, and the question becomes how time and billing reach the accounts. Dye & Durham lists an integration with its own Unity Practice Management; other pairings are checked in the analysis.

Is esiLaw the same as Unity Accounting for a migration?

They are one product line under two names, and both hold the same kinds of record. The version still matters. An older esiLaw installation and the current hosted product may keep their data in different places, so we confirm the version and where the database sits before estimating the work.

When is the best time to cut over the trust accounts?

At a month end, after the trust reconciliation is finished and reviewed. The balances loaded are the reconciled client ledger balances, and the comparison of bank, book and client listing is repeated in the new system on day one. Law society reporting periods are checked so a filing does not straddle two systems.

Do trust balances in Unity Accounting have a place in NetDocuments?

No. NetDocuments does not keep trust ledgers. Trust records from Unity Accounting 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 NetDocuments has no place for?

On this route that is contacts, calendar entries, time entries, billing records, trust ledgers and the firm’s accounts. They are exported from Unity Accounting 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 Unity Accounting data is loaded into NetDocuments?

Matters are carried with mapping, so each mapping is agreed with you first. 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

Unity Accounting and NetDocuments are the names and marks of their owners, used here only to identify the two systems.

Moving from Unity Accounting to NetDocuments?

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

We reply within one business day.