Can you keep Epicor and modernise everything around it?
Yes. Epicor can stay your system of record on the shop floor and in the back office alike, 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 Epicor, or build around it?
For most £1.5m–£20m+ UK manufacturing businesses, the honest answer is: build around it.
Epicor Kinetic is usually not the problem. It's a manufacturing ERP system, and it does that job well. The problem is that it was never designed to be a live, cross-business dashboard for leadership — it wasn't built to show margin by job, or cash position, alongside production data on one screen. 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 Epicor 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 manufacturer can make: months of migration, retraining, data risk, and disruption — to fix something a graft would fix without any of it.
What connecting to Epicor actually involves
Epicor Kinetic exposes a documented Open REST API built on the OData v4 standard, covering Business Objects, Business Activity Queries (BAQs) and Epicor Functions — the same building blocks Epicor's own engineers use internally. This replaced Epicor's older SOAP-based API, so if you're looking at documentation or a previous integration that predates the move to REST, it's worth confirming which generation you're actually looking at.
Kinetic's own API being documented and versioned this way means a graft onto Epicor is working with the platform as Epicor intends it to be extended, not around a workaround bolted on from outside.
Common questions about modernising around Epicor
Can custom software sit on top of Epicor?
Yes. Epicor Kinetic exposes an Open REST API built on the OData v4 standard, covering Business Objects, Business Activity Queries (BAQs) and Epicor Functions. A bespoke interface can draw live data through that API and present it alongside data from your CRM and other systems — giving leadership one real-time view without changing how Epicor itself works.
Can I get a real-time dashboard from Epicor without replacing it?
Yes. A dashboard built on Epicor can show job costs and production status updating live, sat alongside your other systems — the kind of view Kinetic's own screens weren't designed to give leadership.
Is Epicor the problem, or our processes?
Often, neither is fully the culprit. Epicor runs production, purchasing and inventory the way it's supposed to — the real issue is usually that job costs, margin and shop-floor status live in three different places, none of them the screen leadership actually looks at.
Can I connect Epicor to my CRM and see both in one place?
Yes. Grafting an interface across Epicor and your CRM lets customer, sales and production data appear together — the single view that neither system gives you alone.
Does keeping Epicor limit what AI can do later?
Kinetic's modern, documented API if anything argues the other way: once your production and job-cost data is joined into one place, AI features have something genuinely coherent to draw on. What 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 Epicor is modernisation without the migration — you move forward on visibility and capability while the shop floor keeps running exactly as it does today.
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 Epicor