The QuickBooks Desktop shutdown is not a rumour, a warning, or a maybe. Intuit has confirmed the timeline. QBD 2022 support ended in May 2025. QBD 2023 support ends in May 2026. QBD 2024 — the final version — loses support by September 2027. After that: no security patches, no bank feed connections, no payroll processing, and software that slowly becomes incompatible with updated operating systems.
For accounting firms managing 50, 100, or 200 client files on QuickBooks Desktop, the question is no longer whether to migrate. It is whether your firm will do it on your schedule or Intuit's.
This article is a direct action plan. Here is what you need to do, in order, before the deadline compresses your options.
Step 1: Understand What the Deadline Actually Means for Your Firm
The support cutoff is not a cliff that drops overnight. It is a slow deterioration that accelerates as time passes.
After the end-of-support date, Intuit stops issuing security patches. That means any vulnerability discovered in QBD after the cutoff stays unpatched. For accounting firms handling client financial data, running unsupported software is a PIPEDA compliance exposure in Canada and a professional liability question in any jurisdiction.
Bank feeds break next. Intuit's bank feed infrastructure depends on active relationships with financial institutions that require ongoing maintenance. Once support ends, those connections are not renewed. Clients who rely on daily bank feed reconciliation in QBD will start seeing disconnections.
Payroll stops last but most visibly. Payroll tax tables require annual updates. Without support, those updates stop. Firms still running QBD payroll after the deadline will be working from outdated tax tables — which creates filing errors.
None of these failures happen simultaneously on the cutoff date. But they all happen, and firms that wait for a single dramatic failure will have been dealing with degradation for months before they act.
Step 2: Audit Your Client Portfolio Before Migrating Anything
Before submitting a single file for QuickBooks Desktop to Xero migration, spend a week building a conversion inventory. This is not optional if your portfolio has more than 20 files. Skipping it creates problems that are expensive to fix mid-migration.
For each client file, document:
Years of history to migrate. WOW BookSwitch's base $399 USD package covers the current fiscal year plus three prior years. Files requiring more history need to be flagged for extended history pricing at $100 USD per additional year. Not every client needs a full decade of history in Xero — figure out the minimum required before pricing the migration.
Multi-currency flag. Any client with foreign currency transactions needs a migration service with documented multi-currency support. The Xero Conversion Toolbox and most free tools fail on multi-currency files. This eliminates them as options for those clients regardless of cost.
File complexity. A straightforward single-currency file from a retail business with three years of clean history is very different from a manufacturing client with intercompany transactions, class tracking across seven departments, and seven years of data. The conversion timeline and review effort differ accordingly.
CRA retention obligations. For Canadian clients, the source QuickBooks Desktop file must be retained for a minimum of six years from the end of the last tax year it covers, under Section 230 of the Income Tax Act. The Excise Tax Act creates a parallel six-year obligation for GST/HST records. Migrating data to Xero does not satisfy this obligation. The QBD source file stays in archive regardless of how much history transfers.
This inventory becomes your migration plan. Without it, you are making decisions file by file under deadline pressure.
Step 3: Choose the Right Migration Approach for Your Portfolio
There are three options for a QuickBooks Desktop to Xero conversion, and they are not interchangeable.
Manual CSV migration via Xero's Conversion Toolbox. This is the lowest-cost option in licence fees and the highest-cost option in staff time. The manual process runs 12 to 17 hours per client file. For a firm with 80 clients, that is between 960 and 1,360 hours of work. At a fully loaded staff cost of $75 per hour, that is $72,000 to $102,000 in labour — not counting errors that need to be corrected after the fact. The Toolbox also cannot handle multi-currency files or complex chart-of-accounts structures cleanly.
Free third-party tools (Jet Convert). Jet Convert is Xero's official conversion partner and handles the majority of QBD-to-Xero conversions by volume. It works adequately on simple single-currency files. It fails predictably on multi-currency transactions and extended history. There is no AI validation or accountant review, so any errors in the output land with your firm to find and fix.
Professional QuickBooks Desktop to Xero migration service (WOW BookSwitch). WOW BookSwitch converts the chart of accounts, transaction history, customers, vendors, invoices, bills, journal entries, class tracking, and multi-currency transactions from QBD to Xero. AI post-conversion validation compares the trial balance, balance sheet, and profit and loss statement between the source and converted file. Trained accountants apply correcting entries where the validation flags discrepancies. The file is not delivered until it passes.
Pricing: $399 USD per conversion. Extended history is $100 USD per additional year. A 15% volume discount applies at 30 or more files. Turnaround is one to three business days. The 95% accuracy guarantee is backed by a full refund for verified conversion errors.
For a firm with 80 files at the volume discount rate, the total cost is approximately $27,132 USD — a fraction of the labour cost of manual migration, and with validation that manual migration typically skips.
Step 4: Know What Does and Does Not Transfer
This is where firms get caught if they have not done their homework before client go-live.
What transfers: Chart of accounts, transaction history, customer and vendor records, opening balances, invoices, bills, journal entries, class tracking, and multi-currency transactions.
What does not transfer: Bank feeds, reconciliations, memorized transactions, payroll history, and attachments. Every client will need to reconnect their bank feeds directly in Xero after migration. This is not data loss — it is a setup task. But clients who are not told in advance will call your office the day they go live wondering why their accounts are not reconciling.
GIFI code mapping (Canada): GIFI code mapping is a coming-soon feature for WOW BookSwitch. It is not part of the current conversion output. Canadian firms preparing T2 returns should plan for GIFI setup in Xero post-migration and not include it in client communications as a delivered item.
Step 5: Understand the Canadian Compliance Layer
If your firm is in Canada, the migration has a privacy and data residency dimension that does not exist in the same way for US firms.
PIPEDA — the federal Personal Information Protection and Electronic Documents Act — requires accounting firms to ensure that third-party processors handling client financial data provide comparable privacy protection. That means confirming where the migration vendor processes your files. A vague "secure cloud infrastructure" commitment does not satisfy this obligation.
WOW BookSwitch processes Canadian client data exclusively in AWS Canada regions. The data does not leave Canadian infrastructure during conversion. Firms in Alberta, British Columbia, or Quebec face parallel obligations under provincial privacy legislation — Alberta PIPA, BC PIPA, and Quebec's Law 25 — that apply substantively similar requirements.
Confirm data residency in writing before uploading any client file to a migration service. This is not bureaucratic caution. It is a client obligation.
The Timing Problem Most Firms Are Underestimating
The effective migration window is smaller than it looks. Tax season — January through April — is functionally unavailable for large-scale migration work at most Canadian and US accounting firms. Strip those four months out and the usable window is eight to nine months per year.
A firm with 150 client organisations, processing files at an average of five days each including client go-live confirmation, needs to start no later than mid-2026 to finish before the September 2027 QBD 2024 deadline with any buffer for delays.
Firms that wait for the urgency to feel real will start in Q1 2027.
By that point, professional migration services will be operating at capacity. Turnaround times will stretch. Client communication timelines will compress. Staff will be managing migration work during the same period they are managing year-end and tax filing.
The firms that are starting now — in 2026 — are the ones building a process, not a panic.
Frequently Asked Questions
1. What is the QuickBooks Desktop end-of-support timeline?
QBD 2022 support ended May 2025. QBD 2023 support ends May 2026. QBD 2024 — the last version — reaches end of support by September 2027. After that date, Intuit stops providing security patches, bank feed maintenance, and payroll tax table updates.
2. What happens if we keep using QuickBooks Desktop after the shutdown?
The software continues to function initially, but security vulnerabilities accumulate without patches, bank feed connections degrade and eventually break, and payroll tax tables become outdated. There is no single failure date — it is a gradual deterioration that accelerates over time.
3. Can I migrate from QuickBooks Desktop to Xero without losing historical data?
Yes. WOW BookSwitch's base package covers the current fiscal year plus three prior years. Additional years are available at $100 USD per year. Transaction history, chart of accounts, customers, vendors, invoices, bills, and journal entries all transfer. Bank feeds, reconciliations, and payroll history do not.
4. How long does a professional QuickBooks to Xero conversion take?
With WOW BookSwitch, one to three business days for most files. Simple single-currency files tend to complete toward the one-day end. Multi-currency files with extended history sit at the three-day end.
5. What does the WOW BookSwitch conversion cost?
$399 USD per conversion. Extended history beyond the base package is $100 USD per additional year. Firms submitting 30 or more files receive a 15% volume discount.
6. Is Xero better than QuickBooks Online as a migration destination?
For firms migrating from QuickBooks Desktop, Xero's cloud-native architecture is generally the stronger fit. Its bank reconciliation workflow is cleaner, its app ecosystem is broader, and it was purpose-built for multi-user cloud access. QuickBooks Online integrates more tightly with Intuit payroll, which matters for some practices.
7. What does PIPEDA require for Canadian accounting firms during a QBD migration?
PIPEDA requires that third-party processors handling client financial data provide comparable privacy protection. For migration services, this means confirming Canadian client data is processed in Canadian infrastructure. WOW BookSwitch processes Canadian data in AWS Canada regions.
8. Does migrating to Xero satisfy the CRA six-year retention requirement?
No. The CRA retention obligation under Section 230 of the Income Tax Act applies to the source QuickBooks Desktop file. The migration and the retention obligation are separate. Retain the QBD source file in a readable, accessible format regardless of how much history transfers to Xero.
9. Can I use Xero's free Conversion Toolbox for all my client files?
The Conversion Toolbox handles straightforward single-currency files. It is not designed for multi-currency transactions, extended history, or complex chart-of-accounts structures. For those files, a professional migration service is the practical option.
10. What is the volume discount for large accounting firm portfolios?
WOW BookSwitch applies a 15% volume discount at 30 or more files. For a portfolio of 100 files, that reduces the per-file cost from $399 to approximately $339 USD.
Your QBD clock is running. Visit: wowbookswitch.com to submit your intake form, access your migration dashboard, and start converting client files before the deadline forces your hand. AI validation included. Correcting entries applied. Canadian data stays in Canada.
Related Hashtags:
Top comments (0)