Switching Accounting Software on 1 January: The Singapore SME Cutover That Keeps Its History

You can switch accounting or HR software on 1 January without losing your history, but only if you stop trying to move the history at all. Migrate opening balances and master data into the new system, export everything older to CSV and PDF while you still have a working login on the old one, and keep that archive for at least five years because IRAS can ask for it long after the vendor relationship has ended. Switching accounting software on 1 January as a Singapore SME fails for one reason far more than any other: the subscription lapsed before anyone pulled the records out.

Why does 1 January work better than any other switch date?

Two clocks reset on the same day for most small Singapore companies. The financial year ends 31 December, so the closing trial balance becomes the opening balance in the new system with no part-year splice. The payroll year also ends, which matters more than owners expect: your IR8A for 2026 income comes entirely out of the old system and is submitted by 1 March 2027, while 2027 earnings accumulate cleanly in the new one. Switch in June and someone has to add two part-year records together by hand, reconcile the CPF submissions against both, and then defend the total.

If your financial year ends on another date, use that date instead. The alignment is what makes the cutover cheap, not the calendar.

What actually has to move, and what can stay behind?

Only two kinds of data belong in the new system. The first is master data: your chart of accounts, customers and suppliers with contact details and verified bank details, inventory items with costs, the fixed asset register including accumulated depreciation, and the employee master with join dates, salary, CPF status and leave balances. The second is anything still open on 31 December: unpaid sales invoices and unpaid supplier bills, entered line by line with their original invoice dates so the ageing is honest from day one.

Everything else stays behind as an export. Closed transactions from 2023, old journal entries, paid invoices, superseded quotations. Pulling five years of closed documents into a new system is the single largest cost item in most migration quotes, and it buys you a searchable copy of something you are already required to keep elsewhere.

Treat the cutover as a chance to trim. Most SME charts of accounts carry dead codes from a bookkeeper who left in 2019. Migrate the accounts you posted to in the last two years and archive the rest.

Which numbers must match on day one?

Before you post a single January transaction, these seven figures should agree between the old system, the new one and an independent source:

• Bank balance per the new system against the 31 December bank statement, not against the old system.
• Total accounts receivable against the AR ageing report, with the same oldest-invoice date.
• Total accounts payable against the AP listing.
• Inventory value against your physical count sheets, not the old system's perpetual figure.
• GST payable or refundable for the quarter that straddles the change.
• Fixed assets at cost and net book value.
• Leave balance per employee, including whatever carries forward under your own policy.

Print the comparison, sign it, and file it. In eighteen months, when a figure looks wrong, this one page is the difference between a question and an investigation.

What will IRAS still expect you to produce in 2031?

Business records supporting your tax returns must be kept for at least five years from the relevant year of assessment, in a form that can actually be produced on request. CPF contribution records carry a five year requirement too. Under the Employment Act, employee records are kept for two years for current staff and one year after an employee leaves.

None of that obligation transfers to your new software vendor. If the old system is cloud-based and you cancel the subscription, your access usually ends within weeks and the data is deleted on the provider's schedule, not yours. So before you cancel, export the general ledger, trial balance, AR and AP ageing, GST returns and working papers, payroll registers, and the IR8A submissions, as both CSV and PDF. Save them twice, in two different places, and open one file from each backup to prove the export is readable rather than a zero-byte placeholder.

How do you keep the old system available without paying full price?

Ask the outgoing vendor two specific questions: is there a read-only or archive tier, and how long after cancellation can the account be reactivated. Many providers offer a low-cost dormant plan precisely for this. If none exists, a single paid month in March, after you have filed the 2026 accounts and the IR8A, is usually enough to answer anything the auditor raises, and is far cheaper than keeping a full licence running all year on the assumption that you might need it.

What does the timeline look like from here?

1. Late October: choose the new system and confirm the export formats the old one can actually produce. Formats decide feasibility, not features.
2. November: set up the new system in parallel. Load the chart of accounts, master data and employees. Do not post live transactions yet.
3. Early December: run one full payroll cycle in the new HR system alongside the real one and compare every line, including CPF and any SDL. This is the test that catches the costly errors.
4. Mid December: run the exports. Everything, twice, verified.
5. 31 December: stocktake and bank balance captured on the day.
6. First week of January: post opening balances, reconcile the seven numbers, then start live use.
7. Mid January: keep both systems readable while the first month of real transactions settles.

What goes wrong most often?

Four failures account for almost all of the damage. The subscription is cancelled before the export is verified. Open invoices are loaded with a January date, so the AR ageing shows nothing overdue and collection stalls for a month. Supplier bank details are re-keyed from an email rather than copied from the verified master, which is exactly how payment fraud enters. And the person who understands the old system's quirks leaves in December, taking the only explanation of a strange suspense account balance with them.

All four are scheduling problems, not software problems. Which is why the decision worth making this month is not which system to buy. It is who owns the cutover, and whether they will be in the country in the first week of January.

Frequently asked questions

Can I switch accounting software mid-year if I cannot wait until January?

Yes, but budget for extra work. You will need a closing trial balance as at the switch date, and the year's statutory reporting will be assembled from two systems. The payroll side is the expensive part, because one IR8A per employee must combine earnings and CPF from both. If you must move mid-year, align the switch with the start of a GST quarter and a calendar month at minimum.

Should I pay the vendor to migrate historical transactions?

Usually no. Verified CSV and PDF exports satisfy the five year record-keeping requirement, and the staff who need old figures normally want a specific invoice or a comparative total, both of which an export answers. Pay for historical migration only if you genuinely run reports across multiple years inside the system, for example multi-year job costing on long projects.

What is the one thing I should do this week?

Log in to the system you intend to leave and try to export your general ledger for the current year. If the export is incomplete, locked behind a higher plan, or produces a format nothing can read, you have just found the real constraint on your timeline, with ten weeks left to work around it.