Short version: The migration tool moves your lists and open transactions so the balances tie on day one. But a real part of your setup doesn't come across, and some of what "converts" lands in a thinner form. The table below is the plain-English version, because Intuit's own help pages disagree on the details, attachments and budgets most of all. Read it before you click convert, not after.
The pitch is that QuickBooks Online is just the cloud version of Desktop. It isn't. It's a different product with a different data model, and the conversion is a translation, not a copy. Most of the translation is fine. The parts that aren't are the parts that cost you a weekend.
I've moved client files both directions and cleaned up books that got mangled on the way across. Here's what actually happens to your data, grouped by how much you'll feel it.
Three buckets: comes across clean, converts but lands thinner, and doesn't come across at all. The third bucket is the one that bites.
| Data or feature | What happens on conversion | Verdict |
|---|---|---|
| Comes across clean | ||
| Chart of accounts, customers, vendors, items | Lists transfer intact. | Converts |
| Open transactions and balances | Invoices, bills, and account balances come across so the file ties on day one. | Converts |
| Reconciled status | Reconciled transactions keep an "R" marker in the Cleared column. | Converts |
| Closing date | The Desktop closing date comes across. | Converts |
| Current inventory quantities | Quantities and item accounts transfer; inventory is recalculated FIFO from a date you pick. Requires QBO Plus; Windows only, not Mac. | Converts |
| Profit & Loss budget | The P&L budget converts, if you're on Plus or Advanced. | Converts |
| Converts, but lands thinner | ||
| Payroll history | Comes across as journal entries so the books balance. You lose true paycheck history for the pre-migration period. | Partial |
| Jobs under customers | Become sub-customers. Fine until you run a Desktop-style job report that no longer exists. | Partial |
| Classes and locations | Both exist, but the hierarchy is flatter. Deeply nested Desktop class trees collapse. | Partial |
| 1099 tracking | Comes across, but the account-to-1099-box mapping needs re-verifying after the move. | Partial |
| Reports | The engine is narrower. Complex customizations don't survive and get rebuilt. | Partial |
| Doesn't come across at all | ||
| Attachments | Receipt images and attached documents are stripped. Save them first. | No |
| Past reconciliation reports | The reports don't convert (the "R" markers do). Export every one to PDF first. | No |
| Payroll item detail & employee YTD | Item breakdowns and year-to-date numbers don't convert. Re-enter per employee. | No |
| Memorized reports | None convert. Rebuild and re-memorize each one in QBO. | No |
| Custom fields | Custom fields on customers, vendors, employees, and items are dropped. | No |
| Price levels | Don't convert; QBO can't auto-adjust item prices the same way. | No |
| Closing-date password & Desktop audit trail | The password and the prior audit trail don't come across. The new file is open to edits in prior years. | No |
| Non-P&L budgets | Balance Sheet and other budget types don't convert. | No |
| Sales orders, statement charges | No true equivalent in QBO. Open sales orders arrive as estimates and lose status. | No |
Where Intuit's help pages conflict, this reflects what actually lands in the file. Verify the specifics for your edition against Intuit's current conversion documentation, since behavior changes release to release.
The backbone transfers. Your chart of accounts, your name and item lists, your open invoices and bills, and your account balances all come across, so the converted file ties to Desktop on the conversion date. Reconciled transactions keep their status, the closing date follows, and current inventory quantities move (recalculated on FIFO from a date you choose, on Plus, Windows only). If all you care about is a file that balances, the tool delivers that.
This is the bucket people underestimate. The data is technically there, but the shape changed.
Payroll is the clearest example. Your payroll transactions come across as journal entries so the ledger balances, but you can't pull a real employee paycheck history for anything before the move, and the item-level detail is gone. Job costing survives as sub-customers, which looks right until a Desktop job report you relied on simply doesn't exist in QBO. Classes flatten. Reports are the daily one: if your month-end leans on a stack of memorized Desktop reports, budget time to rebuild them and accept you'll lose some fidelity.
These are the ones that generate the "wait, where did it go" support ticket a week later.
Attachments are the big one. Every receipt image and signed document you attached in Desktop is stripped in the move. Past reconciliation reports don't convert either; the reconciled markers follow, but the reports you'd hand an auditor do not, so export them to PDF first. Custom fields, price levels, memorized reports, your closing-date password, the Desktop audit trail, and any budget that isn't a P&L budget all stay behind. None of these stop the file from balancing, which is exactly why they're easy to miss until you need one.
The conversion is capped by your file's Total Targets count. Press F2 in Desktop and read the number. Over Intuit's limit, you can't bring the full transaction history; you convert a recent subset, or start with lists and balances and leave the history in an archived Desktop copy. Check Intuit's current threshold rather than an old number from a forum, because it has moved over the years. Know this before you schedule the cutover, not during it.
The rule I use: a converted file that balances is not a finished conversion. It's finished when it balances and ties to the Desktop reports you saved on the way out. If you didn't save those reports, you have nothing to tie to.
None of this is a reason not to move. Plenty of businesses should, for remote access, integrations, or staffing. It's a reason to save what you need first and to tie the new file out before you trust it. For why a converted file so often doesn't tie, and how to run that down, see the related guides below as they publish. And if you're still deciding whether to move at all, start with what Intuit's 2026 lifecycle change actually means, because there's no longer a deadline forcing your hand.
The Migration Go/No-Go Diagnostic asks 22 questions about your company file (target count, inventory, payroll history, integrations, reconciliations) and tells you whether to migrate as-is, clean up first, rebuild clean, or hire it out, with every reason shown. For the full pre-flight, the Pre-Migration Prep Kit walks the whole checklist.
No. The tool moves your lists and transactions so the balances tie, but a real part of your setup doesn't come across, and some data that converts lands thinner. Attachments, past reconciliation reports, payroll item detail, custom fields, and price levels don't convert.
No. Receipt images and documents attached in Desktop are not carried into QBO. Save anything you need before you convert.
Only Profit and Loss budgets, and only on QBO Plus or Advanced. Balance Sheet and other budget types don't convert and must be re-entered.
Partly. Payroll transactions come across as journal entries so the books balance, but item breakdowns and employee year-to-date figures don't. You re-enter prior totals per employee and lose true paycheck history for the pre-migration period.
No. Reconciled transactions keep their marker, but the reports themselves don't convert. Export every bank and credit card reconciliation report to PDF before you migrate.
Yes. It's capped by your file's Total Targets count (press F2 in Desktop to read it). Over the limit, you convert a subset or start with lists and balances only. Check Intuit's current limit, since the number has changed over time.
General guidance for planning a QuickBooks migration, not accounting, tax, or legal advice. Conversion behavior and platform limits change between releases; verify the specifics for your edition against Intuit's current documentation. Not affiliated with or endorsed by Intuit Inc. QuickBooks® is a registered trademark of Intuit Inc., used here descriptively only.
Next in the series: why a converted file doesn't tie out, and how to run it down. One email per guide. Unsubscribe in a click.