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

Data migration route

Unity Accounting to Litify migration

Unity Accounting is a cloud accounting and billing system, and Litify is a cloud case management system. 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 across
  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. Firm accounts: Confirmed in the analysis
  12. Custom fields: Confirmed in the analysis
  13. Templates: Confirmed in the analysis
  14. Intake: Confirmed in the analysis
ToLitifyCloud
  • 5 carried
  • 1 mapped
  • 8 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Unity Accounting to Litify

Each row is a kind of record Unity Accounting holds, whether Litify has a place for it, and what is planned. On this route five kinds of record carry across, one kind needs mapping and eight kinds are confirmed in the analysis.

Records in Unity Accounting and their place in Litify
RecordIn Unity AccountingIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClients and matters.Has a placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeldClient and contact management.Has a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemHeld in partDocuments can be managed with clients and matters.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedTo be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldShared calendar with email and SMS reminders.Has a placeCalendar events on the matter.Carried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldHas a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeldIncludes flat-fee and contingency billing, card payments and a client payment portal.Has a place in partBilling is part of the product. Loading past invoices is scoped 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.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCustom fields are created before loading.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt in Litify’s document generation.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeLoaded as intakes.Confirmed in the analysis

What the plans mean

Carried across
Litify has a place for this kind of record. It is loaded there and checked against Unity Accounting.
Carried with mapping
Litify 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.

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. Litify 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 Litify 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 Litify 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 a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.

  1. The design comes first

    Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.

  2. One party, many roles

    Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.

  3. Open enquiries load as intakes

    Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.

  4. Documents load after records

    Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.

  5. Validation rules reject bad rows

    A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.

More about moving into Litify

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 Litify 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 Litify. 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 Litify 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 Litify 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 toLitify

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

Loaded data is not yet a working system. The maker of Litify runs or arranges the set-up of its product, so this is what has to be decided and put in place in Litify, whoever does the work, before people rely on it from the first day.

A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.

Set-up decisions in Litify

  • Define intake questionnaires and the rules for conversion
  • Set case types, matter stages and page layouts
  • Build matter plans that create tasks at each stage
  • Design document folders and generation templates per case type
  • Configure user roles and sharing for restricted matters
  • Decide on timekeeping, billing and accounting integrations

Questions

Unity Accounting to Litify: 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 Litify?

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 Litify turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

Does everything in Unity Accounting have a place in Litify?

Most of it does on paper. Emails, notes, tasks, trust ledgers, the firm’s accounts, custom fields, templates and intake records could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Litify is kept as a readable archive, and you see which before the move.

What has to be decided before Unity Accounting data is loaded into Litify?

Billing records are carried with mapping, so each mapping is agreed with you first. Emails, notes, tasks, trust ledgers, the firm’s accounts, 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 Litify are the names and marks of their owners, used here only to identify the two systems.

Moving from Unity Accounting to Litify?

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

We reply within one business day.