Set the Cutover Date Around Your Month-End Close
When a legal billing software migration goes wrong, the cause is usually timing, not technology. The firm accepts a go-live date that suits the vendor's implementation calendar. Then it has to close the month across two systems, with half the pre-bills in each. That's how a billing cycle gets lost: invoices go out two or three weeks late and collections slip with them.
Fix the date first and plan everything else back from it. The safest cutover is the first business day after a completed month-end close. By that point the last invoice run in the old system has gone out, the month's trust or client account reconciliation is signed and the general ledger is closed. Every opening balance in the new system then shares one clean "as at" date that matches a bank statement.
Avoid these dates where you can:
- Your financial year-end, or the month before an external audit or a regulator's accountant's report.
- The last month of a VAT, GST or sales-tax return period. Each tax period's filings should come from a single system.
- Your heaviest billing month. For many firms that's quarter-end, when institutional clients want invoices before their own budget cut-offs.
Write the date into the vendor contract as a milestone. Then count back eight to twelve weeks for the planning, mapping and testing below. A small firm on a standard cloud platform can often work to the short end of that range.
Looking to streamline vendor RFP selection?
Access pre-negotiated tier discounts through our independent institutional network.
Separate Live Balances From History Before Anyone Exports a File
Vendors will offer to "migrate everything." Say no until you've decided, one category at a time, what needs to be working data in the new system and what can go into a read-only archive. Live data has to reconcile to the cent. Archived data only has to be findable.
| Data | Recommended treatment | Why |
|---|---|---|
| Unbilled time and disbursements (WIP) | Migrate as individual entries | Must stay billable, editable and reportable by timekeeper |
| Open accounts receivable | Migrate invoice by invoice, at outstanding balance | Receipts must allocate to the right invoice and ageing must stay accurate |
| Trust / client account balances | Migrate as opening balance per client-matter ledger | Regulatory reconciliation has to tie out from day one |
| Rate tables, fee arrangements, tax codes | Rebuild and test; don't bulk-import blindly | Mapping errors produce wrong invoices without any warning |
| Paid invoices and closed matters | Summary totals plus PDF/CSV archive | Needed for reference and retention, not daily work |
| Historic trust transactions | Archive with read-only access | Regulators may ask for them; they don't need to be live |
For a firm of 10 to 100 lawyers, migrating full transaction history can add a lot of mapping effort and vendor fees, and what you get back is mostly reports you'll seldom run. Our recommendation: bring across two to three years of summary data and keep the full history in an export you can query.
Clear and Carry Over Unbilled Time and WIP
The easiest WIP to migrate is WIP you've already billed. In the last cycle on the old system, bill everything you can, and write off or put on hold whatever you were never going to collect. What's left comes across as individual entries.
- Announce a time-entry cutoff. Timekeepers must finalize every entry dated on or before cutover by a fixed deadline, usually two business days before.
- Run final pre-bills early. Start the last cycle three to five days ahead of your normal timetable so partner review is done before cutover.
- Export remaining WIP with full attributes: original work date, timekeeper, matter, hours, rate applied, task or activity code, narrative and billing status (hold, draft, approved).
- Reconcile totals three ways: by timekeeper, by matter and firm-wide. Check the old system's WIP report against the import file, then the import file against the new system's WIP report.
- Switch the timers. If timekeepers use a separate time-tracking app or a mobile timer, point it at the new system on cutover day and turn off the old sync. If you don't, entries will land in a system nobody bills from.
Migrate each WIP entry at its original rate and date. Some systems re-rate entries on import. When that happens, time recorded at last year's rate shows up on the next invoice at this year's rate, and the client queries it.
Bring Trust and Client Account Balances Across to the Penny
This is the step regulators care about, so control it more tightly than anything else. Requirements vary by jurisdiction. Many US state bars require regular three-way reconciliations of bank statement, trust journal and client ledgers, often monthly. In England and Wales, the SRA Accounts Rules require client account reconciliations at least every five weeks. Canadian law societies and Australian state regulators generally expect reconciliations at least monthly. In parts of the Middle East, Asia and Africa the formal rules can be lighter, but auditors and clients will still want ledgers you can prove. Check the obligations that apply to you with your regulator or a licensed accountant before you design the cutover.
Whichever trust accounting software you're moving to, the mechanics are the same:
- Migrate an opening balance for each client-matter ledger as at the cutover date. One pooled trust balance won't do.
- Bring uncleared items across as reconciling items: outstanding cheques, deposits in transit and pending electronic transfers. Without them, the first reconciliation in the new system won't balance.
- Before go-live, confirm that the client ledgers add up to the adjusted bank balance. Resolve any variance in the old system. Never carry it forward.
- Freeze trust disbursements for the 24 to 48 hours around cutover, except urgent completions. Agree a manual fallback in advance for property or settlement funds.
Get written sign-off on the opening trust position from the person accountable for compliance. That might be the managing partner, the designated trust account signatory or, in England and Wales, the COFA.
Looking to streamline vendor RFP selection?
Access pre-negotiated tier discounts through our independent institutional network.
Rebuild Rate Tables and Tax Settings, Then Prove Them on Real Invoices
Rate and tax errors are dangerous because nothing visibly breaks. The invoice still prints. It just shows the wrong number. Before you configure anything, map your rate hierarchy in full: standard timekeeper rates, client-specific rates, matter-level overrides, capped and fixed-fee arrangements, volume discounts, task-based codes such as UTBMS for LEDES clients, and multi-currency billing if you use it.
Tax treatment varies internationally far more than most vendors' default templates assume. A UK firm needs standard-rate VAT plus place-of-supply and reverse-charge handling for cross-border business clients. An Indian firm has to deal with GST, including the reverse-charge rules that commonly apply when legal services are supplied to businesses. Australia charges GST and the Gulf states charge VAT at different rates, and Saudi Arabia adds ZATCA's e-invoicing requirements. Most US states don't tax legal services, though a few tax some professional services. Several jurisdictions mandate e-invoicing, including Saudi Arabia, Mexico, Italy and India for taxpayers above a turnover threshold. If you operate in one of them, make sure the new system can issue compliant invoices from day one. If it can't, you may not be able to issue valid invoices at all. Have your tax adviser confirm current rates and rules for each entity.
Test with 10 to 15 recent invoices that cover your awkward cases: a capped matter, a foreign-currency client, a LEDES submission, a split-billed matter and a bill heavy on disbursements. Recreate each in the new system's sandbox and compare totals, tax lines and layout to the cent. Any mismatch blocks go-live.
Run One Parallel Cycle With a Fixed Reconciliation Script
Full dual entry, with every time entry keyed into both systems, almost never pays off. Timekeepers stop doing it and the two data sets drift apart within days. Use a controlled parallel run instead. All new activity goes into the new system, the old one becomes read-only, and for the first full cycle finance checks the new system's outputs against expected figures built from the old data.
| When | Action | Sign-off |
|---|---|---|
| Cutover minus 8 to 12 weeks | Data mapping, rate and tax design, sandbox build | Finance lead approves mapping document |
| Minus 4 weeks | Test migration and invoice recreation tests | Billing manager approves test invoices |
| Minus 5 days | Final billing run in old system; time-entry cutoff | Partners release final pre-bills |
| Month-end close | Close GL; reconcile trust in old system | Compliance signatory signs reconciliation |
| Cutover day (first business day) | Load WIP, AR and trust opening balances; three-way totals check | Finance lead and compliance signatory |
| Plus 5 to 30 days | Live use; weekly WIP and AR spot checks | Billing manager |
| First month-end in new system | Full billing run and first trust reconciliation | Compliance signatory; managing partner |
Hypothetical example: a 25-lawyer firm cuts over with 140 open matters, about USD 310,000 of unbilled WIP and 60 trust ledgers. The script for the first close is agreed in advance. Migrated WIP plus new time, minus billed time, must equal the new WIP report. Trust opening balances plus receipts, minus payments, must equal the bank. If a variance exceeds the agreed threshold (say USD 50 on WIP, zero on trust), the billing run stops until someone explains it.
Sign-Offs, Cost Drivers and Red Flags That Should Pause the Cutover
Budget for the migration separately from the subscription. The figures below are typical 2026 market ranges. They vary a lot by contract and region, so confirm them with vendors. Cloud platforms for small and mid-size firms, such as Clio, LEAP, Actionstep, Smokeball, CosmoLex and PracticePanther, sometimes include a basic data migration. Otherwise, vendor-assisted conversion commonly costs somewhere in the low thousands to around USD 10,000. Mid-size firms that need custom mapping, multiple entities or LEDES setup should plan for roughly USD 15,000 to 75,000 once consultant time is included. Enterprise implementations of platforms such as Elite 3E or Aderant often reach six figures. Internal time is the cost firms usually leave out of the budget. Plan for your finance lead to spend a substantial share of their week on the project, often a third to half, for two to three months.
Costs rise with the number of legal entities and currencies, the amount of transaction history you migrate, custom rate arrangements, e-invoicing integrations and any export fees from the outgoing vendor.
Pause the cutover if any of these come up:
- The vendor can't migrate trust balances at client-matter level, or proposes a single pooled opening balance.
- There's no sandbox for test migrations, or the contract covers only one test load.
- The outgoing vendor needs weeks to deliver a full export, or will only provide it in a proprietary format. Check your notice period and data-return clause now, not in the final month.
- The new system's data hosting doesn't meet your obligations under GDPR, India's DPDP Act, UAE or Saudi data-protection law, or a client's outside counsel guidelines.
- Nobody on your side is named as owner of the trust sign-off.
Closing the First Month and Retiring the Old System
Go-live doesn't end the project. It ends when the first month-end close in the new system produces on-time invoices and a trust reconciliation that balances without manual adjustment. Until then, run a short daily check-in between billing, finance and the vendor's support contact. Log every variance with its cause and fix.
Keep the old system running after cutover day. Either move it to a read-only licence or take a complete export in an open format (CSV plus invoice PDFs), then check that you can actually open and search that export. Retention periods for financial and trust records vary by jurisdiction and commonly fall between five and ten years. Confirm yours with your regulator or accountant before you destroy anything.
The decision rule: if the first month-end close ties out on WIP, AR and trust within your agreed thresholds, retire the old system to archive. If it doesn't, keep read-only access for one more full cycle and fix the root cause before the second close. Your next step is to choose the cutover date, the first business day after a closed month that isn't a tax or year-end period, and send it to your vendor as a contract milestone.