How to Migrate Your Client Book from Sage to AccountsOS (2026 Guide for UK Practices)

Moving an entire client book to new software is the kind of job most practices put off for years. The data is scattered across versions, some clients are on desktop and some on cloud, and nobody wants to be the one who breaks a trial balance. This guide walks through exactly how a UK practice migrates from Sage to AccountsOS, what data comes across, how the AI-native import works, and what it costs once you are running every client from one dashboard.

Why are practices moving their client book off Sage?

Sage is the incumbent for a reason. Many practices have used it for decades, and "we already have it" is a powerful argument for staying put. But the reasons firms are now looking for a Sage alternative are consistent.

The first is heritage. Sage 50 is a desktop product at its core. It was built for a world where the books lived on one machine in the office, with backups, updates, and version mismatches to manage. Sage Business Cloud Accounting is the cloud product, but practices running a mixed book often end up supporting both, which means two ways of working and two sets of habits across the team.

The second is the licensing model. Per-seat and per-client licensing means your software cost climbs as your team and your client list grow. That works against you precisely when you are trying to scale.

The third is the shift to AI-native software. Sage's automation is largely rule-engine based. You set up rules, the engine applies them, and you maintain the rules. AccountsOS is built the other way round: an AI accountant, Finn, reads the data in context and proposes the treatment, so categorisation, reconciliation, and month-end happen continuously in the background rather than being a list of rules you have to keep current.

The fourth is Making Tax Digital. MTD keeps expanding, and practices want software that is already HMRC-recognised for MTD VAT and built for what is coming next. MTD for Income Tax begins in April 2026, so the direction of travel is clear.

None of this is a criticism of running a good practice on Sage. It is simply that the software was designed for a different era, and the economics and the workflow both improve when the underlying tool is cloud-first and AI-native.

What does migrating a whole client book actually involve?

Migrating one company is straightforward. Migrating a book of 30, 80, or 200 clients is a different exercise, because the work is repetitive and the risk is cumulative. Get one client's opening balances wrong and it is annoying. Get the same step wrong across the book and it is a project.

A whole-book migration breaks down into four parts:

1. Extraction. Getting clean data out of Sage for every client. This is usually a set of exports from Sage 50 desktop or Sage Business Cloud Accounting.
2. Interpretation. Working out what each file is and how each figure should be treated in the new ledger.
3. Construction. Building balanced double-entry opening positions so each client's accounts tie back to where they were in Sage.
4. Review and sign-off. Checking the result before it becomes live data you will file from.

The traditional way to do this is manual: a spreadsheet per client, a person mapping nominal codes by hand, and a lot of cross-checking. The AccountsOS approach automates the interpretation and construction so your team's time goes into review, which is where their judgement actually adds value.

What data comes across from Sage?

Here is what you export from Sage and what each file becomes inside AccountsOS.

You do not have to provide every file for every client. The AI works with what you give it and tells you what is missing rather than guessing. For most clients a trial balance plus the customer and supplier lists and the open AR and AP positions is enough to stand the company up accurately.

How do I migrate my client book? Step by step

Here is the practical sequence for moving a book of clients from Sage to AccountsOS.

1. Set up your practice account. Create your AccountsOS practice and choose Practice Mode. This is the single dashboard you will run every client from.
2. Export each client's data from Sage. From Sage 50 desktop or Sage Business Cloud Accounting, export the trial balance, nominal ledger, customer and supplier lists, open invoices and bills, opening balances, and VAT history. Save them per client so you know which files belong to whom.
3. Pick a clean migration date. Usually a period end or a VAT quarter end. Migrating as at a clean date keeps the opening position tidy and makes the first post-migration return easy to reconcile.
4. Upload each client's exports into the bulk migration tool. Paste or upload the files for a client. You do not need to label them by type. The AI reads each file and works out whether it is a trial balance, a contact list, open AR or AP, opening balances, or VAT history.
5. Let AccountsOS create a company per client. Each client becomes its own company under your practice, with its own ledger, contacts, and opening position. Nothing is shared between clients except your access to all of them.
6. Review the import preview. Before anything posts, AccountsOS shows you exactly what it intends to import for that client: which figures map to which accounts, the opening balances it will post, the contacts it will create, and the open items it will carry forward.
7. Check the balance and the treatment. The AI proposes the treatment; deterministic code guarantees the double-entry balances. Any residual that cannot be allocated goes to an opening-balance equity account, transparently and visibly, so you can see and resolve it rather than have it hidden.
8. Approve and post. When you are happy, approve. The opening position posts to the General Ledger. Repeat for the next client.
9. Connect the live feeds. Add each client's bank feed or upload statements so Finn can start categorising and reconciling from the migration date forward.
10. Verify the first period. Run a trial balance in AccountsOS and confirm it ties back to the Sage closing position. From there, the next VAT return and month-end run as normal.

The repetitive parts, reading the files and building the balanced opening journals, are automated. Your team's job is the review at step 6 and step 7, which is exactly where professional judgement belongs.

How does AccountsOS handle the migration differently?

The difference is that the interpretation is done by AI rather than by a person mapping fields, and the money math is done by deterministic code rather than by the AI.

