What Happens to Your Books When You Switch Legal Billing Software?

When you switch legal billing software, contacts, matters, and open invoices usually migrate cleanly. Your general ledger and your trust history often do not. Whether they survive depends entirely on whether your books lived inside the product you’re leaving or in an accounting system you own separately.

Vendor migration checklists cover the first list well. The second list is where firms get hurt, and it doesn’t appear on the checklist because it isn’t the vendor’s to fix.

What usually migrates without much trouble

Client and contact records, matter records with their open/closed status, custom fields, and staff users all move reasonably well between modern products. Most vendors have done this migration hundreds of times and have tooling for it.

Open accounts receivable usually moves as an opening balance per client, which works for collections but flattens the detail. If you need the original line items on a two-year-old invoice, ask whether those survive.

Unbilled time in progress is the first thing that gets awkward. Work in progress, meaning time and costs recorded but not yet invoiced, is a real asset and it moves inconsistently. Some migrations carry it as draft entries. Some carry it as a lump. Some ask you to bill everything before cutover, which is a reasonable answer if your calendar allows it. Our guide to work in progress reports covers what that balance is actually worth.

The general ledger is the part nobody plans for

If your billing product also held your general ledger, switching billing products means switching accounting systems. Those are separate projects and firms routinely discover that mid-migration.

A general ledger migration needs, at minimum: a trial balance as of the cutover date, the chart of accounts mapped to the new system’s structure, opening balances for every account, and enough historical detail that you can answer a question about last year without logging back into a product you’ve cancelled.

If your general ledger lives in QuickBooks Online and the billing product connects to it, none of that happens. You disconnect one integration and connect another. The ledger, the history, the reconciliations, and your accountant’s access are untouched, because the accounting system was never the thing you were replacing. That difference is the whole practical argument for keeping billing and accounting on separate lines of ownership, and our post on why billing and accounting shouldn’t live in separate systems works through the other side of the tradeoff.

Trust history is the one with a deadline attached

Individual client trust ledgers are the records a bar examiner asks for, and they are not optional to produce. Retention periods vary by jurisdiction, so read your state bar’s trust account rule for the period that applies to you. In every case the period outlasts a typical software contract.

Three questions to answer before you sign anything:

1. Can the outgoing product export individual client trust ledgers, not just an account summary? Ask for a sample of the actual export file. Dates, matter attribution, running balance per client, and transaction type all need to be in there.
2. Will the new system accept that history, or only opening balances? Most accept opening balances. Fewer accept full transaction history. If it’s opening balances only, your historical trust record now lives in a file rather than a system, and someone has to own that file.
3. Who keeps access to the old system, and for how long? Read-only access after cancellation is sometimes available and rarely automatic. Negotiate it before you cancel, not after.

If your trust ledger is maintained in QuickBooks Online as client trust liabilities on the balance sheet, this problem mostly disappears. The history stays in the accounting file the firm owns, and the billing product change doesn’t touch it.

What to do before you cut over

Run the cutover at a clean boundary. Month end works. Quarter end works better. Year end is best if you can wait, because it aligns the switch with the point your accountant already closes and reviews.

Before the switch, produce and save outside the system: a trial balance, a general ledger detail report, an accounts receivable aging, a work in progress report, and individual client trust ledgers with a matching three-way reconciliation as of the cutover date. Save them as files, in a place the firm controls, with the date in the filename. These are the documents that let you answer a question in two years without a vendor’s help.

Then reconcile the first month in the new system against the last month in the old one. If the numbers agree, the migration worked. If they don’t, you want to know in week four rather than at year-end, and our month-end close checklist for QuickBooks Online is a reasonable place to start that first close.

Frequently asked questions

Does switching legal billing software affect my accounting? Only if your accounting lived inside the billing product. If your general ledger is in a separate accounting system such as QuickBooks Online, changing billing software changes an integration and leaves the books alone.

Will my trust account history transfer to the new system? Usually as opening balances, sometimes as full transaction history. Ask for a sample export before you commit, and confirm it contains per-client detail rather than an account-level summary.

What happens to unbilled time when I migrate? It varies by vendor. Some carry work in progress as draft entries, some as a balance, and some recommend billing it out before cutover. Ask specifically, because unbilled time is revenue you have already earned.

When is the best time to switch billing software? At a closed period boundary, ideally year end. That aligns the cutover with a point your accountant already reconciles and reviews, which makes verifying the migration far easier.

How long should I keep access to the old system? At least through your jurisdiction’s trust record retention period, or until you have verified exports covering it. Negotiate read-only access as part of the cancellation rather than assuming it will be there.