The fear that keeps Canadian firms on aging software is not the price. It is the fear of losing unbilled time (WIP), breaking the trust balance or freezing the firm for a week. Migrating a firm is not copying a client list. It is moving matters, unbilled time, disbursements, open invoices and, above all, trust balances, without a day on which the firm cannot receive funds. This guide sets out a deterministic migration method: a contradictory inventory, a dry-run simulation, a triple equality at $0.00, and a SHA-256 cryptographic integrity certificate.
Regulatory foundations and reference texts
Quebec — Barreau du Québec
CQLR c. B-1, r. 5, ss. 49–56
Migrated balances stay reconciled to the penny, with vouchers attached.
Ontario — Law Society of Ontario
LSO By-Law 9, ss. 7–18
The By-Law 9 history stays readable after cut-over.
British Columbia — LSBC
LSBC Rules, Part 3, Division 7
Division 7 vouchers follow the matter, not the old software.
Alberta — Law Society of Alberta
LSA Rule 119
The Rule 119 register is exported, not only the balance.
Quebec — Law 25
CQLR c. P-39.1, ss. 3.1–3.8
The Law 25 incident register moves with the matter file.
Federal — PIPEDA
S.C. 2000, c. 5, Schedule 1
The export does not hand information to an ungoverned third party.
Inspection pitfall versus the law society standard
Risky practice at inspection
Moving the clients and leaving the trust balances in the old software.
Regulatory requirement and deterministic control
A triple equality at $0.00 and a certificate, before funds are received in the new system.
Why firms postpone migration — and what that costs
Postponing cut-over looks prudent. In practice each month on an aging local server raises the risk: forgotten manual backups, a partner who leaves with the only admin login, a trust reconciliation done in Excel because the report is unreliable. The cost is not only lost time. It is also the inability to prove, at an inspection, that balances have not drifted. A deterministic migration costs one planned cut-over window; an improvised migration after an incident costs the firm’s continuity. Canadian firms that wait for a “quiet month” often discover that month never arrives, while unbilled WIP and uncleared trust entries keep accumulating outside any controlled export.
The right question is therefore not “can we afford to migrate?” It is “can we afford not to be able to prove our balances next week?” A protocol with a dry-run simulation, a $0.00 equality and a SHA-256 certificate answers that question before the inspector asks it, whether the firm is leaving PCLaw, JurisÉvolution, Clio, CosmoLex, Para-Maître, JurisConcept or a stack of Excel workbooks that never reconciled to the penny in any Canadian province of practice.
Source-system risks and concordance controls
A raw export without a control produces variances discovered too late. The table below summarises what is extracted, what breaks most often, and the automatic control to require before cut-over.
Migration: sources, risks and pre-cut-over controls
↔ Swipe| Source software | Data extracted | Classic risks on a raw export | Concordance control before cut-over |
|---|---|---|---|
| PCLaw | Clients, matters, trust ledger, open invoices | Rounded trust balances; forgotten closed accounts | Sum of client balances = bank statement ($0.00) |
| JurisÉvolution | Matters, time, disbursements, trust | Unbilled time left in the old software | Open hours replayed one by one on a sample |
| JurisConcept | Matters and accounting entries | Chart of accounts and taxes miscalculated | GST/QST recalculated on sample invoices |
| Para-Maître | Matters and documents | Incomplete accounting history | Matter list compared with the imported count |
| Clio | Matters, time, invoices | Custom fields and orphaned files | Counts of clients / matters / open invoices |
| CosmoLex | Coupled practice and accounting | Double entry between trust and operating | Three-way equality bank / ledger / clients |
| Excel | Client and balance spreadsheets | Broken formulas, duplicated rows | SHA-256 digest of the checked file |
Two mistakes keep returning in improvised cut-overs. First: importing clients without WIP, then discovering three weeks later that open hours stayed in the old software. Second: rounding trust balances “so it matches,” which creates exactly the one-cent variance an inspection reads as evidence of neglect. Deterministic migration refuses those shortcuts: nothing is written to production until the dry run shows equality, and the SHA-256 digest freezes the checked file.
Six-step cut-over protocol without business interruption
Audit progress: 0 / 6 control points verified (0%) —
- Contradictory inventory — Count clients, open matters, trust balances, unpaid invoices and unbilled time entries (WIP).
- Freeze the cut-over window — Set a date. After that date the old software receives only emergency entries, noted aside.
- Full dry-run simulation — Import a structured CSV or Excel file, without writing to production and without opening an .mdb file. The firm sees the trust variance before accepting.
- Triple equality at $0.00 — Compare bank balance, sum of clients and the report from the old software. The target variance is $0.00, or a variance already known and written down.
- SHA-256 certificate — Issue the PDF migration audit certificate with the SHA-256 digest of the imported files. The digest proves the checked file is the file that was loaded.
- Operational go-live — Cut over on a weekday morning, train the team within 24 hours, keep the old system read-only for inspection.
What the Bar inspector will ask after cut-over
After a migration the inspector does not want a sales pitch. They want continuity of balances: the reconciliation signed the day before cut-over, proof that the sum of client ledgers still equals the statement, and the certificate showing the imported file was not altered between the check and the load. Keeping the old software read-only during the inspection window is not a luxury: it is the answer to “how do you know nothing was lost?” When those four artefacts sit in one controlled folder, the firm can answer in minutes instead of reconstructing history from memory and email.
A deterministic migration turns fear into an evidence file. The firm no longer hopes that “everything goes fine.” It compares three totals, freezes a cryptographic digest and reopens billing the next morning — with Para-Maître, PCLaw, JurisÉvolution, JurisConcept, Clio, CosmoLex or Excel still available read-only. The method holds for a solo practice and for a thirty-lawyer firm: only the scale of the inventory changes, not the requirement of a $0.00 equality. That is how Canadian firms leave aging servers without a lost billing day and without an unexplained trust variance waiting for the next inspection.
Inspection questions — migration
01
May a firm cut over without a $0.00 equality?
No. An inspector from the Barreau, the LSO, the LSBC or the LSA compares the three totals from the day before. An unexplained variance becomes the first paragraph of the report.
02
Must the old software be kept?
Yes, read-only, until validation. That is the answer to “how do you know nothing was lost?”
03
What does the SHA-256 certificate prove?
That the file which was checked and the file which was loaded are the same. It does not replace reconciliation. It stops a change from slipping in between the two.