✦ ERP and CRM
What does an ERP system cost in the UK?
ERP system cost is never one number. It's a licence or subscription fee, an implementation fee, data migration, training, and ongoing support, and the second one usually dwarfs the first. Here's what drives each up or down.
Haystak · 11 August 2026 · Updated 11 August 2026 · 8 min read
ERP system cost is made up of five separate categories, and any quote that gives you a single figure is hiding which of those five it actually covers. The licence or subscription is often the smallest of the five for a mid-sized business, not the biggest.
This isn't a page of prices - anyone quoting a firm number without seeing your data, your process count and your team's current setup is guessing. It's a page about what makes each part of the bill bigger or smaller, so you can ask vendors better questions and get a real number for your business.
The five things you're actually paying for
Every ERP project, whether you buy an off-the-shelf product or commission something built around you, breaks down into the same five cost categories. Vendors bundle them differently, which is exactly why comparing two quotes on price alone is close to meaningless.
| Category | What it covers | What pushes it up |
|---|---|---|
| Licence / subscription | Right to use the software, per user or per site | More users, premium modules, multi-entity |
| Implementation | Configuration, workflow setup, testing, project management | Number of processes covered, how far from the standard product you sit |
| Data migration | Moving stock, customer, order and financial history in cleanly | Poor existing data quality, multiple legacy sources, no single source of truth today |
| Training | Getting staff actually able to use it | Number of roles and sites, resistance to change, staff turnover |
| Ongoing support | Updates, fixes, help desk, minor changes after go-live | Complexity of the build, number of integrations, response time you need |
Off-the-shelf vs a bespoke build
A standard product - Xero, Sage, Odoo, Microsoft Dynamics 365 Business Central, NetSuite - spreads its cost differently to a bespoke system. The licence is ongoing and covers a wide, general feature set; implementation is usually configuration rather than development, which keeps it faster and cheaper for a standard process.
A bespoke system built round your process has no ongoing licence fee, but the build itself carries the cost that a standard product's implementation would - the difference is that you're paying to have your specific process represented properly rather than working around a generic one. Neither is inherently cheaper; it depends how far your process sits from what an off-the-shelf product assumes.
- A standard business with a common process: off-the-shelf usually costs less overall, because implementation is largely configuration.
- A process with a genuine quirk - costing rules, compliance records, scheduling constraints from your equipment: forcing it into a standard product often costs more in workarounds than a build would have cost outright.
- A hybrid is common and often sensible: a standard ERP core with one or two bespoke modules or integrations bolted on for the parts that don't fit.
What makes implementation more expensive
Implementation cost tracks two things: how many of your processes the system needs to cover, and how far those processes sit from the product's assumptions. A business with one site, one currency and a straightforward order-to-cash process is a short, predictable implementation. Add multiple sites, custom approval chains, or a manufacturing process with unusual scheduling rules, and the same product takes considerably longer to configure and test.
This is why business process mapping before you talk to any vendor is worth the time - it tells you, and them, exactly how many processes are in scope before anyone puts a number on paper.
Why data migration is where budgets actually slip
Moving data cleanly assumes the source data is clean, and it rarely is. Duplicate customer records, stock counts that haven't matched the warehouse in years, or supplier data spread across three spreadsheets all have to be reconciled before they can be migrated - and that reconciliation is manual, skilled work regardless of which system you're moving to.
Ask any vendor, early, whether their quote includes data cleansing or only the technical migration step. Those are very different amounts of work.
The cost that gets forgotten: support after go-live
A system that works perfectly on go-live day still needs someone to fix the inevitable small issues, add a new report, or adjust a workflow as your business changes. Ongoing support is usually priced separately and is worth budgeting for as a permanent line rather than a one-off. If you're weighing this against SaaS vs owning your software, support cost is one of the clearest differences between the two models.
HMRC's Making Tax Digital requirements are also worth checking against any ERP finance module before you sign anything, since non-compliant record-keeping can create cost you didn't budget for later.
How to get an actual number
- 01Map your core processes first - even roughly - so vendors are quoting against the same scope.
- 02Ask each vendor for the five categories above broken out separately, not a single total.
- 03Get an honest view of your current data quality before anyone quotes migration.
- 04Ask what ongoing support costs once the initial contract period ends, not just the launch price.
- 05Compare like-for-like scope, not just the bottom line, across any quotes you receive.
The only reliable way to get a number for your business is a conversation about your actual process and data. Get in touch and we'll give you a straight answer, including when the honest answer is a standard product rather than anything we'd build.
✦ Where this fits
More on this from us: bespoke systems built round your process.