Converting QuickBooks Online Back to Desktop: A Full Migration Playbook

Last reviewed 2026-09-01 5 min read

The QuickBooks Online export tool leaves gaps in history, inventory, and balances. This playbook shows how to rebuild a Desktop file that ties.

Moving from QuickBooks Online back to Desktop is a rebuild, not a simple export. The built-in tool gives you a starting point, but what the built-in export misses controls how much manual work remains. Lists and account balances usually survive. Closed transaction history, inventory costing detail, sales tax adjustments, and audit trail entries often do not. The playbook below is the order we follow so the final Desktop file ties to the online books.

When to run this playbook

Run this process before you cancel the QuickBooks Online subscription. It applies when you need a going-forward Desktop file, not just an archive of the online data.

Use this playbook when:

you are leaving QuickBooks Online after a subscription, edition, or feature change
you need local access to completed fiscal years
inventory, job costing, or multicurrency history matters to the books
the built-in export has already produced a file you do not trust

A conversion is worth the effort when the Desktop file must keep operating after the switch. If you only need a read-only copy of the online history, a set of saved reports may be enough.

Phase 1: Preserve the online record

Before any export, take a complete read-only snapshot. Do not rely on the export file alone.

Save each of these reports in both PDF and Excel:

Balance Sheet
Profit and Loss
Accounts Receivable Aging Summary
Accounts Payable Aging Summary
Inventory Valuation Summary
Sales Tax Liability
Payroll Liability

Export every list to Excel as well. That includes the Chart of Accounts, Items, Customers, Vendors, Employees, Terms, and Sales Tax Codes. Record the as-of date and the home currency. If multicurrency is active, export the Currency List and any revaluation history. Download customer invoices, bills, and credit memos in batches.

This snapshot is the first rollback point. Everything later is checked against it.

Phase 2: Identify what the export will and will not carry

Run a small trial export if the account allows one. Do not assume the tool preserves every field.

Open the exported Desktop company in a test copy. Compare list counts for customers, vendors, items, and accounts. Check open invoices and unpaid bills. Note whether they arrive with line items or only balances. Check inventory availability and cost. The export often carries quantity on hand but not historical costing layers, bills of materials, or landed costs. Payroll liabilities, sales tax adjustments, and journal entries are commonly flattened or omitted.

Write down each gap. The gap list becomes the rebuild checklist.

Phase 3: Extract lists and transaction detail

Use the QuickBooks Online transaction detail report to get all transactions, splits, and memo fields for the conversion period.

Export each list separately. Start with the Chart of Accounts, Items, Customers, Vendors, Employees, Terms, and Sales Tax Codes. Then export open transactions with their aging dates and original amounts. For closed transactions, decide how much history you must rebuild. Full history for every year is rarely practical. We usually rebuild detail for the current and prior fiscal year, then set an opening balance for older periods.

Make sure every list export contains the same unique names you will use in Desktop. Mismatched names create duplicate records and broken links.

Phase 4: Inventory and multicurrency decisions

Inventory is where a Desktop rebuild most often diverges from the online export. The export may bring item names and current quantities, but not the costing layers that created the asset balance.

Run the Inventory Valuation Summary by item in QuickBooks Online. Compare that total to the Inventory Asset account on the balance sheet. If the two do not match, correct the mismatch in the online file first, or carry the difference as a one-time adjustment dated before the conversion date.

For serial numbered or lot tracked inventory, export quantity on hand by item and location. These fields may not map cleanly into Desktop. For multicurrency, confirm which home currency the Desktop file should use. Revaluation history rarely survives, so plan a single revaluation entry at the conversion date.

Phase 5: Build the Desktop file and tie the balances

Create a new Desktop company file with the correct fiscal year start and tax basis. Enter or import the lists first. Then enter the opening trial balance from the QuickBooks Online balance sheet as of the conversion date.

Bring in open invoices and bills only after the trial balance is in place. Compare the Accounts Receivable and Accounts Payable aging reports to the saved online reports. Enter inventory quantities and current average cost. Let the Inventory Asset account balance match the online balance sheet.

Run the Desktop Balance Sheet, Profit and Loss, Accounts Receivable Aging, Accounts Payable Aging, and Inventory Valuation. Compare each report to the saved QuickBooks Online version. Enter payroll liabilities and sales tax payable as other current liabilities when they exist.

Rollback points

Keep these checkpoints during the project:

after Phase 1: saved online reports are the permanent reference
after Phase 2: the test export defines what the tool can do
after Phase 3: list and transaction exports are clean, before any import
after Phase 4: inventory and currency decisions are fixed in writing
after Phase 5: a verified Desktop backup is made before new transactions

Do not cancel the QuickBooks Online subscription until the final Desktop file passes the tie-out and you have a local backup.

Clean outcome

A clean conversion is not a copy of every online transaction. It is a Desktop file that agrees with QuickBooks Online at the conversion date and can operate going forward. The balance sheet ties. The Accounts Receivable and Accounts Payable agings tie. Inventory value ties to the general ledger. The first new transaction posts without creating an out-of-balance condition. The project is clean when those reports match in both systems, not when the import says complete.