QuickBooks Desktop migration for a law firm, without breaking trust records

Many small law firms still run their books in QuickBooks Desktop, often with Clio or another practice management system next to it and a manual export in between. With Intuit retiring older Desktop versions, the question is no longer whether to plan a QuickBooks Desktop migration, but how to move without losing the trust history a bar auditor may ask to see.

The short answer: a QuickBooks Desktop migration moves your lists, balances and most transactions, but not everything a law firm relies on. Past reconciliation reports and the audit trail stay behind, so keep a full archive of the Desktop file before you switch. Pick the destination with your accountant (QuickBooks Online, Xero or, for eligible US firms, Clio Accounting), complete a final three-way trust reconciliation in Desktop, and only then cut over on a clean date.

Why firms are moving now

Intuit's service discontinuation policy states that QuickBooks Desktop 2023 versions (Pro Plus, Premier Plus, Enterprise 23.0 and the Accountant editions) are discontinued after May 31, 2026. As listed in October 2026, the software still opens, but connected services stop: security updates, online banking downloads, payroll, payments, online backup and accountant copy transfers among them. Intuit's suggested paths are an upgrade to Desktop Plus 2024 or Enterprise 24.0, or a move to Enterprise.

For a law firm, losing bank downloads and security patches on the system that holds trust and operating records is hard to justify for long. That pushes many firms to look at cloud ledgers, and at whether the Desktop setup was ever the right fit.

What a QuickBooks Desktop migration carries over, and what it leaves behind

If you go to QuickBooks Online, Intuit's own migration is the usual route. Its help article on what to expect when you switch from Desktop to Online lists, as of October 2026:

What moves

• Lists such as customers, vendors and the chart of accounts.
• Transactions, with reconciled ones marked R and cleared ones marked C in the account history.
• Attachments of 30 MB or smaller stored on your computer.
• Memorized transactions, which become recurring transactions.

What does not move

• Past reconciliation reports.
• The audit trail.
• Memorized reports, custom templates, reminders and mileage.

Two more details matter. Intuit says accrual-basis reports in Online should match Desktop, but cash-basis reports may not, and many small firms run cash basis. And jobs move as Projects in the Plus and Advanced plans; Intuit notes that to keep them as sub-customers you sign up for Essentials first, convert, then upgrade. If your firm tracked clients or matters as customer:job in Desktop, decide which structure you want before you run the conversion.

Moving to Xero is a conversion rather than a migration tool. Xero points firms to conversion options on its QuickBooks page, and the partners offered vary by region and by Desktop or Online source. Some conversion apps, such as Q2X, state that Desktop files must first be moved to QuickBooks Online. Ask the conversion provider in writing exactly which history comes across: full transactions, or opening balances plus open invoices and bills.

Why trust records are the risky part

Trust money is held for clients, not earned by the firm, and the ABA Model Rule 1.15 sets out the duty to safeguard it. Many bars expect regular three-way reconciliations and expect you to keep the records for years. Rules differ by state and outside the US, so check your own obligations with your accountant or ethics counsel.

A migration can damage those records in quieter ways than lost data:

• Reconciliation history disappears. The transactions arrive marked reconciled, but the monthly reports that prove it do not.
• Client-level detail flattens. If each client's trust balance lived in a sub-account or job in Desktop, a conversion that maps differently can merge or rename them.
• Opening balances land in the wrong place. A trust liability posted as income, or a trust bank account mapped to operating, is the most damaging single mistake.
• Two systems disagree on day one. If Clio already holds the client trust ledger, the new ledger's trust balance must match Clio's total on the cutover date.

Choosing where to go

The trust rows come from Clio's help articles: the QuickBooks Online integration exports trust transactions as journal entries, while the Xero integration says trust transactions cannot sync and must be recorded manually. Clio's setup guide for Clio Accounting states it requires Clio Manage and is limited to US firms. Clio also states that Clio Manage does not integrate directly with QuickBooks Desktop, so a move off Desktop is often the moment a firm finally gets a live connection. Features change, so confirm each row with the vendor before deciding.

For a fuller comparison, see our guide to Clio Accounting vs QuickBooks Online vs Xero.

A cutover plan that keeps trust records intact

1. Agree the destination and the date with your accountant. The start of a month is the minimum; the start of a quarter or fiscal year is cleaner. Write the date down.
2. Archive the Desktop file in full. Keep a backup copy, plus PDF or Excel exports of every past trust reconciliation report, the audit trail and client ledger reports for the retention period your bar requires. These do not migrate, so this archive is your proof.
3. Close the last period in Desktop. Reconcile operating and trust bank accounts through the cutover date and complete a final three-way reconciliation: bank statement, trust balance in the books, sum of client ledgers.
4. Map the chart of accounts before converting. Confirm the trust bank account, the client funds liability account, and where Clio revenue, write-offs and expenses will land.
5. Run a test conversion where the tool allows it. Compare the trial balance, each trust account and the client ledger totals against Desktop as of the same date.
6. Reconnect the integrations. Bank feeds and the Clio sync have to be set up again. Our guide to connecting Clio to QuickBooks or Xero covers first-sync mistakes, especially duplicate contacts and trust mapping.
7. Reconcile again at the end of the first month. The first month-end in the new system is where mapping errors show up. Do the three-way reconciliation before anyone relies on the new reports.

Mistakes to avoid

• Assuming "reconciled" means "proved". The R flag moves; the report behind it does not.
• Switching mid-month because the renewal date forced it. A short Desktop Plus renewal can cost less than a messy cutover.
• Running both systems for months. A short overlap for checks is fine. Entering live trust activity in two ledgers is how balances drift.
• Letting the first sync run before mapping is checked. Turn integrations on only after the trust accounts are confirmed.

How Flow Mesh helps

Before a move like this, our stack audit looks at Desktop, Clio and the tools around them, gives each one a verdict (keep, configure, consolidate or replace) and sets out in writing how billing and trust data should flow afterwards. Any build is quoted in writing after the audit and done inside your own accounts, alongside your accountant. See how we work with law firms.

Key takeaways

• QuickBooks Desktop 2023 versions lost connected services after May 31, 2026, per Intuit's discontinuation policy.
• A move to QuickBooks Online carries lists and transactions, but not past reconciliation reports or the audit trail: archive them first.
• Cash-basis reports may not match after migration, and Desktop jobs can change structure, so test before you rely on the new file.
• Finish a three-way trust reconciliation in Desktop, cut over on a clean date, and reconcile again after the first month.
• Choose QuickBooks Online, Xero or Clio Accounting with your accountant, and confirm trust record rules with your accountant or ethics counsel.