QBO Readiness Report

What the readiness report covers

The report covers twelve categories: chart-of-accounts compatibility against QBO conventions, list sizes against QBO's own ceilings, classes and locations versus QBO's tagging model, recurring transactions, advanced inventory, multi-currency posture, payroll history portability, attachment storage, custom fields, sales-tax configuration, bank-reconciliation history, and Desktop-only integration apps. Each category receives a verdict — clean migration, simplified migration, or manual rebuild required — plus a concrete remediation step quoted against the relevant service in this Portal. The structure is reusable, so a second readiness report after remediation produces a like-for-like comparison.

What the report does not promise

We do not run Intuit's actual Desktop-to-QBO migration during the readiness diagnostic and we do not guarantee what Intuit's tool will do on any specific file. The report applies the publicly documented migration rules and our own field experience from Canadian practices to predict the outcome of the migration with high confidence; it is not a substitute for actually running the migration. The intent is to surface every meaningful landmine before you commit, so that the actual migration is uneventful — which is the opposite of running the migration first and discovering surprises three months in.

Why this is read-only and same-day

The diagnostic does not modify your file in any way. We open a copy in our isolated Canadian processing environment, run the inspection passes, write the report, and discard the working copy. No tables are touched on the source, no transactions are re-keyed, no preferences are changed. That is what makes the same-business-day turnaround an honest target — we are not rebuilding anything, we are reading. If the report surfaces issues that need rebuilding, those rebuilds are separate paid services in this Portal and the report tells you which one fits each specific finding.

Should I run remediation services before or after the readiness report?

Run the readiness report first. The report tells you which remediation services to buy and which ones not to bother with, which is consistently the cheapest way to allocate the next dollar. Buying remediation services blind, on the assumption that they are obviously needed, is how practices end up with a clean Multi-Currency Removal followed by a discovery that the actual migration blocker was advanced inventory all along. Twenty-five dollars to know which order to spend in is a small price relative to the cost of the wrong order.

Does the report cover Canadian sales-tax configuration specifically?

Yes. Sales-tax configuration is one of the twelve report categories, and it is the category where Canadian practices most often hit avoidable QBO migration friction because the Desktop sales-tax structure does not map perfectly onto QBO's tax-rate model. The report enumerates every active sales-tax code and item in your Desktop file, predicts the post-migration mapping, and flags any code that would need to be rebuilt manually in QBO. We test the predictions against current QBO releases for Canadian users specifically, not the U.S. defaults that most external guidance assumes.

How does the report handle Desktop-only integration apps?

The report enumerates every integration that has touched your Desktop file via the QuickBooks SDK or Web Connector and categorizes each by its QBO-side availability — same vendor with a QBO build, different vendor required, no QBO equivalent yet. For integrations with no QBO build, the report records what data the integration was writing to the file so you can either pause that workflow during migration or rebuild it on a different platform afterward. The category is one of the most overlooked migration risks and a major reason the report exists.

Will the report tell me whether QBO is actually the right move?

The report is scoped to migration readiness on your specific file, not to the broader strategic question of whether QBO is the right platform for your business. That said, the report's findings often inform the strategic question — a file that scores well on readiness migrates cleanly and the strategic decision becomes easier; a file that scores poorly may be better served by staying on Desktop or by a more substantial pre-migration rebuild. Pre-purchase chat in the Portal can scope a strategic review separately if you want a stand-alone recommendation.