A migration is not a single click — it is a controlled move with a proof step at the end. The tool does the copying; the discipline is what makes the copy trustworthy.
Most businesses reach this guide because the decision is already leaning one way. Intuit has shifted its focus to QuickBooks Online, new Desktop subscriptions are no longer sold to most new U.S. businesses, and each annual Desktop version loses payroll, payments, and security updates a few years after its release. Intuit publishes the current status of each edition on its QuickBooks Desktop pages, and you should read the dates there rather than trust a number quoted secondhand. If your version still does everything you need and is still supported, there is no rule that forces a move today. But for most files it has become a question of when, not if — so it is worth doing the move well the first time.
The whole method runs source to cutover: a cleaned Desktop file is the source, its lists and balances are mapped into QuickBooks Online, the converted file is validated against Desktop, and only then does the business go live. The figure below shows the shape; the steps that follow walk each stage.
The migration, end to end
1 · Clean the Desktop file before you move it
Clean first, migrate second — a conversion copies problems as faithfully as it copies good data, so anything wrong in Desktop arrives intact in QuickBooks Online. Unreconciled accounts, duplicate transactions, a stale undeposited-funds balance, and miscategorized expenses all survive the move. Reconciling that mess once, in the file you already know, is far cheaper than diagnosing it again in an unfamiliar system after cutover. Run your bank and credit-card reconciliations current, clear the undeposited-funds account, and resolve any negative or nonsensical balances now. If the file has years of accumulated drift, treat the cleanup as its own project first — our cleanup method walks that in order. A tidy source is the single biggest thing you control, and it makes every later stage shorter.
2 · Prepare the file and capture the "before" baseline
Before you convert anything, save a complete picture of the file as it stands — this baseline is what you will reconcile against later. Update QuickBooks Desktop to its latest release, back up the company file, and confirm you have admin access. Then export and save, for a fixed date, the trial balance, the balance sheet, the profit and loss, an A/R aging, and an A/P aging. These saved reports are the yardstick: after the move, QuickBooks Online has to reproduce the same numbers for the same date. Note practical limits too — very large files can exceed the conversion's target-count threshold, and Intuit documents both the size limits and the preparation steps in its official QuickBooks help center. Reading those limits now prevents a failed conversion later.
3 · Run the conversion into QuickBooks Online
Run Intuit's built-in export from Desktop into a QuickBooks Online company — this is the mapping stage, where lists, balances, open items, and posted history carry across. In current Desktop versions the path is the Company menu's export-to-QuickBooks-Online option, which prepares the file and moves it into a QBO company you have set up to receive it. Use a fresh, empty QuickBooks Online company as the target; converting into a file that already has transactions mixes two data sets and undoes the whole point of a clean baseline. The conversion runs on Intuit's side and can take from minutes to hours depending on file size, and Intuit emails when it completes. Follow the current on-screen steps and the official migration instructions rather than a remembered sequence, because the exact menu wording changes between versions.
4 · Verify what carried — and what didn't
Immediately after the conversion, check what came across and what has to be rebuilt, because the honest answer is that not everything moves. Lists, account balances, open invoices and bills, and posted transaction history carry over. What changes are the software-specific pieces: memorized transactions, some report and template layouts, the inventory costing method, and most payroll detail — year-to-date figures and prior filings usually need to be set up deliberately in the new file with your payroll provider or CPA. Inventory is the classic edge case, because Desktop and Online can value stock differently and item-level history does not always land the same way. Walk each list and each open-item report in QuickBooks Online against the Desktop original, and write down every gap. This inventory of differences is not a failure of the move; it is the map for the setup work that finishes it.
5 · Reconcile the converted file back to Desktop
Reconcile the new QuickBooks Online file against the baseline you saved — this validation step is what proves the migration, and it is the one most people skip. Open the trial balance, balance sheet, and P&L you exported in step two and confirm QuickBooks Online produces the same balances, to the penny, for the same date. Tie the A/R and A/P totals to the agings you saved, and confirm the inventory asset balance matches. Where a number is off, trace it before you move on — a mismatch here is almost always inventory valuation, a payroll liability that did not convert, or an open item that changed state during the move, and each has a specific fix. A migration is not finished when the data appears in QuickBooks Online; it is finished when the converted file reconciles back to Desktop and every difference is explained. Getting that proof is exactly the discipline behind our methodology.
6 · Cut over and go live in QuickBooks Online
Cut over only once the converted file ties and the rebuild list is done — going live before validation just moves the guesswork into daily operations. Set the go-live date, connect the bank and credit-card feeds in QuickBooks Online, recreate the memorized transactions and report layouts you flagged, invite users and set their access, and finish any payroll setup. Keep the Desktop file archived and read-only as your permanent record of the pre-migration history; you are not deleting it, you are retiring it. Then run the business forward in QuickBooks Online and reconcile the first full month there as normal — the first clean month-end in the new system is the last confirmation that the move held. If the file is large, or inventory and payroll make the validation stage daunting, that is the natural moment to bring in help rather than cut over on a file you cannot prove.
Questions about migrating QuickBooks Desktop to Online
Does everything move from QuickBooks Desktop to Online?
No. Your lists, account balances, open invoices and bills, and posted transaction history carry over. Software-specific pieces — memorized transactions, some report layouts, inventory costing, and most payroll detail — are rebuilt or set up deliberately in QuickBooks Online. Map what changes for your file before you move it, not after.
How far back does the history come across?
The conversion is designed to bring your full posted history within the tool's size limits. If the file is very large or you only need an opening balance and the current year, you can bring balances as of a chosen date and keep the deep history in the archived Desktop file, which stays yours.
Do I have to clean up the file before migrating?
You don't have to, but a migration copies problems as faithfully as it copies good data. Unreconciled accounts, duplicates, and a stale undeposited-funds balance all arrive intact in QuickBooks Online. Cleaning first means you reconcile the mess once, in Desktop, instead of chasing it again in a new system.
How do I prove the migration was accurate?
Save Desktop's trial balance and key reports before cutover, then confirm QuickBooks Online produces the same balances to the penny for the same date. That reconciliation of the converted file back to Desktop is the proof; a migration without it is only hoping the numbers matched.
Should I keep using QuickBooks Desktop instead?
Sometimes. If your version still does what you need and is still receiving service, there is no rule that forces a move. But Intuit has shifted its focus to QuickBooks Online and each annual Desktop version loses payroll, payments, and security updates a few years after release, so for many files the move is a question of when, not if.