What to Do When a CRA Audit Covers Your QuickBooks to Xero Migration Period

You moved your client from QuickBooks Desktop to Xero. Six months later, the CRA sends an audit notice, and the review period spans the exact months when the migration happened. Two systems, two sets of records, potential gaps in the trail. This is the scenario that keeps managing partners up at night.

Here's the good news: a QuickBooks Desktop to Xero conversion doesn't create a compliance problem if you document it properly. The CRA doesn't care which software you use. They care that you can produce complete, accurate records for the period under review.

This article covers exactly what the CRA expects, what records you need, and how to prepare when the audit window overlaps your migration.

What the CRA Actually Requires

The CRA's audit requirements are platform-agnostic. Under the Income Tax Act (Section 230), every person carrying on a business in Canada must keep adequate books and records. "Adequate" means you can substantiate every transaction on your return.

The CRA does not require you to maintain a specific software platform. They require you to produce records that are complete, accurate, and organized. That can come from one system, two systems, or paper ledgers. The format doesn't matter. The completeness does.

The Migration Period Documentation Package

When a CRA audit covers your QuickBooks Desktop to Xero migration period, you need to produce a documentation package that covers three phases.

Phase 1: Pre-Migration (QBD Records)

Everything up to your data cutoff date lives in QuickBooks Desktop. You need to be able to produce the following from the QBD file.

• Trial balance as of the cutoff date
• Balance sheet as of the cutoff date
• Profit and loss for each fiscal year under review
• General ledger detail for any account the auditor requests
• GST/HST return working papers
• Bank reconciliation reports through the cutoff date
• Payroll records (T4 summaries, remittance confirmations)
• Audit trail export from QBD

Keep your QBD file accessible and backed up in at least two locations.

Phase 2: Migration Period (The Crossover)

This is the part most firms miss. The migration itself needs documentation. Here's what to keep.

Migration date record. A simple note stating: "Client file migrated from QuickBooks Desktop to Xero on \[date\]. Data cutoff date: \[date\]. Xero go-live date: \[date\]."

Conversion validation report. If you used a professional QuickBooks Desktop to Xero Migration Service, you should have received a validation report showing the trial balance comparison between QBD and Xero. If you used WOW BookSwitch, this is part of the standard deliverable, as every file gets AI validation plus trained accountant review with a 95% accuracy guarantee.

Correcting entries. Any journal entries posted to align balances between the two systems. Each entry should have a memo explaining the adjustment (e.g., "FX rounding adjustment, QBD to Xero migration, \[date\]").

Gap period transaction log. If transactions occurred between the data cutoff and Xero go-live, document each one. Show where it was originally entered (QBD) and where it now lives (Xero).

Phase 3: Post-Migration (Xero Records)

Everything from the go-live date forward lives in Xero. You need the same standard reports you'd produce from any system.

• Trial balance, balance sheet, and P\&L from Xero for the post-migration period
• Bank reconciliation reports
• GST/HST filing summaries
• General ledger detail as requested

GIFI Code Considerations

Canadian corporate tax returns require GIFI (General Index of Financial Information) codes mapped to each account. QuickBooks Desktop handles this natively. Xero's GIFI mapping is more limited.

If the CRA audit involves a T2 return, the auditor may ask how GIFI codes were maintained across the migration. Document your GIFI mapping, whether it's handled in your tax preparation software (Profile, TaxCycle, etc.) or through a manual mapping spreadsheet.

How the CRA Handles Split-System Periods

CRA auditors see system migrations regularly. They're not unusual or suspicious. What raises flags is incomplete records, not the fact that records span two platforms.

Here's what auditors typically do when they encounter a migration mid-period.

They request records from both systems. They'll ask for QBD reports for the pre-migration period and Xero reports for the post-migration period. Be ready to produce both.

They check for continuity. The closing balances in QBD should match the opening balances in Xero (within a documented tolerance for rounding adjustments). If they don't match, you need correcting entries with clear explanations.

They may request the raw QBD file. Under Section 231.1, the CRA can request electronic records, including the QBD file itself.

They'll scrutinize the gap period. Expect questions about any window where transactions could have been missed or duplicated. Your gap period transaction log is your defense.

PIPEDA and Data Retention

Be aware that your QBD file, Xero file, and all migration documentation contain personal financial information subject to PIPEDA. Ensure your data retention policy covers migrated and archived files, and know where the data is stored. WOW BookSwitch uses AWS Canada for Canadian clients.

Building Your Audit-Ready Migration File

Create a folder for each client migration containing: migration date memo (cutoff and go-live dates), QBD and Xero trial balances, trial balance comparison with correcting entries, gap period transaction log, correcting entry journals with memos, QBD audit trail export (PDF), QBD file backup location, GIFI mapping documentation, and the migration service's validation report. This takes 30 minutes per client and saves hours during an audit.

When Professional Migration Documentation Pays Off

DIY migrations and free tools like Jet Convert don't produce validation reports or correcting entry documentation. You're on your own to create the audit trail.

A professional QuickBooks Desktop to Xero Migration Service generates this documentation as part of the process. WOW BookSwitch's deliverable includes validation against the trial balance, balance sheet, and profit and loss. The correcting entries are documented and posted. If the CRA comes calling, you have a professional third-party validation of the conversion accuracy.

At $399 per file (with 15% off at 30 or more files), the migration cost is a small price for audit-ready documentation on every client file.

Conclusion

A CRA audit covering your QuickBooks to Xero migration period is manageable if you've documented the migration properly. Keep the QBD file, document the cutoff and go-live dates, maintain your correcting entries, and build a migration folder for each client. The CRA wants complete records. Give them complete records, and the fact that those records span two systems is a non-issue.

Need audit-ready migration documentation? Get a quote from WOW BookSwitch. Every file includes AI validation, accountant review, correcting entries, and documentation that holds up under scrutiny.