Can you keep Sage and modernise everything around it?
Yes — and the specifics depend on which Sage 200 you're actually on, Standard or Professional. Either way, you can keep Sage as your system of record and build a bespoke, real-time interface on top of it, without a rip-and-replace or an ERP migration, and without losing the setup your business already runs on. This is what Sysgraft calls a graft: a precise join between a new intelligent layer and the systems you already own.
Should you replace Sage, or build around it?
For most £1.5m–£20m+ UK businesses, the honest answer is: build around it.
Sage is the system we're asked about most, and it's usually not the problem. It's an accounting system, and it does that job well. The problem is that Sage was never designed to be a live, cross-business dashboard. The frustration leaders feel ("why can't I see margin in real time?", "why does month-end still take a week?") isn't a reason to tear Sage out. It's a reason to add a layer it was never meant to provide.
Ripping out a working accounting system to solve a reporting and visibility problem is one of the most expensive mistakes a mid-market business can make: months of migration, retraining, data risk, and disruption — to fix something a graft would fix without any of it.
What connecting to Sage 200 actually involves
The first thing that matters is which Sage 200 you run, because they behave differently. Sage 200 Standard is cloud-hosted and has the API enabled by default — users just need to be given API access. Sage 200 Professional is installed on your own infrastructure, so external access has to be deliberately opened up. The cleaner route there is Sage's Native API, which tunnels through Microsoft 365's Azure Active Directory rather than requiring an internet-facing server — no extra hardware, but it does mean a valid Microsoft 365 subscription is a prerequisite.
There's a second, less obvious issue with Professional that catches people out. Because it's on-premise, sites drift between versions — and an endpoint documented by Sage may simply not exist on the version you're actually running. Checking your specific version against Sage's release history is part of doing this properly, not an afterthought, and it's one of the first things a discovery session establishes rather than assumes.
The honest limitation worth stating plainly: Sage 200's API is deliberately scoped, and it does not expose bespoke or custom fields. If your business has years of meaning encoded in custom fields — and many do — that data needs a different route than the standard API, which is exactly the kind of thing that should be established before anyone quotes you a price rather than discovered halfway through a build.
Common questions about modernising around Sage
Can custom software sit on top of Sage 200?
Yes. A bespoke interface can draw live data from Sage 200 — through its API on Standard, or the Native API tunnelling through Microsoft 365's Azure Active Directory on Professional — and present it alongside data from your CRM and other systems, giving leadership one real-time view without changing how Sage itself works.
Does it matter whether we run Sage 200 Standard or Professional?
Yes. Sage 200 Standard is cloud-hosted with the API enabled by default — users just need API access granted. Sage 200 Professional is installed on your own infrastructure, so external access has to be deliberately opened up, typically via Sage's Native API through Azure Active Directory rather than an internet-facing server.
Can I get a real-time dashboard from Sage without replacing it?
Yes. A dashboard built on Sage can show margin and cash position updating as transactions post, sat alongside your other systems — not a static export from last week.
Does Sage's API expose our custom fields?
Not by default. Sage 200's API is deliberately scoped and does not expose bespoke or custom fields. If your business has years of meaning encoded in custom fields, that data needs a different route than the standard API — established at discovery, not discovered halfway through a build.
Can I connect Sage to my CRM and see both in one place?
Yes. Grafting an interface across Sage and your CRM lets customer, sales and margin data appear together — the single view that neither system gives you alone.
Does keeping Sage limit what AI can do later?
No. What actually limits AI usefulness is fragmented data, not which accounting package — or which Sage 200 edition — you run. Once your operational data, custom fields included, is joined into one accessible place, AI features have something coherent to work with. Keeping Sage doesn't hold that back; scattered data does.
Modernising isn't migrating
The software industry has trained businesses to believe that "modernising" means a large, disruptive replacement project. It doesn't have to. Grafting a new layer onto Sage is modernisation without the migration — you move forward on visibility and capability while everything that currently works, Standard or Professional alike, keeps working.
See how the whole process works, step by step →
Get your AI Exposure snapshot Find out where your real constraint is — most often it isn't AI, and it isn't Sage