Migrating QuickBooks Desktop Company Files Across Regional Editions

Move a QuickBooks Desktop company file between US, UK, CA, and AU editions when the native file format is incompatible and direct conversion fails.

QuickBooks Desktop regional editions — US, UK, Canada, and Australia — use different database schemas, tax frameworks, and list structures. A .QBW file created in one regional edition will not open in another. When a business relocates or restructures across regions, our engineers rebuild the company file through a structured export, list conversion, and trial-balance reconstruction process.

When to Run This Migration

This playbook applies when a company needs to move financial data from one QuickBooks Desktop regional edition to another and the source file is intact enough to pass a Verify Data check in single-user mode. If the source file is damaged, it must be repaired first — a migration cannot succeed against a file with target chaining errors or a broken balance sheet. Confirm the source edition, target edition, file size (via F2 Product Information), and whether multi-currency or Advanced Inventory is in use before beginning.

Phase 1: Source File Assessment

Open the source file in its original regional edition in single-user mode. Press F2 to record the file size, list counts, and transaction count. Run Verify Data from the File > Utilities menu. If Verify fails, run Rebuild Data and repeat Verify until it passes cleanly. Export a full set of baseline reports: Trial Balance, Balance Sheet by Date, Profit and Loss by Account, AR Aging Summary, AP Aging Summary, and an Item List export to Excel. These reports are the reconciliation target for the finished migration.

Rollback point: The source file is untouched at this stage. If anything goes wrong downstream, the original backup remains the source of truth.

Phase 2: List Export and Conversion

Export every list from the source file: Chart of Accounts, Customers, Vendors, Employees, Items (Service, Inventory, Non-Inventory), Sales Tax Codes, and Terms. In the target regional edition, create a fresh company file with the correct fiscal year and tax structure. Import the Chart of Accounts first, then Customers and Vendors, then Items. Tax code mappings require manual attention — US Sales Tax items do not map directly to UK VAT codes or AU GST codes. Each tax code must be recreated in the target edition's native tax framework and assigned to the correct accounts.

Checkpoint: Compare list counts between source and target. Every customer, vendor, account, and item in the source must exist in the target before transactions are rebuilt.

Phase 3: Trial Balance Reconstruction

Rather than migrating individual transactions — which frequently fail due to schema differences in journal entry structures, payroll items, and tax line mappings — our engineers reconstruct the file using opening balances. The Trial Balance from the source file's earliest migration-period date becomes the foundation. Enter opening balances for every account: bank, AR, AP, fixed assets, equity, and retained earnings. Post a single balancing journal entry to retained earnings if the debits and credits do not tie to the penny.

For ongoing-period transactions, export transaction detail reports from the source and re-enter them in the target edition using the rebuilt lists. Prioritize open invoices, open bills, unpaid checks, and unreconciled bank transactions. Historical, fully reconciled, closed transactions can be represented by summary journal entries by month.

Phase 4: Reconciliation and Verification

Once reconstruction is complete, generate the same reports produced in Phase 1 from the target file. Compare the Trial Balance line by line — every account balance must match the source within zero variance. Reconcile each bank account against the source file's last reconciled statement. Verify that AR Aging and AP Aging summaries tie to the source. Run Verify Data on the target file to confirm structural integrity.

Rollback point: If reconciliation fails, identify the variance, correct the specific entries, and re-run the comparison. If the variance cannot be isolated, restore from the Phase 2 checkpoint and rebuild the trial balance.

Clean Outcome

A successful cross-region migration produces a target file that opens natively in the destination regional edition, passes Verify Data with no errors, and matches the source file's Trial Balance, Balance Sheet, AR Aging, and AP Aging with zero variance. All open transactions — unpaid invoices, outstanding bills, unreconciled bank entries — are present and linked to the correct customers, vendors, and accounts. The source file remains available for reference but is no longer needed for ongoing accounting.

If the source file is too large or contains years of historical data that slows the reconstruction, consider running a SuperCondense before exporting to reduce the transaction volume our engineers must rebuild. For files that also need a version downgrade alongside the regional move, our downgrade and conversion team handles both operations in sequence.