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

Data migration route

Unity Accounting to SharePoint migration

Unity Accounting is a cloud accounting and billing system, and SharePoint is cloud file storage. What moves is the files, plus a readable export of everything else the old system holds.

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

What moves

What moves from Unity Accounting to SharePoint

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

Records in Unity Accounting and their place in SharePoint
RecordIn Unity AccountingIn SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClients and matters.Has a place in partAs a site, library, folder or list row the firm designs; no built-in matter record.Carried with mapping
ContactsClients, other parties and referrersHeldClient and contact management.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeld in partDocuments can be managed with clients and matters.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs .msg or .eml files, with columns for sender and date if set up.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a place in partAs documents, or as rows in a notes list if one is built.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldShared calendar with email and SMS reminders.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a place in partPossible as a list; no legal workflow built in.Confirmed 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 placeColumns and content types on libraries and lists.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partPrecedents as files; templates can be offered from a library.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeConfirmed in the analysis

What the plans mean

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

An export the firm can open without the system.

SharePoint holds files, and most of what Unity Accounting 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 Unity Accounting, 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 SharePoint is limited before the export is copied in.

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

SharePoint will take a firm’s documents in almost any arrangement, which is the difficulty. The structure has to be chosen before the load: what a client is, what a matter is, and where security is applied. Changing it afterwards means moving every file again. Most of the effort goes into that design and into the columns that describe each document.

  1. Site, library or folder per matter

    A matter can be a site, a library within a client site, or a folder in one large library. Each choice has consequences for permissions, for search and for how a new matter is opened. The firm makes that decision, and the people who open matters every day should be part of it.

  2. Columns are built before content

    If documents are to carry matter number, client, document type or author as columns, those columns and any content types exist before loading, so each file can be tagged as it arrives. Tagging hundreds of thousands of documents afterwards is a second project that seldom gets finished.

  3. The 400 character path

    SharePoint limits the full decoded path, site and library and folders and file name, to 400 characters. A deep tree copied from a server drive under a long site name can cross it. Path lengths are calculated against the planned structure, not the old one, before any file moves.

  4. Large libraries and the view threshold

    A library can hold millions of files, but a view that tries to show more than 5,000 items at once runs into the list view threshold. One flat library with a folder per matter needs indexed columns and filtered views from the start, or views begin to fail as the library fills.

  5. Security by library, not by file

    Microsoft supports up to 50,000 unique permissions in a library and recommends staying under 5,000. Restricting matters one folder at a time reaches that sooner than firms expect. Restricted work is better grouped into its own site or library, so the permission is set once.

More about moving into SharePoint

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in SharePoint 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 SharePoint. 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 SharePoint 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 toSharePoint

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

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

Making SharePoint work as a firm’s document store is a design and build job in its own right. The sites, libraries, columns and permission groups are created, a way of opening a new matter is put in place so the structure repeats itself, and the Outlook and Teams habits around it are agreed. Search is tested with real questions from fee earners.

What is agreed and set up

  • Site and library structure for clients and matters
  • Columns and content types for matter number and document type
  • Permission groups, with restricted matters in their own libraries
  • A repeatable way to create each new matter’s workspace
  • Version history limits and retention labels for closed matters
  • Views, indexed columns and search tested on loaded data

Questions

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

No. SharePoint 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 SharePoint has no place for?

On this route that is 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 SharePoint?

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

Moving from Unity Accounting to SharePoint?

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

We reply within one business day.