Migrating QuickBooks Desktop to QuickBooks Online: What Stops the Move
Moving a Desktop company file to QuickBooks Online hits walls at every step — file size, hosting, payroll timing, and the migration window. Here is what to check.
QuickBooks Desktop users looking to move their company file to QuickBooks Online routinely run into the same set of obstacles: oversized files, data stored on hosted environments, payroll sync timing, and a strict migration window that closes without warning. The accepted community guidance walks through the preparation steps that determine whether the built-in migration tool succeeds or fails silently.
Check Your File Size Before Anything Else
The single most common barrier is file size — but not in the way most users expect. QuickBooks measures eligibility by target count, not raw megabytes. Open QuickBooks Desktop and press F2 (or Ctrl+1) to bring up the Product Information window. Look for the Total Targets figure. If that number is below 4,000,000, the file is small enough to migrate. If it exceeds that threshold, the file must be condensed before the move can proceed.
Verify and Rebuild Before Migrating
Even a file that passes the size check can carry hidden structural problems. Running the Verify Data utility checks the file for damage; if Verify reports issues, running Rebuild Data attempts to repair them. Skipping this step risks carrying corrupted transactions into the new Online environment, where they become harder to isolate and fix.
Local Copies Only — No Hosted Files
The migration tool requires the company file to sit on a local drive. Users running QuickBooks Desktop through a hosting provider — Rightworks, for example — must obtain a local copy of their company file from that provider before attempting the export. The tool cannot pull a file directly from a remote hosted environment.
Payroll Requires Extra Preparation
Users who run payroll in Desktop face additional steps. Employee information must be current, and any employees with no pay history in the current calendar year should be deleted before migration. After running payroll, the guidance calls for waiting two to three business days for everything to sync. The migration itself should finish at least seven business days before the next scheduled payroll run to avoid delays in processing.
The Migration Window Is Finite
QuickBooks Online enforces a time limit on new subscriptions during which a Desktop file can be imported. Users who signed up for QuickBooks Online themselves have 90 calendar days from the signup date. If an accountant set up the Online account on the user’s behalf, the window extends to 180 calendar days. Once that window closes, the built-in migration tool can no longer push the Desktop file into that Online company.
Country and Admin Requirements
The QuickBooks Online company must be registered in the same country or region as the Desktop file. A mismatch here blocks the migration outright. The user also needs admin-level access to both the Desktop company file and the Online account — standard user permissions are not sufficient.
Running the Export Tool
With the prerequisites met, the export itself runs from inside QuickBooks Desktop. Sign in as the company admin, then navigate to the Company menu and select the option to migrate the company file to QuickBooks Online. (In Enterprise, the path may differ slightly.)
The tool presents a personalized checklist of remaining preparation tasks. Users can work through each item individually or select the option to complete all tasks at once, then continue.
At this point the tool offers a choice: bring all company data — full transaction history included — or bring only lists and balances. The lists-and-balances option carries customers, vendors, the chart of accounts, employees, and items, but leaves historical transactions behind. Users who want a clean start in Online often choose this route; those who need their full audit trail should select the complete-data option.
The tool then prompts the user to sign in to the QuickBooks Online account using the credentials created at signup. After authentication, the user selects the destination Online company from a list. If that destination company already contains data, the import overwrites it — so verifying the target before confirming is essential.
What the Tool Handles Automatically
Once initiated, the migration runs in the background. The Desktop file remains usable during the process, though Intuit recommends not making significant changes while the export is underway. The Online company receives lists first, then transactions, with progress visible in the Online dashboard.
When the Built-In Path Falls Short
The migration tool covers the standard scenario, but it does not handle every situation. Files that have been condensed repeatedly over the years, files with damaged transaction links that Verify does not catch, and files in older Desktop formats that predate the current migration infrastructure can all produce incomplete imports or fail outright. Users whose files exceed the target limit and who are weighing whether condensing is worth the tradeoff in historical detail can also evaluate alternatives before committing to the move.