Moving Client Books From QuickBooks Online Back to Desktop

Moving a client from QuickBooks Online back to QuickBooks Desktop is a reverse migration, and it behaves like one. The export tool creates a new Desktop file from the Online data, but it is not a mirror. Fields map differently, some history does not come across at all, and the first close after the switch is where the gaps show up. This article covers the bookkeeping side: what to check before anyone runs the export, and how to prove the new file agrees with the old one.

What the export actually produces?

The migration tool builds a Desktop company file from your Online data, but the two products do not store data the same way. Expect changes in appearance and in some behaviour, not just in the interface. Certain record types and settings do not export at all, and Intuit publishes a list of what is included. Read that list before you commit, not after.

The practical consequence is that the Desktop file is a new set of books, not a continuation. Treat it the way you would treat any conversion: the opening balances and the first reconciliation in the new file are the points where errors surface.

What should you verify before the export?

Run the migration only from a clean, closed period. Reconcile every bank and credit card account in Online through the final month, finish the month-end close, and lock the period. A reverse migration done mid-month leaves you comparing a part-exported month across two systems, which is the worst possible evidence position.

Take a full backup of the Online data and keep your working papers for the closed periods. Once the subscription lapses, historical access to the Online books becomes the hard question, so export any reports you may need as PDFs first: trial balances, reconciliation reports, and the general ledger for the retained years.

How do you prove the new file agrees?

After the export, run a trial balance in Desktop as at the switch date and agree it, account by account, to the Online trial balance. Do not accept a matched net difference of zero. Individual accounts can be wrong in offsetting directions, and a reverse migration is exactly the kind of event that produces them.

Then check the things the export is known to weaken. Aged receivables and payables should tie to the Online versions. Sales tax payable needs particular care, because tax settings frequently map imperfectly between the two products. If the client is registered for VAT or GST, confirm the tax agency and rates before the first filing period in Desktop.

What happens to bank reconciliations?

Reconciled status does not always survive the journey intact. Plan to reconcile the first statement in Desktop as a fresh exercise, and expect to investigate uncleared items from before the switch. If a cheque written months ago never cleared, it must still be sitting in the Desktop register, not silently vanished.

If reconciliation differences appear, work out whether they come from the migration or from ordinary posting errors after it. A difference dated on or before the switch date points at the export. A difference in later transactions is just bookkeeping, and you fix it normally.

When does this stop being bookkeeping?

A reverse migration you planned, from clean and reconciled books, is routine and the export tool handles it. It stops being routine when the export fails partway, when the Desktop file will not open or verify, or when the trial balance will not agree and you cannot isolate why. At that point the data itself is suspect, and that is repair work rather than close work.

Preserve everything before anyone retries: the Online subscription still active, the exported file untouched, and a written note of what was attempted. Repeated failed imports into a damaged file make the eventual repair harder. Our sister service handles QuickBooks data repair and migration recovery, and that is where a failed reverse conversion should go.

The working rule

Close, reconcile, back up, export, then prove the trial balance. If you follow that order, the switch is an evidence problem you can manage. Skip a step, and the first close in Desktop becomes an archaeology project.