Every migration to accounting software succeeds or fails on one date: the day you enter your opening balances. Get that date right, and switching software is invisible to your reports. Get it wrong — one account missed, one balance transposed — and the error doesn't stay in month one. It reappears in every balance sheet you print after it, until someone finds it.
Key takeaways
- Migration is really an opening-balance exercise, not a data-transfer exercise — the software you choose matters less than what you enter on day one.
- Pick a cutover date before you touch anything else; the start of a month or fiscal year keeps a single accounting period from being split across two systems.
- Rebuild the chart of accounts to match your business before entering a single balance — the wrong account structure corrupts every report built on top of it.
- A short parallel run, recording the same real transactions in both systems, is the cheapest insurance you can buy against a bad migration.
- Archive the old spreadsheets or software file — most jurisdictions require you to keep source records for years after you stop actively using them.
To migrate to accounting software: rebuild the chart of accounts to match your business, pick a cutover date, enter an accurate opening trial balance as of that date, bring across customer and vendor balances in detail, then run the old and new systems side by side for a few weeks before retiring the spreadsheet for good.
Why the opening balance is the whole migration
New software arrives with an empty ledger. Every account starts at zero, which is correct for a brand-new business and wrong for one that already has cash in the bank, stock on the shelf, and money owed both ways. The opening balance is what tells the new system: this is where you're picking up, not starting from.
If that opening balance is wrong — an account left out, a customer balance missed, a total transposed — the mistake doesn't correct itself next month. Your balance sheet won't balance from day one, and every report you generate afterward carries the same error forward, because each period's closing balance becomes the next period's opening balance.
Step 1: Rebuild your chart of accounts first
Before you enter a single dollar, make sure the accounts you're about to use actually match your business. Most software ships with a generic default chart of accounts — delete the ones you'll never use, add the ones you're missing, and rename anything that doesn't match how you actually talk about the business. Doing this after balances are already entered means re-mapping numbers you've already keyed in twice.
Step 2: Choose your cutover date
Pick a date before you do anything else, because it determines everything that follows. The start of a calendar month, or better still the start of your fiscal year, is almost always the simplest choice — it means a full accounting period sits cleanly on one side of the switch or the other, with nothing split down the middle.
Switching mid-year is possible, but it's more work: you'll need to divide that year's transactions and reports between the old system and the new one, and your year-end figures will need to be reassembled from both. If you can wait for a period boundary, wait.
Step 3: Enter accurate opening balances
This is the step that decides whether the migration is a success. You need, as of the cutover date: cash and bank balances, the total owed by each customer (not just one combined receivables figure), the total owed to each vendor, the value of inventory on hand, fixed assets at their current book value, and equity — including the owner's capital and any drawings taken so far.
Take a wholesale supply business switching over on 1 January as a worked example.
Bay Street Wholesale — opening position, 1 January
| Account | Amount |
|---|---|
| Cash | $4,200 |
| Bank | $18,600 |
| Accounts receivable | $9,400 |
| Inventory | $26,300 |
| Equipment | $12,000 |
| Total assets | $70,500 |
| Accounts payable | $14,800 |
| Loan payable | $20,000 |
| Total liabilities | $34,800 |
| Owner's capital (balancing figure) | $35,700 |
$70,500 assets = $34,800 liabilities + $35,700 equity. That balancing figure for capital only appears once every other line is entered correctly — if it doesn't match what the owner actually put into the business, something upstream is wrong.
Posted as a single entry in the new system, it looks like this:
| Account | Debit | Credit |
|---|---|---|
| Cash | 4,200 | |
| Bank | 18,600 | |
| Accounts receivable | 9,400 | |
| Inventory | 26,300 | |
| Equipment | 12,000 | |
| Accounts payable | 14,800 | |
| Loan payable | 20,000 | |
| Owner's capital | 35,700 |
Debits and credits both total $70,500. That's not a coincidence — it's the accounting equation doing exactly what it's supposed to do.
Step 4: Verify the trial balance before you record anything new
Once the opening entry is posted, pull a trial balance and check that total debits equal total credits — before you record a single new sale or bill in the new system. Reconcile the cash and bank figures against your actual bank statements, and check the receivables and payables totals against your aging reports from the old system, customer by customer and vendor by vendor. A trial balance that balances only proves the debits match the credits; it doesn't prove the individual figures are right.
Step 5: Run the old and new systems in parallel
For two to four weeks, record the same real transactions in both the old system and the new one, then compare the reports each produces. This is where account-mapping mistakes and setup errors surface — a sale posting to the wrong revenue account, tax calculating differently, a customer balance that doesn't quite match. It's far cheaper to catch these while both systems are still running than to discover them three months later when a report looks wrong and you can't tell why.
Only retire the old spreadsheet or software once the parallel period's numbers agree. Keep the file itself archived rather than deleting it — most jurisdictions require business records to be retained for a period of years, and you'll want it if a question ever comes up about a transaction from before the switch.
Reyuko's Chart of Accounts is already organized around the accounting equation — Assets, Liabilities, Equity, Revenue and Expenses — so Step 1 means editing that existing structure rather than building one from a blank page. To bring in the opening balances from Step 3, you record them as a normal entry in the General Journal, dated at your cutover, exactly like the worked example above. Once it's posted, run the Trial Balance report from Reporting — it's generated live from the ledger, so if debits and credits don't match, you see it immediately rather than after your first real month of new transactions has already been layered on top.
Reyuko doesn't currently import historical transactions in bulk from another system, so the parallel-run step still matters: enter the same transactions in both places for a few weeks before you retire the old one. The chart of accounts, general journal and trial balance report are all in the free edition.
Before you flip the switch
A migration is ready to go live when all of the following are true: the chart of accounts matches how the business actually operates, a cutover date is fixed, opening balances are entered and the trial balance is in balance, individual customer and vendor totals have been checked against the old system, and a parallel run has produced matching reports for at least a few weeks. If any of these is still uncertain, it's cheaper to wait than to fix it after the fact — see the migration readiness checklist and the most common migration mistakes before you set a date.
Reyuko