Disclaimer: QuickBooks.ninja is an independent site and is not affiliated with, endorsed by, or sponsored by Intuit Inc. "QuickBooks" is a registered trademark of Intuit Inc., used for identification and reference purposes only. See our Terms.

Guides / conversions · 11 min read · Updated August 2026

QuickBooks Online to Desktop: What Actually Transfers

A practical guide to moving a QuickBooks Online company back to QuickBooks Desktop -- why the built-in export falls short, which lists and transactions carry over, what has no Desktop equivalent at all, and how to verify the result before you cancel the subscription.

Going Backwards Is a Real Requirement

Most migration guides assume you are moving to the cloud. Plenty of businesses need the opposite. Speed on a large company file, inventory workflows that behave predictably, an accountant who works Desktop-first, or simply the end of a subscription that renews forever -- the reasons are ordinary, and the direction is legitimate.

What stops people is the history. Years of transactions live in the Online company, and starting a Desktop file from zero throws away the thing that makes the books worth having.

This guide covers what actually moves, what cannot, and how to check the result.

Why This Is Not a File Conversion

QuickBooks Online and QuickBooks Desktop do not share a data model. They are separate products that describe the same accounting reality using different internal structures. A customer, an item, a tax line and an estimate are each stored differently on the two sides.

The practical consequence is that nothing is copied. Every record has to be re-created in the Desktop file, and every internal reference -- which customer an invoice belongs to, which account a line posts against, which invoice a payment settles -- has to be re-pointed at the Desktop file's own version of that record.

That is where the risk lives, and it is worth being precise about the failure mode. A botched conversion does not usually announce itself with an error. It produces a company file that opens perfectly, looks entirely normal, and quietly disagrees with your accounts by an amount nobody notices until year end. The whole discipline of doing this properly is aimed at that specific outcome.

The Built-In Export: Try It, But Know Its Limits

Intuit does provide an export from QuickBooks Online to Desktop, and you should try it first if your situation is simple. For a small company with a short history and no inventory, it can be all you need.

Its limits are well known:

  • It is version-picky. It targets particular Desktop releases, and the file it produces has to be opened in a compatible one.
  • It strains on larger companies. Long histories and high transaction counts are where it starts failing or timing out.
  • Inventory is its weakest area. This is the single most common complaint, and the most consequential one.
  • Availability varies. Depending on your plan and region you may find it incomplete, or not offered at all.
  • It does not check its own work. It hands you a file. It does not tell you whether that file's balances agree with the reports you were looking at in QuickBooks Online.

That last point is the one that matters most. An export you cannot verify is not finished work.

What Carries Over

Lists come across in full. Chart of accounts, customers, vendors, employees, items, classes, departments or locations, terms, payment methods, tax codes and tax rates, and budgets. Lists are not sampled or filtered -- a transaction cannot exist without the customer, item and account it refers to.

Transactions come across for a date range. Invoices, bills, payments, bill payments, journal entries, estimates, sales receipts, credit memos, refund receipts, purchases, purchase orders, deposits, transfers and time activities. How far back that range goes is a decision, and it drives the size of the job.

The order matters as much as the content: lists have to be written before the transactions that reference them, or you end up with entries pointing at records that do not exist yet.

What Does Not Carry Over

These are not omissions anyone chose. Several are cloud-side constructs with no counterpart in the Desktop file format:

  • Attachments -- files attached to transactions and list entries
  • Audit-log history -- the activity trail from the Online company
  • Bank-feed connections -- these are re-established in Desktop, fresh
  • Recurring templates -- recreated in Desktop as memorized transactions
  • Custom report layouts
  • Payroll history, filings and reconciliations -- outside the scope of a conversion

Reconciliation state in particular does not transfer between the two platforms. You will re-reconcile the first period in Desktop against your statement, and subsequent periods then proceed normally. That is expected, not a defect.

The Four Complexity Drivers

Whether this job is straightforward or genuinely difficult comes down to four features. Check your company for each before planning anything.

Multicurrency. Every foreign-currency transaction carries an exchange rate that has to survive the move, and the destination's currency setup has to exist before any transaction lands in it.

Inventory quantity tracking. Quantities, valuation and the inventory start date all have to reconcile after the move. This one has a sharp edge: an inventory start date later than a transaction's own date will cause QuickBooks to reject that transaction outright. The start date has to be chosen deliberately rather than left at a default.

Automated Sales Tax. QuickBooks Online recomputes tax from the customer's location and ignores explicit tax lines. Tax on the converted side has to be re-checked rather than trusted to have arrived correctly.

Progress invoicing. It has no clean equivalent in Desktop. Each affected estimate chain needs its own decision rather than a blanket rule applied across all of them.

A company using none of these is a simple job. A company using three or four of them is where the real work is, and where an unverified export is most likely to hand you a plausible wrong number.

For the full engineering detail of how this conversion is performed and reconciled, E-Tech Corporation publishes a technical write-up on converting QuickBooks Online to Desktop.

Choosing the Target Edition and Year

Decide this before anything else, because QuickBooks Desktop company-file upgrades are one-way. A file built for a later release cannot be opened in an earlier one. If you build for 2024 and the machine you actually use runs an older year, the file is useless to you and there is no way back down without redoing the work.

Pro, Premier and Enterprise are all valid destinations. Pick based on the licence you will genuinely be running, not the newest thing available.

How to Verify the Result

Do not take the file on trust, and do not cancel your subscription before you have done this. Keep QuickBooks Online active -- read access is enough -- through at least the first verification pass, so the source is still there to compare against.

Open the Desktop file and compare these against the same reports in QuickBooks Online:

  1. Trial Balance -- the single best whole-file check
  2. Balance Sheet
  3. Profit & Loss for the full converted range
  4. A/R and A/P aging summaries
  5. Bank and credit-card register balances

If inventory is in play, also check on-hand quantities and inventory valuation, since that is the area most likely to have gone wrong quietly.

Once those tie out, the Desktop file is yours and the subscription is your decision.

One Thing Worth Saying Plainly

A conversion does not fix your bookkeeping. Errors in the Online company arrive intact in the Desktop file -- the work translates what is there rather than re-coding it. If your P&L or balance sheet already looks wrong in QuickBooks Online, sort that out first. Converting a problem simply moves it somewhere harder to find.