Introduction
Nobody plans to lose accounting data. They just don't plan to protect it either.
When accounting firms migrate from QuickBooks to Xero, the attention goes where it always goes: conversion accuracy, chart of accounts mapping, multi-currency handling, and go-live dates. Backup is the afterthought — something to sort out later, once the client is live and the migration project is technically closed.
Later is usually too late.
A Xero organization with no backup is exposed from the first transaction. User errors, ransomware attacks on connected systems, accidental bulk deletions — none of these are hypothetical risks. They're documented events that happen to accounting firms managing dozens of client Xero files. When one of them happens, the question isn't "how do we prevent this?" It's "what do we have to recover from?"
If the answer is nothing, the conversation that follows with the client is not a good one.
This article is about why backup has to be part of the migration plan — not an add-on after go-live — and what a complete backup strategy looks like across the full transition from QuickBooks Desktop to Xero.
The Three Times Backup Actually Matters
Most firms think about backup as post-migration protection. That's one of three windows where data is vulnerable. Missing either of the other two has its own set of consequences.
Before Conversion: The Source File Is Your Safety Net
The QuickBooks Desktop source file is the only record of the client's financial history before migration. It lives on a workstation or server that will eventually be shut down, cleared, or handed back to an IT team. Once that happens — and it happens faster than firms expect — the data is gone unless someone archived it first.
This matters for reasons that have nothing to do with the migration itself. CRA audits can cover any period within the six-year retention window. A client dispute about a 2022 invoice requires pulling the original QuickBooks Desktop records. An error discovered in the converted Xero file may need to be traced back to the source.
The source file backup is simple. It takes 20 minutes. But it only exists if someone actually does it before the migration starts.
During Conversion: The Gap Period
Between the moment a QuickBooks Desktop file is uploaded for conversion and the moment the client goes live in Xero, there's a period where transactions are happening in QuickBooks Desktop but won't appear in the converted output. Invoices, payments, payroll runs — any transaction recorded after the upload date needs to be manually posted in Xero after delivery.
Firms that don't track this gap period go live with incomplete books. The accounts receivable aging doesn't match reality. The cash position in Xero doesn't reflect what actually happened. This is recoverable — but it requires someone to catch it, which requires someone to be looking for it.
Documenting the gap period — upload date, go-live date, every transaction in between — is the protection. It's a 10-minute task per client that prevents a multi-week reconciliation project.
After Go-Live: The Live File Needs Its Own Protection
Once the client is working in Xero, that Xero organization is the live financial record for the business. It's also, by default, only as protected as Xero's own platform infrastructure provides.
Xero has solid platform-level security. But platform security is not the same as backup. If a user deletes a batch of transactions, or makes a series of incorrect journal entries, or a connected app pushes corrupted data into the file, Xero's infrastructure redundancy doesn't reverse those changes. You need a point-in-time restore capability to get back to a state that was correct.
Without that, the only option is manual reconstruction — which is what it sounds like: expensive, time-consuming, and imprecise.
What Built-In Backup Changes
WOW BookSwitch includes six months of free backup through WOW Backup and Restore with every QuickBooks Desktop to Xero conversion. The backup covers the converted Xero organization with automated daily snapshots and point-in-time restore capability.
This isn't a default Xero feature. It's separate infrastructure that sits outside the Xero platform, which means it's not affected by platform-level issues, accidental data changes made through the Xero interface, or user permission problems that might otherwise let someone with too much access modify records they shouldn't.
The practical difference: when something goes wrong with a client's Xero file — and eventually, something will — the firm with backup can restore to the previous day's state in a matter of hours. The firm without backup is starting from whatever the Xero file currently shows and working backward from bank statements and source documents.
Why Activation Timing Matters
The six months of free backup only protects data that exists at the moment of activation going forward. A backup activated on day 30 of Xero use doesn't protect the first 30 days of transactions. Those are gone if something happens before activation.
This is why activation before the client's first transaction in Xero isn't a recommendation — it's the minimum. The moment the converted file is delivered and reviewed, the backup subscription should be running before the client enters a single new record.
Most firms miss this. They activate backup eventually — at month two or three, when someone circles back to the task. By then, two or three months of live bookkeeping is unprotected. That's the window where recovery becomes reconstruction.
The Source File Archive Stays Separate
Six months of Xero backup does not replace the obligation to archive the QuickBooks Desktop source file.
These are two different things solving two different problems. The Xero backup protects the live Xero organization going forward. The QBD source file archive preserves the historical record for the periods that existed before migration — the data a CRA auditor would ask for if they selected a year that predates the Xero go-live date.
Under Canada's Income Tax Act, books and records must be retained for a minimum of six years from the end of the tax year they relate to. A client who migrates in 2026 needs their pre-migration records accessible until at least 2032. The Xero backup doesn't cover that. The QBD archive does.
Both need to exist. They're not interchangeable.
What Recovery Actually Looks Like
Two accounting firms in British Columbia, each managing a 50-client migration. Both use WOW BookSwitch. Both receive validated Xero files within one to three business days of upload.
Firm A activates the six-month free backup subscription immediately for each client, before the first transaction. They also retain the QBD source files in a documented archive. Four months after migration, one client's Xero file is hit by a connected app pushing duplicate transactions across 90 invoices. Firm A restores the file to the state from two days before the issue started. The duplicate transactions are gone. The client loses one afternoon of work entering the last two days of legitimate transactions again. Total disruption: four hours.
Firm B activates backup for most clients but misses eight files — they plan to do it during a slower week that never comes. One of those eight files develops the same problem. The only path forward is finding every duplicate transaction manually, reversing each one, and confirming the accounts receivable aging matches the original. Two staff members spend three weeks on it.
Same migration service. Same conversion quality. Different backup discipline. Completely different outcome.
Building a Complete Protection Strategy
The QBD to Xero migration isn't done when the converted file is delivered. It's done when the protection infrastructure is in place. Here's what that looks like:
Before upload: Back up the QuickBooks Desktop source file to a location separate from the production workstation. Open the backup and verify it contains current data. This takes 20 minutes and is the only version of that data you'll have once the workstation is cleared.
At upload: Record the exact date and time. Any transactions the client records in QuickBooks Desktop after this point are your gap period. Assign someone to capture and post them in Xero after delivery.
At delivery: Run the post-delivery review — spot-check the trial balance, confirm opening balances, verify accounts receivable aging. Then activate the WOW Backup and Restore subscription before the client enters anything new.
Ongoing: Confirm the backup ran successfully at least once before the client begins active use. Set a calendar reminder to renew the subscription before the six free months expire.
Archive: Document the QBD source file location in the client file, with the retention end date calculated from the most recent tax year in the file. Don't decommission the workstation or clear the backup drive without confirming the archive is complete.
That's the full strategy. It adds roughly two hours per client to the total migration project. Against the alternative — a reconstruction project that takes two staff members three weeks — it's not a difficult calculation.
Frequently Asked Questions
1. Does WOW BookSwitch include backup as part of the conversion service?
Yes. Every WOW BookSwitch conversion includes six months of free backup through WOW Backup and Restore. Activate it before the client's first Xero transaction, not after.
2. Does Xero back up your data automatically?
Xero has platform-level infrastructure redundancy, which protects against server failures. It doesn't provide point-in-time restore for individual organizations. If a user deletes records or a connected app corrupts data, Xero's redundancy doesn't reverse those changes. That's what the dedicated backup subscription is for.
3. Does the Xero backup also cover the QuickBooks Desktop source file?
No. The WOW Backup and Restore subscription covers the converted Xero organization. The QuickBooks Desktop source file is a separate archive that the firm needs to maintain independently. Both are required — they protect different things.
4. When exactly should I activate the backup subscription?
Before the client's first transaction in Xero. Not after the first week. Not when someone remembers. Before day one. The backup protects data from the moment of activation forward. Anything that happens before activation is not protected.
5. What does the six-month free backup actually include?
Automated daily backups of the converted Xero organization and point-in-time restore capability. After six months, the subscription renews on standard WOW Backup and Restore terms. Plan to continue it rather than letting coverage lapse.
6. How long should I keep the QuickBooks Desktop source file after migrating to Xero?
Under Canada's Income Tax Act, books and records must be retained for a minimum of six years from the end of the tax year they relate to. That clock doesn't reset at migration. A client who migrated in 2026 with records going back to 2020 needs those records accessible until at least 2026 — and likely 2031 for the earliest years covered.
7. What happens if a client's Xero file is corrupted or has data deleted after go-live?
With an active WOW Backup and Restore subscription, you can restore the Xero organization to any previous backup state. Without backup, the recovery path is manual reconstruction from bank statements, source documents, and whatever the current file shows — a project measured in weeks, not hours.
8. Is the backup important if my clients only have simple, single-currency files?
Yes. Data loss risk doesn't scale with file complexity. Simple files are just as vulnerable to user error, bulk deletions, and connected app problems as complex ones. Multi-currency files are harder to reconstruct if lost, but that doesn't make single-currency files safe to leave unprotected.
9. Can I recover a Xero organization to a date before a user made a mistake?
With an active WOW Backup and Restore subscription, point-in-time restore allows you to bring the organization back to any previous backup state. The most recent backup would typically be from the previous day.
10. Does backing up the Xero file also capture historical QuickBooks Desktop data that was converted?
The backup captures the Xero organization as it exists at the time of each backup, which includes the converted historical data from QuickBooks Desktop. The source QBD file itself is not stored in the Xero backup — that needs to be archived separately.
Conclusion: Get the Backup Done Before the Client Does Anything
Backup conversations have a way of happening after the fact. After the data loss. After the reconstruction project. After the client relationship takes the hit.
The backup strategy for a QuickBooks Desktop to Xero migration is not complicated. Archive the source file before upload. Document the gap period. Activate the Xero backup before day one. Keep the QBD archive for six years. None of these steps take more than an hour each.
The firms that get this right don't have recovery stories to tell because they never needed to recover. That's the goal.
Migrate from QuickBooks to Xero with WOW BookSwitch at wowbookswitch.com. Every conversion includes six months of free backup through WOW Backup and Restore. $399 USD per conversion, AI validation included. 95% accuracy guaranteed or your money back.
Related Hashtags:
Top comments (0)