How to switch cloud accounting providers without losing historic invoices, bank feeds or reconciliations

I recently helped a client move from one cloud accounting provider to another, and it reminded me how many small business owners worry about losing historic invoices, bank feeds or months of neat reconciliations. The good news is that a migration doesn’t have to be disruptive — with the right checklist, a few practical workarounds and realistic expectations you can move systems without losing critical data or your sanity.

Why people switch — and what usually goes wrong

Business owners switch accounting software for sensible reasons: better bank feed reliability, cheaper pricing, favourite integrations (e.g. payroll or point-of-sale), or simply a more usable interface for the person doing the bookkeeping. What trips people up is underestimating what "moving" really means. You can transfer invoices and opening balances, but not every platform keeps the same structure for reconciliations or attachments. I always tell clients to think in two streams: historical records (invoices, receipts, PDF attachments, VAT returns) and active workflows (bank feeds, rules, open invoices, VAT obligations).

Prepare before you touch anything

Don’t rush the export/import stage. Spend time mapping where data currently lives and where it needs to go.

List the specific data you must keep: sales invoices, purchase invoices/credit notes, supplier/customer contact details, chart of accounts, VAT history, payroll journals (if relevant), and attachments.

Check integration points: bank feeds, payment gateways (Stripe/GoCardless/PayPal), POS systems, payroll and time-tracking apps.

Take screenshots of important setups: bank rules, invoice templates, VAT settings, closing balances at the migration date.

Exporting your historic invoices and attachments

Most cloud accounting platforms (Xero, QuickBooks Online, Sage Business Cloud) let you export invoices and transaction histories as CSVs. Attachments often need a separate export or have to be manually downloaded. I recommend exporting both the CSV data and the original PDFs/images.

Export invoices and credit notes in CSV with meaningful fields: invoice number, date, due date, customer, net, VAT, gross, status, and reference.

Export attachments in a folder structure where filenames include the invoice number — this makes re-linking far easier.

Run a VAT report covering historic periods you may need for audits. Keep PDF copies of VAT returns submitted to HMRC.

Transferring bank feeds without losing reconciliations

Bank feeds are often the sticking point. You can reconnect a bank feed to a new provider, but you will rarely bring across the bank feed history or reconciliation flags. That’s not necessarily a problem if you keep a copy of reconciled statements and reconciliations up to the migration date.

Decide a cut-off date for the migration — usually month-end or quarter-end works best.

Download bank statements (CSV or OFX) from your bank from the start of the year (or further back if you need). Keep the statement ending on the last reconciliation date as your opening point in the new system.

Keep reconciled transactions in the old system as readonly. Some clients archive the old subscription until they’re comfortable the new system works.

Keeping reconciliations meaningful

You can’t usually migrate reconciliation "matches" one-for-one, because the new software will try to re-match bank lines to invoices or spend. My approach is pragmatic:

Ensure the new chart of accounts and customer/supplier references match the exported invoice CSVs — consistent references make automatic matching far smoother.

Import historic invoices into the new system with the original invoice dates and numbers. If the new system lets you mark them as reconciled, only do this for opening balances — otherwise allow the bank feed to rematch.

For periods you want preserved exactly (for audit), export a reconciliation report from the old system and keep it as a PDF with your archives.

Import tips and common pitfalls

Importing is rarely a single-click job. Expect to clean CSVs and tweak fields.

Column headers must match the new system’s template. Common problems are date formats (DD/MM/YYYY vs YYYY-MM-DD), tax rate names and account codes.

Split large imports into chunks. If something goes wrong, a smaller batch is easier to fix.

Keep original invoice numbers. Renumbering causes headaches for audit trails and supplier/customer queries.

What to do about ongoing bank feeds and real-time bookkeeping

Plan a short freeze period during the switch. I usually advise clients to stop daily reconciliations and invoice creation for 24–72 hours around migration day. Use that time to:

Finish processing payments and issue invoices dated before the cut-off.

Reconnect bank feed(s) to the new provider and let transactions flow in. Expect to manually match at first while rules rebuild.

Recreate bank rules in the new system — many suppliers (e.g. direct debits) will come through with consistent descriptions that make rule recreation straightforward.

Practical checklist to follow on migration day

Here’s a checklist I use when leading a migration. Copy it, adapt it to your business size:

Choose a migration cut-off (date & time).

Export final reports from old system: trial balance, VAT returns, bank reconciliations, aged receivables/payables.

Export CSVs for invoices, expenses and a copy of attachments.

Download bank statements covering the migration date.

Import chart of accounts, opening balances and historic invoices into new system.

Reconnect bank feeds and import bank statements if required.

Rebuild key bank rules and automated payments.

Run reconciliation on the cut-off bank statement, check opening balance matches.

Keep the old subscription active for at least one accounting period post-migration.

When you should call in help

If your business has complex VAT history, bridging contracts, payroll journals or multi-currency transactions, get a bookkeeper or accountant involved. I’ve taken over several migrations where incorrect opening balances or misapplied VAT from a DIY import created weeks of extra work. A short session with someone experienced will save time and reduce risk.

File formats and compatibility table

Data	Common Export Format	Notes
Invoices / Credit notes	CSV / PDF	Keep invoice numbers and attach PDFs where possible
Bank Statements	CSV / OFX / QIF	OFX/QIF often preserve richer data for imports
Attachments	ZIP / Folder of PDFs/JPGs	Name files with invoice numbers for easy re-linking
Chart of Accounts	CSV	Match account codes to the new system before import

Switching cloud accounting providers can feel like a leap, but with structure and a realistic migration plan you can preserve historic invoices, bring in bank feeds and keep reconciliation integrity. If you’d like, I can share a migration template (CSV headers and a step-by-step checklist) tailored to the specific platforms you’re moving between — tell me which provider you’re leaving and which you’re joining (for example Xero to QuickBooks or Sage to Xero) and I’ll tailor the checklist to that route.