A realistic look at what happens when you migrate from QuickBooks Desktop to QuickBooks Online, what actually carries over, and the things that consistently get left behind.
You're reading this because something is forcing the question. Maybe Intuit emailed you about an end-of-support date for your specific Desktop version — those dates roll year by year, and your version may be on the list. Maybe your accountant wants real-time access during quarterly reviews and is tired of waiting for an Accountant's Copy. Maybe the office laptop running Desktop is dying and the IT cost of keeping it alive doesn't pencil. Maybe you've been running an old perpetual-license QuickBooks Desktop for years — a Pro 2018, a Premier 2020, something you bought once and never had to think about — and now the Windows machine it runs on is failing, or you've upgraded to a newer Windows that won't run it, or payroll and bank feeds stopped working long ago and you've finally hit the limit of what you can do without them. Maybe a new CFO walked in and said, "Why are we still on Desktop?" Maybe a bank, an auditor, or a private-equity diligence team needs cloud access and Desktop is the blocker. Maybe payroll keeps breaking, or your remote bookkeeper needs to stop driving in to use the file, or a multi-entity restructure is making the file-per-company Desktop model untenable.
The specific trigger matters less than what it implies: the decision isn't really whether to move, it's how and when. Once you're at that point, the questions worth answering are practical ones. What does the conversion actually do? What carries over and what doesn't? What's the original file's role after the move? When do you decommission Desktop — and what does that even mean?
This guide answers those, in that order.
Before anything else, decide how you're going to make the move. There are four realistic paths and the right one depends less on company size than on what you care about preserving. Intuit's free conversion tool, built into QuickBooks Desktop, is the default — fast, supported, and good enough for most clean files. A third-party migration service (Dataswitcher, MoveMyBooks, and others) costs money but handles edge cases the free tool doesn't, particularly around inventory and historical detail in larger files. Manual entry — starting fresh in QuickBooks Online with only opening balances — is the right answer surprisingly often, especially for companies whose QuickBooks Desktop file has accumulated years of cruft that nobody wants to bring along. And hiring a professional to handle the whole thing is the right answer when the file is complex enough that the cost of the migration is small compared to the cost of getting it wrong. Pick the path before you start planning the details, because every other decision below depends on it.
Picking the path requires knowing what you have. Before you can choose between Intuit's free tool, a third-party service, manual entry, or a professional, you need an honest analysis of your QuickBooks Desktop file against what QuickBooks Online can hold. Some things will land effortlessly — chart of accounts, customers, vendors, the bulk of your transactions. Some things will need adjustment but will fit — class hierarchies that flatten, custom fields that consolidate. Some things won't fit at all without help — assemblies that need to become bundles, custom fields beyond the QuickBooks Online cap, attachments that don't transfer. For each gap, the question is the same and it's a business question, not a technical one: how important is this to you? Can you live without it? Is there a workaround inside QuickBooks Online that's good enough? Is the loss painful enough to justify a third-party tool, a manual reconstruction, or a different platform entirely? The analysis is what turns "we have a problem" into "here are the specific problems and what each one is worth solving." Without it, every other decision is a guess.
The next decision is how much history you're moving and how you'll handle access to whatever you leave behind. There are essentially three approaches. The full migration brings everything across in one move — all years, all transactions, all detail that the conversion tool can carry. It produces the most complete QuickBooks Online file and the cleanest mental model going forward (one system, one source of truth), but it's the slowest, the most likely to hit conversion limits, and the most likely to import old cruft along with the data you actually want. The clean cutover starts QuickBooks Online from a recent date — typically the start of the current fiscal year, sometimes the start of a quarter — with only opening balances and master data, no historical transactions. It's faster, cleaner, and forces the historical-access question to be answered explicitly: the QuickBooks Desktop file becomes the system of record for everything before the cutover date, and the company commits to a retention plan to keep it accessible. The partial migration sits in the middle: a year or two of recent transaction history comes across for continuity, older history stays on the QuickBooks Desktop side. Most industry professionals — accountants and bookkeepers who do migrations regularly — lean toward the clean cutover for any file with meaningful complexity or age. The reasoning is consistent: a clean QuickBooks Online file is easier to work in day-to-day, the conversion gotchas matter less because there's less data to mishandle, and the historical record is preserved in its original form rather than in a partially-translated copy. The trade-off is that you now have two systems to think about — current books in QuickBooks Online, history in QuickBooks Desktop — and you need a real plan for accessing the historical side as the years go by, especially after your QuickBooks Desktop subscription ends. The state of the books matters too. If your QuickBooks Desktop file is well-maintained and the numbers tell a clean story, bringing everything across can make sense — the work has already been done, and you carry it forward. If the file has accumulated question marks — uncategorized transactions, mystery balances, reconciliation gaps, accounts nobody can quite explain — starting over is often the saner move, because a clean cutover is also a chance to leave behind problems you'd otherwise be importing for the next decade. There is no right answer in the abstract; there is only the right answer for a particular company at a particular moment. That plan is the next part of the conversation.
The first piece of planning is taking stock of your customizations — the things you've built on top of the standard ledger over the years. Custom fields, class and location hierarchies, memorized transactions, recurring templates, saved reports, item assemblies. These are the layers most likely to lose something in translation, and they're the layers least visible until you go looking for them in QuickBooks Online and find they're not quite what you remembered. Walking your file once, with a notepad, will save you a quarter of bewildered reports later.
The second piece is your documents. Attachments — scanned bills, signed POs, engineering drawings, anything you've clipped to a transaction in QuickBooks Desktop — do not migrate. If your workflow leans on them, you need to decide before the move whether you'll extract them, keep the QuickBooks Desktop file accessible afterward, or both. This is a decision that gets harder the longer you wait, because Intuit's post-migration access window has a clock on it and your QuickBooks Desktop subscription is finite.
The third piece is reconciliation. Reconciled-status preservation through the conversion is inconsistent — in practice, recent reconcile periods tend to come across with their flags intact, older history less reliably. Behavior varies by Desktop version, file size, and which migration path you use. Reconciling as far forward as possible before you migrate maximizes the amount of history that survives the trip with its flags attached, and minimizes how much you'll need to re-reconcile manually in QuickBooks Online. For most companies this means doing one extra reconcile, on purpose, right before the move.
The fourth piece is the trial run. Intuit doesn't have a dedicated preview feature, but the same effect is easy to achieve: sign up for a free QuickBooks Online trial — QuickBooks Online Advanced is the usual recommendation because it accepts the widest range of data — and run the conversion into that trial account. You'll see exactly what your books look like on the other side. If the result is what you want, that trial becomes your real QuickBooks Online file. If it isn't, you note what needs fixing on the QuickBooks Desktop side, abandon the trial, and start a fresh one with a different email when you're ready to do it for real. The first conversion is rarely the one you keep — it's the one that tells you what to fix before you do the real one. Two practical notes: each QuickBooks Online account has a 60-day window from the moment you create it to accept a migration, so don't start the trial until you're realistically within a month of being ready; and a "fresh" trial requires a different email address, which is why accountants and migration consultants typically use a separate email per client.
The last piece is a quiet one: deciding what your QuickBooks Desktop file becomes after the move. It doesn't get retired the day the conversion finishes. The file itself is yours and stays on your drive regardless of subscription status — Intuit is explicit that you own the data. But "owning the file" and "being able to open it" aren't the same thing, and the answer depends on which kind of QuickBooks Desktop you bought. Older perpetual-license editions — Pro 2021 and earlier, Premier without the "Plus" suffix, QBPOS 2019, and similar — were sold once and can usually continue operating indefinitely on compatible hardware. Intuit may stop supporting them (no payroll updates, no live bank feeds, no security patches), but the program itself keeps opening the file. The practical limits show up over time: newer versions of Windows may not run the software, reinstallation or activation can become difficult, and connected services that depend on Intuit's servers stop permanently. Many businesses are still running 10- and 15-year-old QuickBooks Desktop installations exactly this way; just as many discover one morning that the machine died and the install media is gone. For them, the retention plan is mostly hardware: keep a Windows machine that can run the software, hold onto the install media, and accept that the clock runs out when the OS or the hardware does.
Current QuickBooks Desktop — Pro Plus, Premier Plus, and Enterprise, all of which are annual subscriptions — works differently. When the subscription lapses, the software locks. Intuit's Pro Plus, Premier Plus, and Enterprise editions provide one year of view-only access after the subscription ends; after that year, you need to renew or you can't open the file at all. So the retention plan has to answer a concrete question: how, specifically, will someone read this file two, five, or seven years from now? Options include keeping an active subscription longer than you otherwise would, extracting the data you actually need into an open format before the access window closes, or planning to renew a single year of subscription only when something needs to be looked up. None of these answers is wrong. Not answering the question is what creates the problem.
Riverside Plumbing is a small residential plumbing contractor with six employees. They've been on QuickBooks Desktop Pro for eleven years. Their bookkeeper, Dana, runs a clean shop: chart of accounts is tidy, customer list is current, no inventory tracking, no class tracking, payroll handled by an outside service so it lives in QuickBooks Desktop only as journal entries. Their file is about 180 MB and contains around 47,000 transactions.
Dana's reasons for moving to QuickBooks Online are straightforward: their CPA wants real-time access during quarterly reviews, the office laptop running Desktop is on its last legs, and Intuit keeps emailing about end-of-support dates for older Desktop versions.
Dana followed the standard procedure. She updated QuickBooks Desktop to the latest release, ran a verify-and-rebuild, made sure the file was under the 750,000-target-count limit, and from the File menu chose Utilities → Move QuickBooks file → Export company file to QuickBooks Online. The tool created an Intuit-side account, asked her to confirm the QuickBooks Online subscription tier, and started the upload. Riverside's file finished in about 90 minutes.
Most of what mattered to Riverside came across cleanly:
| Carried over | Didn't carry over |
|---|---|
| Chart of accounts (98 accounts) | Reconciled status on transactions older than the most recent reconcile |
| Customers and jobs (1,200+) | A handful of "memorized transactions" Dana relied on |
| Vendors (340) | Document attachments on bills and invoices |
| Open invoices, bills, and balances | Customer "notes" fields (transferred to a single combined notes field, formatting lost) |
| Full transaction history (within QuickBooks Online limits) | Custom-field labels on customers (data came in as generic Custom 1, Custom 2, Custom 3) |
For Riverside, the losses were annoyances, not blockers. Dana spent about a day in QuickBooks Online re-marking the most recent reconcile, renaming the custom fields, and rebuilding two recurring transactions she actually used. The attachments were the most painful — Riverside had been attaching scanned vendor invoices to bills as a paperless workflow, and none of them came through. She ended up keeping the old QuickBooks Desktop file accessible (her subscription provides one year of view-only access after it ends, and she planned to renew briefly if she needed access beyond that) and downloaded the attachments manually as she needed them.
Net result: about eight hours of cleanup, a working QuickBooks Online file, and a backlog of attachments to handle reactively.
Midland Industrial is a custom metal fabricator with 40 employees, six departments, and inventory. They run QuickBooks Desktop Enterprise with the Advanced Inventory add-on, Class tracking (by job), Location tracking (two warehouses), payroll in-house through QuickBooks Desktop Payroll, and roughly 30 custom fields across customers, vendors, and items. Their file is 4.2 GB. Transaction count is well into seven figures.
Midland's controller, Ray, has been postponing the move for two years. The CFO finally drew a line: with end-of-support dates closing in on their current Desktop version, they're moving to QuickBooks Online Advanced by year-end. Ray's first phone call was to their long-time CPA, who said, in so many words, "You can run the conversion, but plan for things to be off when you're done."
Ray ran the same Intuit conversion tool Dana did. There is no other free path; the only difference is QuickBooks Online Advanced (Midland's target tier) supports class and location, where the lower tiers don't.
The upload took six hours and required two retries — once because of an oversized attachment, once because a corrupted inventory item caused the export to fail mid-stream. After the second retry, the conversion completed.
This is where the story diverges from Riverside. The core books came across, but every layer of complexity Midland had built in QuickBooks Desktop lost something on the way:
Six weeks of accountant and bookkeeper time to triage. A new custom-field strategy (some fields moved to a different system entirely; some became line-item descriptions; some were simply abandoned). A separate retention plan for the QuickBooks Desktop file itself — the one-year view-only window that comes with subscription expiration wasn't enough for a manufacturer with seven-year retention obligations, so Ray planned for ongoing access to the file beyond what Intuit's subscription terms alone would provide. And a quarter of awkward reports while the team learned what "Unspecified" meant in every QuickBooks Online summary.
Net result: the conversion succeeded — the books balance, the GL is intact, payroll YTDs are accurate. But the institutional memory wrapped around those numbers (the classes, the custom fields, the attachments, the reconcile history) is partially or entirely on the Desktop side, on a file that won't be supported forever.
Across hundreds of conversations with businesses post-migration, the same six issues come up over and over. They're ranked here roughly by frequency — the most common at the top.
Documents attached to QuickBooks Desktop transactions (scanned bills, receipts, engineering drawings, signed POs) do not migrate. The QuickBooks Online record will exist; the attached file will not. If your workflow leans on attachments, you'll need to keep the QuickBooks Desktop file accessible — or extract attachments before your access to the file becomes limited.
Reconciled-status preservation through the conversion is inconsistent and tends to be limited primarily to recent reconciliation periods. Recent flags often carry across; older history is hit-or-miss and varies by version and migration path. The full bank-reconciliation audit history — who reconciled what, on which date, against which statement — stays on the Desktop side regardless of what the flags look like in QuickBooks Online.
For very large or complex files, Intuit may bring inactive accounts and old transactions across as summary opening-balance entries rather than the original detail. This isn't the default outcome for most migrations, but it does happen — typically when the file is at or beyond the migration tool's size limits, when certain transaction types aren't supported, or when condensing is required to fit. The result, when it occurs, is that years of historical detail collapse into opening balances on day one of the QuickBooks Online file. Worth checking specifically against your file's size and the current target limits before you assume your full history is coming with you.
Classes and locations come across as names, but hierarchy is flattened, and any transaction that didn't have a tag in QuickBooks Desktop ends up tagged "Unspecified" in QuickBooks Online. Reports that depended on the hierarchy or on every transaction being tagged need to be rebuilt and back-filled.
QuickBooks Desktop's distinction between Inventory Part, Inventory Assembly, and Non-Inventory Part doesn't have a clean equivalent in QuickBooks Online. The most common pattern is that assemblies end up represented as bundles, but bundles aren't a one-to-one substitute — they track quantity, cost, and BOM behavior differently. Manufacturing workflows, work-in-progress logic, and assembly cost history rarely survive the trip intact. Companies that use BOMs or build-and-stock workflows often need to redesign their inventory structure for QuickBooks Online's model rather than expect the conversion to preserve it.
QuickBooks Desktop allows many custom fields with descriptive labels. QuickBooks Online is far more restrictive — exact caps depend on subscription tier, entity type (customer, vendor, item, transaction), and have changed across recent Intuit updates, so the right thing to do before migrating is verify the current limits against your file rather than rely on a number that may already be stale. Excess fields typically come across as generic Custom 1, Custom 2, Custom 3 — or are dropped entirely. Anything beyond the QuickBooks Online cap stays on the Desktop side with no place to land.
Both Dana and Ray would tell you the same thing in retrospect: the migration itself is the easy part. The hard part is knowing what you have, knowing what you're going to lose, and deciding what to do about it before the conversion happens — not after.
Before you run the converter, document everything in your QuickBooks Desktop file that lives outside the standard ledger:
Attachments don't migrate. If you've been using QuickBooks Desktop as a document repository, decide before the move whether you want to extract them or rely on continued access to the Desktop file afterward. There are tools that bulk-extract QuickBooks Desktop attachments by transaction; this is worth doing while QuickBooks Desktop is still fully functional, not after.
The conversion will preserve reconciled flags on transactions that were reconciled as part of the most recent reconcile. Anything before that period typically comes across un-reconciled. Reconciling everything as recently as possible — even completing a partial-month reconcile — maximizes how much of the reconciled status carries over.
Intuit lets you do a trial conversion. You can convert a file into a temporary QuickBooks Online sandbox, look at what happens, decide whether the result is acceptable, and then either keep that conversion or run it again with a freshly-prepared QuickBooks Desktop file. Use this. The first conversion is rarely the one you keep.
The conversion finishing is the start of the work, not the end. A reasonable post-conversion checklist:
For most small businesses with clean files — companies that look like Riverside — Intuit's free conversion tool works fine. You'll spend a day or two cleaning up, you'll lose your attachments, and your books will be where you want them. That's a reasonable trade.
For complex companies — companies that look like Midland — the conversion is the beginning of a multi-week project, not the end of one. The books will balance, but the institutional knowledge wrapped around them needs to be reconstructed, and a meaningful slice of historical detail will live on the Desktop side for as long as you can keep it accessible.
The single most useful thing you can do before clicking "Convert" is to be honest with yourself about which company you are.
If you've worked through this guide and you're starting to wonder how to make the migration itself defensible — how to know later what your books looked like before the conversion, what changed during it, and what didn't survive — see Sealed Ledger's approach to migration.