Can you keep NetSuite and modernise everything around it?
Yes. NetSuite can stay your system of record while a bespoke, real-time interface gets built on top of it, designed to work within its concurrency limits rather than against them — 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 NetSuite, or build around it?
For most £1.5m–£20m+ UK businesses, the honest answer is: build around it.
NetSuite is usually not the problem. It's a cloud ERP system built to run finance, inventory and operations — and for most businesses it does that job well. The problem is that even a capable ERP wasn't 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 NetSuite 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 NetSuite actually involves
NetSuite governs integrations differently from most systems, and the difference matters. Where Xero or Business Central count requests per minute, NetSuite limits how many requests can run at the same instant — typically around ten to fifteen concurrent for a standard account. Volume over the day isn't usually the constraint. Simultaneity is.
Two consequences follow, and neither is obvious until you hit them. First, that concurrency budget is shared across every integration on the account — so a middleware connector or a payroll sync you already run is consuming the same slots a new reporting layer would need. Second, raising the ceiling isn't an engineering fix: additional capacity comes from SuiteCloud Plus licences bought from Oracle. Whether a graft needs one is a question worth answering during discovery, not after go-live.
The upside is that NetSuite gives you an unusually efficient way to read data. SuiteQL allows SQL-style queries returning far more per call than the standard REST endpoints, which cap out at a thousand rows. For the kind of joined, historical view leadership reporting needs, that's the difference between a handful of queries and several thousand — which, given the concurrency model, is precisely the difference that keeps an integration inside its budget.
Common questions about modernising around NetSuite
Can custom software sit on top of NetSuite?
Yes. A bespoke interface can draw live data from NetSuite through its API and present it alongside data from your CRM and other systems — giving leadership one real-time view without changing how NetSuite itself works.
Can I get a real-time dashboard from NetSuite without replacing it?
Yes. A dashboard can read live from NetSuite alongside your other systems — the concurrency limits shape how the build queries the data, not whether real-time visibility is possible.
Is NetSuite the problem, or our processes?
Often, neither is fully the culprit. NetSuite is a genuinely capable cloud ERP — the real gap is usually that its own reporting doesn't reach the specific, cross-business view leadership actually wants, and that's solvable without touching the platform underneath.
Can I connect NetSuite to my CRM and see both in one place?
Yes. Grafting an interface across NetSuite and your CRM lets customer, sales and financial data appear together, without either system needing to become the other's system of record.
Does keeping NetSuite limit what AI can do later?
No. What limits AI usefulness is fragmented data, not NetSuite's concurrency limits or which ERP you run — those govern how a build is engineered, not what's ultimately possible once your data is joined up.
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 NetSuite is modernisation without the migration — you move forward on visibility and capability while NetSuite carries on exactly as it does today, concurrency limits and all.
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 NetSuite