Sage 50 migration in Ireland: a playbook for practices

Desktop accounts tie the books to one machine and one set of files. The practice works from copies, questions go back and forth by email, and nobody sees the figures until the client sends them. Cloud software gives the practice and the client the same live ledger, which turns year-end catch-up into periodic review.

E-invoicing adds a deadline of sorts. From November 2028 every Irish business must be able to receive structured e-invoices, and practices will want clients on systems with a clear plan for that.

Not every client should move at once, and some should not move yet.

• Move first: sole traders, small companies and holding companies with simple books and no payroll in Sage.
• Move next: clients with straightforward VAT and a few hundred transactions a month.
• Plan carefully: clients with heavy stock, job costing or multi-company structures.
• Leave for now: clients whose Sage setup is deeply customised or tied to other systems.

Move a client at the start of a VAT period, so that one return is never split across two systems. The start of the financial year is better still, because the new system then holds the whole year. Two-month VAT periods begin in January, March, May, July, September and November, so there are six natural switch points a year.

A common rule is to bring opening balances at the switch date plus open debtor and creditor items, and to leave detailed transaction history in a read-only archive of the old company file. That archive has to stay readable for as long as Revenue’s record-keeping rules require, either in Sage itself or as exported reports saved to the client folder.

Most clients need opening balances, open sales invoices and open purchase bills, not years of transaction detail. Export a trial balance and aged debtor and creditor reports from Sage 50 at the switch date, and bring those across. Keep the Sage data accessible, either installed read-only or exported, for the six years Revenue expects records to be kept.

Bringing full history sounds safer but usually imports old errors and slows the project.

For the first VAT period after the switch, prepare the return in the new system and compare it with what Sage would have produced if you can. Differences usually point to a VAT code mapped wrongly or an opening balance entered in the wrong account. Fix them in month one and the rest of the year runs cleanly.

The software change matters less than the habit change. Show the client how to capture receipts on a phone, how to review the transactions the system has coded, and what the practice will check each period. A one-page routine left with the client does more than a long training session.

Migration takes time, so price it as a project or absorb it against future savings. The return comes from faster VAT reviews, fewer year-end questions and less re-keying. Track hours per client before and after for the first batch, so the business case for the rest is based on your own numbers.

HelloBooks imports opening balances, contacts and open items through CSV templates, and accountants manage client workspaces from their own login at no extra cost. Its AI codes transactions with Irish VAT treatment and computes VAT3 figures for review and entry in ROS. Irish payroll is not included, so clients with Sage payroll keep a payroll product; payroll journal import is coming soon.