Moving a Large Desktop Company File to QuickBooks Online

A large or aging QuickBooks Desktop file can stall or fail on the way into QuickBooks Online; this playbook gets the history across intact.

A Desktop file that has grown for a decade does not export cleanly into QuickBooks Online. It has to be measured, repaired where necessary, slimmed to a size the import can finish, and cut over on a fixed date. Our engineers run this as a staged migration, and this page sets out the stages in order.

Read the F2 screen first

Open the company file in Desktop and press F2. The Product Information window reports the file size, the total target count, the transaction count, and the customer, vendor, and item counts. Note the first transaction date as well, and screenshot the window for the project record.

Targets matter more than file size. The import is measured in targets, and the ceiling Intuit publishes for it is 350,000; long imports turn fragile well below that line. Name and item lists consume room too, so record those counts separately.

Does the file need repair and condense first?

Run Verify from the Utilities menu before anything else. If Verify finds damage, run Rebuild and Verify again, and repeat until it comes back clean. Damage that will not clear is a stop condition; see our QuickBooks Verify and Rebuild repair service rather than condensing a broken file. Condensing damaged data seals the damage into the migration copy.

With a clean file, the question becomes size. A condense summarizes closed transactions before your cutoff into journal entries while preserving account, customer, and inventory balances, and that is what pulls the target count down. Our engineers size the condense from the F2 numbers; condensing an oversized company file is a discipline of its own.

If the counts and the feature list point to a long job, our QuickBooks Online file preparation service covers assessment, repair, and condense as one engagement.

The rollback point sits here. Take a verified backup before the condense and store it away from the working machine. The condensed copy becomes the migration copy; the backup holds every transaction the condense removed.

Choosing the cutoff date

Pick a clean period end, usually the most recent fiscal year end or a later month end. Everything on or before the cutoff is summarized; everything after it carries into the online company in full detail. Open items survive regardless of date, so unpaid invoices, unpaid bills, and payments sitting in undeposited funds must come across still open.

Depth is a cost. Years of detail inflate the target count for history nobody reconciles line by line, and a recent fiscal year end is usually the honest boundary. Decide the date before the condense runs, because the condense is built around it.

What stalls an import mid-flight?

Three Desktop features stop or deform a straight import, and each has to be resolved before export day.

  • Multi-currency. The standard import refuses a Desktop file with multi-currency enabled. The setting has to come off the Desktop file first, or the online company has to be started fresh; there is no conversion in flight. Our Desktop multi-currency removal service handles the first path.
  • Advanced Inventory. Serial and lot numbers, bin locations, and FIFO layers in Enterprise editions have no counterpart online. The items import; that layer of tracking does not. Decide what will track it instead before the cutover.
  • Assembly builds. QuickBooks Online has no build assemblies, so inventory assembly items and their build history will not carry as such. Convert the items, or plan to manage builds outside the ledger, before export day.

Run the cutover on a fixed date

Set the date, and stop all entry in Desktop that morning. Then work the checklist.

  • Take a final backup, confirm it opens, and store it off the machine alongside the working file.
  • Export a trial balance, receivable and payable aging reports, and an inventory valuation as of the cutoff. These are your reconciliation evidence.
  • Record the admin password and the Desktop edition and year that last opened the file, and keep both with the archive.
  • Import into a fresh online company. The import overwrites whatever is already there, so never point it at a company holding live data.
  • Afterwards, tie the online trial balance to the Desktop copy at the cutoff, then match the open invoice list, the open bill list, and the inventory counts.

Keep the Desktop file as the fallback archive

The Desktop file is not decommissioned; it becomes the archive. Keep it read-only on a machine that can still open that version, and leave the old software installed. It answers the history questions the online ledger cannot.

It is also the rollback. Because the import ran into a fresh company and the archive never moved, a disappointing result costs you little: reopen Desktop, resume entry, and re-plan.

What does a clean outcome look like?

The import finishes without timing out. The online trial balance ties to the Desktop balance at the cutoff, and the open receivables and payables match the Desktop aging reports invoice by invoice. Inventory valuation matches within the limits you accepted for assemblies and advanced tracking. The archive opens on demand, and the pre-condense backup sits stored and untouched.

Keep going

Your Desktop doesn’t have to end when Intuit says so.

Start with the master survival guide, or jump straight to the fix you need.