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

Data migration route

Unity Accounting to Neos migration

Unity Accounting is a cloud accounting and billing system, and Neos is a cloud case management system for personal injury work. Only part of what Unity Accounting holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.

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

What moves

What moves from Unity Accounting to Neos

Each row is a kind of record Unity Accounting 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.

Records in Unity Accounting and their place in Neos
RecordIn Unity AccountingIn NeosWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClients and matters.Has a placeCases by case type.Carried across
ContactsClients, other parties and referrersHeldClient and contact management.Has a placeParties, providers and case contacts. Contacts can be imported from CSV.Carried across
DocumentsFiles stored in or linked from the systemHeld in partDocuments can be managed with clients and matters.Has a placeCase Docs tab, organised in sub-tabs.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas 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 notesTo be confirmedHas a placeConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldShared calendar with email and SMS reminders.Has a placeCase calendar entries.Carried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeLoaded as checklist items.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldHas 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 balancesHeldIncludes flat-fee and contingency billing, card payments and a client payment portal.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 balancesHeldRegular and interest-bearing trust, built to provincial law society rules.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldFull general accounting; no third-party package required.No placeThe general ledger stays in QuickBooks.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeUser-defined fields are created on the relevant tab first.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt for Neos document generation.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas 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 Unity Accounting.
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 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

Clients and jobs move. The books stay books.

An accounting or billing system and a case management system overlap less than firms expect. Unity Accounting 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 Unity Accounting as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If Unity Accounting 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.

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 Neos 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

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.

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

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

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

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

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

More about moving into Neos

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 Unity Accounting and checking each trial against Unity Accounting.

  1. Analysis

    We read what Unity Accounting 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.

  2. Clean-up

    Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Unity Accounting, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Neos as a trial and checked against Unity Accounting: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Unity Accounting 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 Unity Accounting as at the cutover date. 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 toNeos

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

Unity Accounting to Neos: 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 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 Unity Accounting 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 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 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.

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

Moving from Unity Accounting 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.