QuickBooks Desktop Regional Conversion: US, UK, CA, and AU Edition Switch

Last reviewed 2026-07-18 4 min read

Converting a QuickBooks Desktop company file between US, UK, Canadian, and Australian editions requires careful database re-mapping to preserve all lists, transactions, and reporting structure.

QuickBooks Desktop is built differently for each regional market. The US edition uses a single currency and a straightforward sales-tax model; the UK, Canadian, and Australian editions enforce multi-currency, VAT/GST structures, and region-specific tax reporting. When a business relocates or restructures across borders, the company file must be converted at the database level so that charts of accounts, tax-agency vendors, and historical transactions map cleanly into the target edition's framework. This playbook walks through the full conversion process.

Prerequisites and Assessment

Before beginning, confirm the source file's health and gather the required information. Open the company file in its native regional edition and press F2 to open the Product Information window. Note the exact version, release, and file size. Run Verify Data from the File → Utilities menu; if Verify reports errors, run Rebuild Data until it passes clean. A file with structural damage must be repaired before any regional conversion begins — converting a damaged file compounds the problems. Record the Admin password; it is required to unlock the file for database-level access.

Pre-Conversion Backup

Create a full portable backup (QBM) and a full backup (QBB) of the source file. Store both on separate media. The QBB serves as the primary rollback point; the QBM provides a compact secondary copy. If the source file exceeds 1 GB, consider running a SuperCondense to reduce list-count and transaction volume before conversion — smaller files convert more reliably and reduce the risk of timeout during the re-mapping pass.

Tax Code and Currency Preparation

In the source file, identify every tax code, tax agency, and tax-rate item currently in use. Print or export the Chart of Accounts, Customer List, Vendor List, and Item List to Excel as reference documents. If the source file has multi-currency enabled but the target edition will operate in single-currency mode, document the current exchange-rate table — those rates will need to be reconciled after conversion. Disable any payroll service subscriptions in the source file, as payroll data is region-specific and does not migrate between editions.

Database Re-Mapping

The core of the conversion involves re-mapping the source database tables to match the target edition's schema. Each regional edition stores tax configuration, currency handling, and regulatory reporting fields in different table structures. The process works directly on the database layer — not through the QuickBooks application interface — to reassign tax-code identifiers, remap VAT/GST categories to their target-edition equivalents, and rewrite the currency-handling flags that differ between editions. For example, the US edition's sales-tax items map to the UK edition's VAT-rate items, the Canadian edition's GST/HST/PST structures map to flat-rate equivalents where a single tax authority exists, and the Australian edition's GST codes map to the target edition's nearest tax-code type. The chart of accounts generally survives intact because account structures are similar across editions; the tax-agency vendor records, however, must be recreated to match the target region's tax-authority naming conventions.

Validation and Integrity Checks

After the re-mapping pass completes, open the converted file in the target regional edition. Press F2 and confirm the Product Information window shows the correct region and version. Run Verify Data immediately. If Verify flags errors, run Rebuild Data and re-verify. Check the following:

Chart of Accounts: Compare account count and balances against the pre-conversion export.
Tax Codes: Open the tax-code list and confirm each code maps to a valid target-edition tax agency.
Customer and Vendor Balances: Spot-check ten records against the source file.
Transaction History: Open the most recent month's register and confirm transactions display correctly.
Reports: Run a Balance Sheet and Profit & Loss for the most recent fiscal year and compare totals to the source.

Rollback Procedure

If the converted file fails validation or produces incorrect balances, abandon the conversion and restore from the pre-conversion QBB backup. Open the restored file in the original regional edition, run Verify Data to confirm the restore is clean, and reattempt the conversion after addressing whatever caused the failure — typically an unresolved data-damage flag or an incomplete tax-code map.

Clean Outcome

A successful regional conversion produces a file that opens natively in the target edition, passes Verify Data with no errors, matches the source file's account balances and transaction totals, and allows new transactions to be entered using the target edition's tax codes and currency settings.