When you upload a client's exports, the AI reads each file in context. It does not rely on the file name or a rigid template. It works out what the file is and what should happen to each line, the same way an experienced bookkeeper would glance at an export and know it is an aged creditors report. It then proposes a treatment: this column is the nominal balance, these are open supplier invoices, this is the VAT control account, and so on.

That proposal is then executed by deterministic code that guarantees the double-entry balances by construction. The AI never decides the final numbers and never posts unbalanced journals. Anything that does not reconcile is pushed to an opening-balance equity account and shown to you clearly, so a small difference becomes a visible line to investigate rather than a silent error buried in the ledger.

Then you review. Nothing posts until you approve it. This is the principle that runs through the whole tool: AI proposes, deterministic code guarantees the balance, the accountant reviews and signs off. You stay in control of every client's books.

The same engine powers a company per client, so a whole-book migration is the single-company flow repeated, with the heavy lifting automated each time.

How does running the practice change after migration?

Once clients are migrated, the day-to-day changes because Finn, the AI accountant, works across every client continuously.

Finn handles categorisation, reconciliation, and month-end in the background for each company. Instead of a team member opening each client's file to code transactions and chase a reconciliation, Finn does the routine work and surfaces only the exceptions that need a human decision. The practical effect is that each person can service more clients without the per-client workload rising in step.

Your clients do not need to log in. Under Practice Mode they are covered by your practice plan, not billed their own subscription, and you have full access to every client's books from one dashboard. For practices used to managing multiple logins or client invites, this is a simpler model: you hold the relationship and the access, the client does not have to learn new software.

How does AccountsOS compare with Sage for a practice?

A straight comparison of the things that matter when you are running a book of clients.

The point of the table is not that Sage cannot do the job. It is that the design choices, desktop heritage, rule engines, and per-seat licensing, all pull in the opposite direction from where a scaling, cloud-first practice wants to go.

What does it cost to move a whole client book?

AccountsOS Practice Mode is one flat price. It is £299 per month for unlimited clients, or from £5 per client per month with a minimum of 20 clients. You choose whichever works out cheaper for the size of your book.

Crucially, your clients are covered by the practice plan. They are not billed their own subscription, so there is no per-client cost landing on the client and no awkward conversation about who pays for the software. The economics improve as you migrate more of your book, because the flat practice fee spreads across more clients. That is the opposite of a per-seat or per-client licensing model, where each addition pushes the bill up.

There is no separate charge to use the bulk migration tool. Migration is part of getting your book onto the platform.

Frequently Asked Questions

How long does it take to migrate a whole client book from Sage?

It depends on the size of your book and how clean your Sage exports are, but the per-client work is fast because the AI handles the interpretation and the balancing. The time you spend is mostly reviewing the import preview for each client and confirming the opening position ties back to Sage. Most practices migrate in waves, starting with a handful of clients to get comfortable with the flow, then moving the rest in batches.

Do I need to export from Sage 50 desktop or Sage Business Cloud Accounting?

Either, depending on what each client is on. AccountsOS works from the standard exports both produce: trial balance, nominal ledger, customer and supplier lists, open invoices and bills, opening balances, and VAT history. The AI reads whatever format the export comes in and works out what it is, so you do not need to reformat the files or match a specific template.

Will my opening balances and trial balance still tie back to Sage?

Yes. The deterministic engine guarantees the double-entry balances by construction, and any residual that cannot be allocated is posted to a visible opening-balance equity account rather than hidden. After import you run a trial balance in AccountsOS and confirm it matches the Sage closing position as at your migration date. Because you review the full preview before anything posts, you catch any discrepancy before it becomes live data.

Does each client get their own company, or is it all one ledger?

Each client becomes its own separate company under your practice, with its own ledger, contacts, opening balances, and VAT position. Nothing is mixed between clients. You, as the adviser, have full access to every company from one dashboard, which is what makes running the whole book from a single login possible.

Do my clients have to log in or pay for anything?

No. Under Practice Mode your clients are covered by the practice plan and never need to log in. There is no separate client subscription and no per-client bill landing on them. You hold the access and the relationship, which keeps the experience simple for clients who do not want to learn new software.

Is AccountsOS suitable for MTD VAT?

Yes. AccountsOS is HMRC-recognised software for MTD VAT, and the migration carries across each client's VAT history so the next return follows on cleanly from where Sage left off. MTD for Income Tax is coming in April 2026, and the platform is built for that direction of travel.

What happens to VAT history during migration?

You can include each client's VAT history in the export, and AccountsOS uses it to maintain continuity, so the next VAT period in AccountsOS picks up correctly from the last filed period in Sage. This matters most for clients mid-quarter at the point of migration, where you want the next return to reconcile without a gap or an overlap.

Can I migrate clients gradually rather than all at once?

Yes, and most practices do. The migration tool works one client at a time, so you can move a first batch, get comfortable with the review flow, and then bring the rest of the book across in waves. There is no requirement to switch everyone on the same day, which keeps the disruption to your team manageable.

Ready to move your practice off Sage?

Migrating a client book is a one-time effort with a lasting payoff: a cloud-native, AI-native platform where Finn does the routine work across every client, one flat price covers your whole book, and your clients never have to log in or pay a separate subscription. The bulk migration tool does the heavy lifting of reading each Sage export and building a balanced company per client, and you stay in control by reviewing everything before it posts. To see how Practice Mode works and start moving your book across, visit /for-accountants.