What Actually Converts When You Move from QuickBooks Desktop to Online

QuickBooks Desktop users preparing to move their company file to QuickBooks Online routinely discover that the built-in migration tool is selective about what it carries over. The conversion works well for core financial data, but a number of items don’t make the trip — and knowing that before you start prevents surprises after the import finishes.

How the Migration Works

The export path lives inside Desktop itself. From the company file you want to move, you initiate an export to QuickBooks Online, sign in to your QBO account, and the data is converted into the online company. A few conditions apply. You generally have a limited window — historically 60 days — after creating the QBO company to import Desktop data into it; after that, importing into an existing company becomes more difficult. Your Desktop version should be current, because older versions can lack the export option or handle the conversion less cleanly. And very large files can exceed the conversion’s target-count limits and be rejected outright.

Those limits are worth understanding before you start. QuickBooks Online caps the chart of accounts at 250 entries, and lists such as customers, vendors, and items carry an overall target limit of 750,000 across the entire company. A Desktop file that has accumulated years of data can approach or exceed those thresholds, which is why the migration tool may refuse the file or truncate data without warning.

What Comes Across

Lists convert in most cases: the chart of accounts, customer and vendor records, and item lists typically populate the QBO company without issue. Most historical transactions also make the trip — invoices, bills, payments, deposits, and similar day-to-day entries generally appear in the online company with their original dates and amounts intact.

What Doesn’t Convert Cleanly

Several categories of data either don’t transfer at all or arrive in a diminished form:

• Reconciliation reports and some reconciliation history — prior reconciliation reports are not part of the conversion, and accounts may show as unreconciled for periods that were previously cleared in Desktop.
• Memorized reports and memorized transactions — these need to be recreated in QBO, which uses a different approach to recurring templates and saved report configurations.
• Custom form templates — invoices, sales receipts, and other customized forms do not carry over; QBO has its own template system that must be set up fresh.
• Payroll setup and detail — employee earnings, deductions, year-to-date wage data, and payroll liability records typically need to be re-established in QBO’s payroll module.
• Certain transaction types — including estimates that were never converted to invoices, sales orders, purchase orders in some configurations, and pending builds or assembly transactions, which QBO handles differently or not at all.
• Inventory handling — QBO’s inventory model differs from Desktop’s, particularly around assemblies, multi-location tracking, and unit-of-measure conversions, so those links between transactions can shift or break.
• Budgets and some class tracking nuances — budgets may not transfer, and the way QBO handles classes and locations can differ from Desktop’s class structure.

Prepare Before You Migrate

A few steps before the export can prevent problems during and after the conversion. Update QuickBooks Desktop to the most current release available for your version. Run Verify Data — found under the File menu in the Utilities section — and resolve any errors it surfaces, because a damaged Desktop file can produce a corrupted QBO import or cause the conversion to fail partway through. Take a full backup so you retain an authoritative copy of the Desktop file exactly as it stood at the moment of migration.

Verify After the Import

Once the conversion finishes, compare key figures between the old Desktop file and the new QBO company as of the cutover date. The Trial Balance, accounts receivable and accounts payable aging, and bank and credit card balances should all tie out. If a number is off, the discrepancy usually traces back to a transaction type that didn’t convert or a list entry that exceeded a limit — and catching it early means you can correct it before day-to-day operations resume on the online side.

When the File Is Too Large or Damaged

When the Desktop file exceeds the conversion limits, shows damage that Verify Data cannot resolve, or has accumulated years of obsolete data that inflates its size, a professional file-preparation or migration service can condense the file, repair any structural problems, run the conversion, and verify that the result ties out — so nothing important is silently dropped during the move.