Can you keep SAP Business One and modernise everything around it?
Yes. Business One stays exactly as it is — enforcing the same validation it always has — while a bespoke, real-time interface gets built on top of it. No rip-and-replace, no ERP migration, and nothing lost from 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 SAP Business One, or build around it?
For most £1.5m–£20m+ UK businesses, the honest answer is: build around it.
SAP Business One is usually not the problem. It's the SME-scoped version of SAP's ERP, built to run finance and operations for smaller businesses — and it does that job well. The problem is that it was never designed as a live, cross-business dashboard for leadership. 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 it out. It's a reason to add a layer it was never meant to provide.
Ripping out a working ERP 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 SAP Business One actually involves
Business One offers two routes in, and the choice isn't arbitrary. The Service Layer is the modern one — a REST/OData interface, multi-threaded, and the right choice for anything that needs to serve several requests at once. The older DI API is a .NET library that reaches deeper into the system but is single-threaded, which makes it a poor foundation for a live reporting layer regardless of its other merits.
One genuinely useful property: the Service Layer sits on top of the same business-object layer the desktop client uses. That means it enforces exactly the same validation rules as the application itself — an integration can't write a record through the API that a person couldn't have created through the UI. For anything writing back into your ledger, that's a meaningful safety property rather than a technicality.
Two practical notes. Business One runs on either Microsoft SQL Server or SAP HANA, and which one you're on affects deployment specifics, so it's an early question rather than a detail. And unlike some accounting systems, Business One does expose user-defined fields and tables through the API — they carry a U_ prefix. If years of your business's actual meaning lives in custom fields, that's genuinely good news here, and it's not true everywhere.
Common questions about modernising around SAP Business One
Can custom software sit on top of SAP Business One?
Yes. A bespoke interface can draw live data from SAP Business One through its data connections and present it alongside data from your CRM and other systems — giving leadership one real-time view without changing how SAP Business One itself works.
Can I get a real-time dashboard from SAP Business One without replacing it?
Yes. A dashboard built through Business One's Service Layer reads the same live data the desktop client shows, presented alongside your other systems rather than in a separate screen.
Is SAP Business One the problem, or our processes?
Often, neither is fully the culprit. Business One's validation rules exist for good reason — the real issue is usually that the data behind them never reaches a screen built for leadership rather than transaction entry. That's solvable without touching the platform.
Can I connect SAP Business One to my CRM and see both in one place?
Yes. Grafting an interface across Business One and your CRM lets customer, sales and finance data appear together, read through the same Service Layer that already governs everything else in the system.
Does keeping SAP Business One limit what AI can do later?
If anything, Business One's Service Layer helps here: because it enforces the same validation the desktop client does, the data an AI feature would draw on is exactly as trustworthy as what your team already sees. What actually limits AI usefulness is fragmented data, not which ERP you run.
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 SAP Business One is modernisation without the migration — you move forward on visibility and capability while Business One keeps enforcing the same validation it always has.
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 SAP Business One