What Data Doesn't Transfer When You Migrate QuickBooks Desktop to Xero

Every firm considering a QBD migration to Xero asks the same question: "Will all our data come across?" The honest answer is no. Not everything transfers, and pretending otherwise leads to unpleasant surprises weeks after go-live.

This article gives you a complete inventory of what does and doesn't survive a QuickBooks Desktop to XERO conversion, so you can plan around the gaps before you start.

What Transfers Successfully

Before covering the gaps, here's what does come across in a properly executed QuickBooks to Xero conversion.

• Chart of accounts (with some structural flattening)
• Customer and supplier contact records
• Outstanding invoices and bills
• Journal entries
• Historical transactions (number of years depends on your migration scope)
• Tax codes and rates (mapped to Xero equivalents)
• Account balances and opening balances
• Items and inventory quantities (basic)

A professional QuickBooks Desktop to Xero migration service like WOW BookSwitch covers the current fiscal year plus three prior years in the standard $399 per file price, with additional years available at $100 each.

What Does Not Transfer

Bank Feeds

QuickBooks Desktop stores your bank feed connections and downloaded transaction history. None of this migrates to Xero. Bank feeds are a direct connection between your bank and the accounting software, and that relationship doesn't port between platforms.

What to do: Reconnect bank feeds in Xero after migration. Xero will pull in new transactions from the connection date forward. For the gap between your last QBD bank feed download and the Xero connection date, you'll need to import a CSV bank statement.

Payroll History

Payroll data, including pay runs, employee YTD totals, tax withholdings, and superannuation/pension contributions, does not transfer. This is one of the biggest surprises for firms that haven't done a QuickBooks Desktop to Xero migration before.

What to do: You have two options. First, you can manually enter YTD payroll figures into Xero's payroll module as opening balances. Second, you can keep the QBD file as a read-only archive for payroll history lookups and start fresh in Xero payroll from the migration date forward. Most firms choose the second option.

File Attachments

Receipts, PDF invoices, contracts, and other documents attached to transactions in QuickBooks Desktop don't come across. QBD stores these as embedded files or links within its proprietary database format, and there's no automated way to extract and reattach them in Xero.

What to do: If you need historical attachments, keep the QBD file accessible as a reference archive. Going forward, use Xero's Files inbox or a document management integration like Hubdoc.

Memorized Transactions (Recurring Templates)

QuickBooks Desktop's memorized transactions, including recurring invoices, bills, and journal entries, don't transfer. These are essentially saved templates within QBD, not actual transaction data.

What to do: Recreate your recurring templates in Xero manually. Pull a list from QBD (Reports > Memorized Transaction Listing) and rebuild each one in Xero's repeating transactions feature. Budget 10 to 15 minutes per template.

Audit Trail / Transaction History Log

QBD's audit trail, the log showing who changed what and when, is specific to QuickBooks and doesn't migrate. Xero maintains its own audit history from the moment you start using it.

What to do: Export the QBD audit trail to PDF before migration and store it with your archived QBD file. If you're in a regulated industry or expect a CRA or ATO audit covering the QBD period, this is non-negotiable.

Custom Reports and Saved Report Templates

Any custom report layouts, saved filters, or modified report templates you built in QuickBooks Desktop won't carry over. Xero has its own reporting engine with different customization options.

What to do: Screenshot or export your most-used custom reports from QBD. Rebuild the ones you need in Xero. Some firms find Xero's reporting more flexible for multi-entity consolidation but less customizable for individual report layouts, a tradeoff worth knowing about when comparing xero vs quickbooks.

GIFI Code Mapping (Canadian Firms)

For Canadian firms, GIFI (General Index of Financial Information) codes used for CRA T2 corporate tax filing are a known gap. QuickBooks Desktop maps GIFI codes to accounts natively. Xero's GIFI mapping is more limited.

Professional migration services are actively working on this. WOW BookSwitch has noted that GIFI code mapping is coming soon but is not yet live. In the meantime, you'll need to map GIFI codes manually in your tax preparation software or use a third-party integration.

How Professional Migration Services Handle the Gaps

The data that doesn't transfer is the same regardless of whether you use a free tool, a paid automated converter, or a full-service migration. The difference is in how the gaps are handled.

Free tools like Jet Convert and Dataswitcher convert the data they can and leave you to discover the gaps yourself. No documentation, no correcting entries, no human review.

A professional QuickBooks Desktop to Xero Migration Service like WOW BookSwitch takes a different approach. Every file goes through AI validation plus trained accountant review. The migration includes correcting entries to ensure balances tie correctly, and you get six months of free WOW Backup and Restore for the migrated Xero organization.

More critically, a professional service documents what didn't transfer and gives you a clear handoff checklist. You know exactly what needs manual setup in Xero (bank feeds, recurring templates, payroll opening balances) before your team starts working in the new system.

Planning Your Migration Around the Gaps

Knowing what doesn't transfer lets you build a realistic timeline. Here's a practical sequence.

Week 1: Run the migration (one to three business days with a professional service). Reconnect bank feeds. Import CSV statements for any gap period.

Week 2: Rebuild recurring transaction templates. Set up payroll opening balances if migrating payroll. Recreate custom reports.

Week 3: Run parallel systems. Enter transactions in both QBD and Xero for one pay period or billing cycle. Compare outputs.

Week 4: Cut over to Xero exclusively. Archive the QBD file with its audit trail export.

Firms with 30 or more client files on QuickBooks Desktop should plan for a phased migration rather than a big-bang approach. Migrating 10 files per week, with one week of parallel running per batch, keeps the workload manageable.

Conclusion

Not everything transfers when you migrate QuickBooks Desktop to Xero, and anyone who tells you otherwise is setting you up for trouble. Bank feeds, payroll history, attachments, and memorized transactions are the big four gaps. Plan for them, document them, and you'll have a clean migration.

Need a migration that accounts for every gap? Get a quote from WOW BookSwitch. Every file gets AI validation, accountant review, and correcting entries, plus a clear handoff checklist for the items that need manual setup.