QuickBooks Desktop to Online Readiness Report

Overview

Intuit's official QuickBooks Desktop to Online migration tool has documented limitations: file size caps, target-count limits (250,000 targets on most editions), features that are not supported in QBO, and behaviors that silently change after migration. Running headfirst into these after cutover is painful — reports that worked yesterday stop working tomorrow, and a rollback to Desktop is not trivial because the QBO file's data structure differs from the Desktop file's in ways that no third-party tool can perfectly reverse.

The QBO Readiness Report analyzes your Desktop file across four dimensions. Technical compatibility: file size, target count, list sizes against QBO's ceilings. Feature usage: which Desktop features you actively use (inventory assemblies, progress invoicing, custom fields, job costing, advanced inventory, classes, multiple budgets) and how each behaves in QBO. Integration inventory: which third-party apps and bank feeds are attached to your Desktop file and whether equivalents exist in the QBO app store. Data hygiene: how many duplicate names, orphaned transactions, or stale items might complicate the migration.

You receive a written report that lists every issue found, rated by severity, with a recommendation. Some issues are "fix in Desktop before migrating" (for example, reducing lists to get under QBO's name and item limits, or running Super Condense to get the file under QBO's target-count ceiling). Others are "accept the behavior change" (for example, progress invoicing working differently in QBO, or job costing being less granular). A handful are "do not migrate to QBO yet" (for example, a critical integration that has no QBO equivalent and that your business operations depend on day-to-day).

The readiness report is not the migration itself — it is the decision aid you use before deciding whether, when, and how to migrate. Many customers use it to identify pre-migration cleanup work, then schedule the actual migration once their file is ready. Other customers use it specifically to decide against migrating, either temporarily (until a blocking integration becomes available in QBO) or permanently (because the cost-benefit does not work for their specific feature mix).

Canadian-specific considerations are built into the analysis. Canadian Payroll on Desktop has no direct QBO equivalent (QBO Canada uses a different payroll architecture), GST/HST handling in QBO Canada has subtle behavioral differences from Desktop, and Canadian-edition multi-currency handling differs in ways that affect reporting. We flag each of these explicitly in the report rather than treating Canadian editions as edge cases — a common gap in generic QBO readiness assessments produced by US-based consultancies.

Most readiness reports are delivered same-day once the file is uploaded. Very large files (over 1 GB) or files with extensive third-party integrations may take a full business day. The report is delivered as a 4–8 page PDF with severity-rated findings, recommended next steps for each, and a "go / no-go / wait" recommendation at the top. The report is yours to keep and share with your accountant, internal IT, or any other advisor — there are no licensing restrictions on circulation.