An accounting software migration checklist isn't a formality before the "real" work of switching — the items on it, done properly, are the real work. Software takes an afternoon to install. Getting your business's numbers ready for it, correctly, is what actually determines whether the switch to accounting software goes smoothly.
Key takeaways
- Work through readiness in order: back up, clean up, map accounts, pick a cutoff date, enter opening balances, verify, run parallel, train, then archive the old system.
- The single highest-leverage step is verifying that your new opening trial balance has total debits equal to total credits before any new transaction is entered.
- A cutover date at the start of a fiscal period or month avoids splitting one period's transactions across two systems.
- A parallel-run period — both systems live at once, for real transactions — is the cheapest way to catch a setup mistake before it's permanent.
- Nothing on this list needs to happen in a single day. Spread it across the weeks before your chosen cutover date.
Step 1 — Back up your existing data
Before touching anything, export and securely store a complete copy of your old system's data and reports: full transaction history, customer and vendor lists, and any year-end reports you've already filed. You may need to reference this detail for several years after migrating, even once the old system is no longer your day-to-day source of truth, and in many places business records must be kept for a set number of years regardless of which system produced them.
Step 2 — Clean up your data
Migrating messy data into a new system just gives you a cleaner-looking version of the same mess. Before you export anything:
- Remove or merge duplicate customer and vendor records.
- Close out, write off, or otherwise resolve very old unpaid invoices that are never going to be collected.
- Reconcile all bank accounts fully, up to the point where your cutover will happen.
- Fix any known errors in the old system rather than carrying them forward — a wrongly categorized expense doesn't become correct by moving to new software.
Step 3 — Document your current chart of accounts
Write down every account you actually use today — not the textbook list, the real one. If you've never formally built one, how to build a chart of accounts covers the structure to use. This documented list becomes the source for the mapping step next, and it's also the moment most businesses notice accounts that have gone stale (a supplier that closed years ago, a category nobody's posted to since last year) and can simply be retired rather than carried across.
Step 4 — Map old accounts to new ones
Your new software will likely ship with its own default account structure. Go through your documented list from Step 3 and decide, account by account, where each one lands in the new chart of accounts — and do the same for tax codes if your business collects or remits tax. This mapping table is worth a second set of eyes, ideally your accountant's, before you rely on it: see common migration mistakes for what goes wrong when a mapping error slips through unreviewed.
Step 5 — Pick a cutover date
The start of a new fiscal year or, failing that, the start of any calendar month, is the simplest cutover point — it means entering exactly one clean opening balance rather than splitting a period's transactions across two systems. A cutover in the middle of a reporting period is still possible, but it adds real complexity: transactions before the date need to reconcile against the old system's figures, and transactions after need to reconcile against the new one.
Step 6 — Enter opening balances
With a mapping table and a cutover date settled, enter the actual opening balances into the new system: cash and bank, receivables, payables, inventory value, fixed assets, and equity (including any prior owner's drawings). Every figure should come directly from the old system's closing trial balance as of the cutover date — not a rounded or re-estimated version of it.
| Account | Debit | Credit |
|---|---|---|
| Cash | 18,000 | |
| Opening balance equity | 18,000 |
Most software posts opening balances against a temporary "opening balance equity" account, which nets to zero once every asset, liability, and equity balance has been entered. If it doesn't net to zero, something on the list is still missing or mistyped.
Step 7 — Verify the trial balance
This is the single most important checkpoint on the entire list. Before recording one new transaction, pull a trial balance from the new system and confirm two things: total debits equal total credits, and every individual account balance matches the old system's closing figure for that account (see the accounting software glossary if "trial balance" isn't a familiar term yet). If either check fails, stop and find the discrepancy now — it is dramatically cheaper to fix before go-live than after weeks of new transactions have posted on top of it.
Step 8 — Run a parallel period
For a defined stretch — commonly one month — record real transactions in both the old and new system, then compare the results. This is where mapping errors, missed accounts, and tax-code mismatches actually surface, because you have two independent sets of numbers to compare instead of trusting one blindly. Only stop maintaining the old system once a full period's comparison has come back clean.
Step 9 — Train the team
A short parallel-run period is also a natural training window: staff enter transactions in both systems and get comfortable with the new one while the old one is still the safety net. Pair this with a quick-reference guide covering the handful of tasks done daily (recording a sale, entering a bill, taking a payment), and designate one person as the internal point of contact for everyday questions once the new system is the only one running.
Step 10 — Archive the old system
Once the parallel comparison is clean and the team is comfortable, retire the old system as your live source of truth — but keep it, and its backups, safely archived rather than deleted. It remains your audit trail for everything before the cutover date.
| Step | What "done" looks like |
|---|---|
| 1. Back up | Full export of old data and reports saved securely |
| 2. Clean up | Duplicates merged, stale invoices resolved, bank reconciled |
| 3. Document current accounts | Real, currently-used chart of accounts written down |
| 4. Map accounts | Every old account assigned to a specific new one, reviewed |
| 5. Pick cutover date | A single agreed date, ideally start of month or fiscal year |
| 6. Enter opening balances | Every account matches the old system's cutover-date balance |
| 7. Verify trial balance | Debits = credits, confirmed before any new transaction |
| 8. Run parallel period | Both systems live, results compared, discrepancies resolved |
| 9. Train the team | Staff comfortable, quick-reference guide in hand |
| 10. Archive old system | Retired from daily use, kept safely for historical reference |
Two steps on this list have a direct equivalent inside Reyuko. Step 4 (account mapping) is easier to reason about against Reyuko's fixed four-level Chart of Accounts structure — five top-level categories (Assets, Liabilities, Equity, Revenue, Expenses) that every account, old or new, has to sit under. Step 7 (verifying the trial balance) is a live report in Reyuko's Reporting section: Trial Balance shows every account's debit or credit balance with a total-debit and total-credit figure and a balanced indicator, computed directly from the ledger — exactly the check this step asks for.
Reyuko's onboarding also includes a country and currency setup step and a choice of nine industry-specific business templates with prefilled example data (retail, wholesale, services, F&B, manufacturing and others), which can shorten Step 3 by giving you a realistic starting chart of accounts to compare your own against, rather than starting from a completely blank list.
Use this before you talk to any provider
Work through this list — even roughly — before you request a demo or a quote. A provider who can answer specifically how each of these ten steps works inside their product is a much stronger signal than a features list, and it puts you in a position to spot the migration mistakes this checklist exists to prevent, before they happen instead of after.
Reyuko