Switching accounting software without losing your history: what to migrate, what to archive, and when not to switch
Moving ledgers? Decide what comes across, what goes to a read-only archive for the retention period, how last year stays comparable, and when staying put is wiser.
Mark Holleman6 min read
Working on this yourself? Talk to Mark, our co-founder. We’re here to solve it with you.
On this page
Switching accounting software without losing history means moving the balances, open items and master data you work with every day, bringing across as much transaction history as you will actually use, archiving the rest in a readable form for the legal retention period, and checking that the opening position in the new ledger matches the old one on the cutover date. Before any of that, it means checking whether you need to switch at all.
Three questions decide whether a switch goes well. Will the opening balance tie out? Will last year's comparison still work? Can you still find an invoice from 2022 when the tax inspector asks? Answer them before you sign anything new, and plan around the retention rules, because they outlast any software contract.
This post is for finance leads, CFOs and accounting firms planning a move. It covers what to migrate, what to archive, how to check the cutover, how agents change the work, and the honest case for not switching.
Should you switch accounting software at all?
Start with the reason. Write down the three problems you want the switch to solve, and be specific.
Some problems really are the ledger. It cannot handle the number of entities or currencies you now run. Your accountant no longer supports it. It cannot produce the reports or VAT returns your country needs. The vendor is ending the product. In those cases a migration is the right call.
Many problems are not the ledger. Bank lines reconciled two weeks late. Supplier invoices waiting in an inbox. A close that takes ten days. Reports that are rebuilt in a spreadsheet every month. A new ledger will not fix these, because the cause is the manual work around the ledger, not the ledger itself. You can move all of that work to a new system and find yourself in the same place six months later, minus a quarter spent on migration.
If your problems are in the second group, consider adding automation on top of the ledger you have. Your accountant keeps working where they always have, your history stays exactly where it is, and nothing needs to be migrated. More on that at the end.
What should you migrate?
If you do switch, separate what the new system needs to run from what you merely want to keep.
Always migrate
- The chart of accounts, mapped account by account to the new structure. This is the moment to clean it up. In the Netherlands, mapping to the Referentie Grootboekschema (RGS) makes reporting and the conversation with your accountant easier later.
- Opening balances at the cutover date, as a trial balance that totals to zero.
- Open receivables and payables, invoice by invoice. Not just the balance. When a customer pays invoice 2026-0412 in the new system, there needs to be an invoice 2026-0412 to match it against.
- Customers and suppliers, with VAT numbers, IBANs, payment terms and contact details. Deduplicate before you move them, not after.
- The fixed asset register, with cost, accumulated depreciation and remaining life per asset, so depreciation continues correctly.
- Anything that runs on a schedule, such as prepaid costs being released, deferred revenue and recurring invoices.
Decide case by case
Transaction history is the real choice. There are roughly three options:
- Full history. Every journal line for the years you migrate. Best for drill-down and audits, slowest to do and to verify.
- Monthly balances per account for the comparison years, usually one or two. You can still compare each month with the same month last year, but to see the entries behind an old balance you open the archive.
- Opening balance only, with everything earlier archived. Fastest, and fine for a company whose reporting does not look back far.
For most growing companies, option 2 is the sensible middle. You keep comparability in the reports you actually use, and the old detail stays available in the archive.
What should you archive, and for how long?
Everything you do not migrate still has to be kept. Retention rules apply to your records whichever system they live in.
In the Netherlands, the Belastingdienst generally requires you to keep your records for seven years, and longer for some records, such as those relating to real estate. In the UK, a limited company must generally keep its accounting records for six years from the end of the financial year they relate to, and HMRC asks for at least six years for VAT records. If you sell to consumers in other EU countries through the One Stop Shop (OSS), those records must be kept for ten years. These are general rules with exceptions, so check what applies to you with your accountant before you switch anything off.
A practical archive contains:
- The general ledger and trial balances per year, exported to a format you can open without the old software
- VAT returns as filed, with their supporting reports
- Sales and purchase invoices with the source documents attached
- Bank statements
- The fixed asset register and any depreciation schedules
Also check whether the old vendor offers a cheap read-only licence. Being able to log in and look something up is often worth more than a perfect export.
How do you tie out the cutover?
With a tie-out at the cutover date, done before anyone posts a new transaction.
Here is an illustrative opening balance at 1 January, the same in both systems:
- Bank €126,410
- Accounts receivable €84,250
- Fixed assets, net €38,600
- Total assets €249,260
- Accounts payable €41,780
- VAT payable €18,940
- Accruals €12,500
- Equity €176,040
- Total liabilities and equity €249,260
Then check that the detail supports the balances. The open sales invoices in the new system must add up to €84,250, and the open purchase invoices to €41,780. The asset register must total €38,600. The bank balance must match the bank statement on 31 December. If any of these differ by a cent, find out why before you continue.
Choose the cutover date carefully. The start of a financial year is cleanest. If that is not possible, use the start of a VAT period, so that no single VAT return has to be built from two systems. Running both systems side by side for one month costs some effort and catches most of the mistakes.
How do agents change a migration?
People decide the things that shape the new books, such as how to restructure the chart of accounts, which history to keep and what the opening equity should be. Much of the rest is repetitive checking, and that is where agents help.
- Mapping. An agent can suggest where each old account belongs in the new chart, based on account names, how each account was actually used and how its balances move, and flag the accounts it is unsure about.
- Cleaning master data. It can find the three versions of the same supplier with slightly different names, and the customers without a VAT number, before they are copied into a clean system.
- Tying out. It can compare the old and new trial balances, every control account against its open items, and the asset register against the ledger, as often as needed during the project instead of once at the end.
- Running alongside. In the parallel month, it can book the same transactions in both systems and report every difference.
The tie-out then runs throughout the project, and the differences surface while the person who mapped the account still remembers why.
When should you not switch?
When the problem is the work, not the ledger.
Thred Layer runs finance agents on top of the accounting software you already use. Thred keeps a full copy of your ledger in sync, the agents reconcile, chase, prepare approvals and answer questions within the rules you set, and the finished entries flow back to your ledger through a two-way sync. Your accounting software stays the system of record for your accountant and your filings. There is nothing to migrate, and your history stays where it is.
For accounting firms this matters even more. Moving dozens of clients to one new ledger is rarely realistic. With one layer across all your clients' administrations, clients keep the software they know and your team reviews instead of keying in. See the accounting firms page.
And if you do decide that a new ledger is the answer, Thred's own ledger comes with white-glove onboarding. Our team moves your opening balances and history, connects your banks and systems, and runs alongside your current setup until you are confident.
Whichever way you go, book a demo and we will help you work out whether to switch or to build on what you have.
Frequently asked questions
Do I need to migrate all historical transactions to new accounting software?
Usually not. Many companies migrate monthly balances per account for one or two comparison years and archive the older detail. Full transaction history helps with drill-down and audits but takes longer to move and verify.
How long must a Dutch company keep its financial records?
The Belastingdienst generally requires seven years, with longer periods for some records such as those relating to real estate. The obligation applies whichever system the records are in, so archive what you do not migrate. Check the details with your accountant.
How long must a UK company keep accounting records?
A UK limited company generally keeps its accounting records for six years from the end of the financial year they relate to, and HMRC asks for at least six years for VAT records. Some situations require longer, so check with your accountant.
When is the best time to switch accounting software?
The start of a financial year is cleanest. Otherwise choose the start of a VAT period, so no single VAT return has to be prepared from two systems, and run both systems in parallel for a month.
Can I automate my bookkeeping without changing accounting software?
Yes. Agents can work on top of an existing ledger through a two-way sync, handling reconciliation, approvals and collections while the ledger stays the system of record for your accountant and filings. Nothing has to be migrated.
Sources
Read next
- Have you really outgrown your accounting software? A test to run before you migrate
- Getting messy exports into your books: how to clean CSVs from banks, webshops and payroll reliably
- Your finance data in Claude or ChatGPT through MCP: what it is and what to watch out for
Where Thred comes in
Finance agents running on top of your existing ledger. You set the rules, approve the work and handle the exceptions. No migration.



