How much does an ERP cost? A UK budgeting guide

When a finance director asks about ERP price, the honest answer starts with a question: price of what? A software subscription, an implementation project, or the full cost of owning the system over its life? Most budgets that go wrong do so because only the first of these was priced.

This guide explains what an ERP costs in the UK, which lines make up the ERP budget, what pushes the total up or down, and how to compare quotes properly. We do not publish invented price ranges: they would be misleading, because the real cost depends on your scope. Where a vendor publishes a price, we quote it with its source.

The short answer: what does ERP software cost?

There is no single ERP software price. The total is the sum of several blocks:

• the licence or subscription to the software;
• the implementation, meaning analysis, configuration, integration and testing by an integrator;
• the data migration from your current systems;
• training and change management for your teams;
• support and maintenance once you are live;
• the infrastructure you pay for yourself, if you do not use the vendor’s cloud.

The licence is the most visible line because vendors publish it. It is rarely the whole story. A realistic ERP cost estimate always covers every block, over the full period you expect to use the system.

ERP cost breakdown: the main budget lines

The table below lists each cost line, what it covers and what makes it vary. It deliberately contains no amounts, because the amounts only exist once your scope is defined.

The last two lines are the ones most often forgotten. Internal time is real money even though it does not appear on an invoice, and a project without a reserve is a project that will either overrun or be cut back at the end.

Licences and subscriptions: what vendors publish

Subscription ERPs are usually priced per user per month. Prices below come from the vendors’ own pages and are quoted as published, in the currency shown there. They are not UK pounds sterling prices, and they will change, so always ask your integrator for a current quote.

Odoo

Odoo publishes its pricing openly, which makes it a useful reference for understanding how a licence is structured.

• A One App Free formula is available at 0 EUR. It is limited to a single application (plus its dependencies), hosted on Odoo Online, with unlimited users.
• Odoo Standard is listed at 24,90 EUR per user per month, with all applications on Odoo Online. A discount from 31,10 EUR applies for 12 months for users ordered at the start.
• Odoo Custom is listed at 44,90 EUR per user per month, with a discount from 56,90 EUR for 12 months. It can be hosted on Odoo Online, on Odoo.sh or on your own premises. Odoo.sh costs are not included.
• A light user is shown at 7,90 EUR per month, on appointment with an Odoo adviser.

Three details matter when you build a budget. First, Odoo Custom adds Odoo Studio, agentic AI, multi-company and external API access; installing Studio or adding companies moves a free database to Custom. Second, paying users are those with backend access, while portal users such as customers and suppliers are not counted as paying. Third, Odoo 19 Community is licensed under LGPLv3, whereas Odoo 19 Enterprise is licensed under the Odoo Enterprise Edition licence v1.0 and may be used only with a valid Enterprise subscription for the right number of users. For more on the open-source side, see our guide to open source ERP and our page on Odoo integrators.

Microsoft Dynamics 365 Business Central

On its US pricing page, Microsoft lists Business Central per user per month, billed annually:

• Essentials: 80 USD;
• Premium: 110 USD;
• Team Members: 8 USD.

Microsoft adds that displayed prices may differ from the actual catalogue price depending on currency, country and regional variant, and that the final price appears at checkout. So treat the dollar figures as an indication of the pricing structure, not a UK price.

On localisation, Microsoft delivers Business Central directly in a list of countries that includes the United Kingdom. For other countries, localisation comes from partner-built apps available on Marketplace. For UK buyers this means the product is supported natively, but you should still confirm with your integrator how UK-specific requirements such as VAT reporting are handled. See our page on Business Central integrators.

Sage, Oracle NetSuite and SAP Business One

We do not quote prices for these three, because we have no verified published figure to cite. What can be said safely is how they are typically structured:

• Sage offers business software that is familiar to many UK finance teams; pricing and packaging depend on the product and edition, so a quote from an integrator is the only reliable source. See our page on Sage integrators.
• Oracle NetSuite is a cloud ERP sold as a subscription, with the price depending on the modules and users you select. See NetSuite integrators.
• SAP Business One is aimed at small and mid-sized companies and is typically sold through an integrator, which adds its own services to the licence. See SAP Business One integrators.

If a quote for any of these products arrives without a clear breakdown of licence, services and recurring fees, ask for one before you compare it with anything else.

Subscription, perpetual licence or open source: how the model changes the budget

The licensing model shapes when you pay, not only how much.

Subscription (SaaS). You pay monthly or annually, and the vendor looks after hosting and upgrades. Cash outlay at the start is lower, but the subscription never ends and grows with headcount. It is usually treated as operating expenditure.

Perpetual licence with annual maintenance. You pay a larger sum upfront and then an annual fee for support and upgrades. This model is less common for new projects, and it moves more of the infrastructure burden onto you.

Open source. The software licence can be free, but you still pay for hosting, implementation, support and sometimes paid modules. Free software is not free to run.

Our guide to cloud versus on-premise ERP goes further into how hosting changes both the cost and the risk profile.

Implementation: usually the second big line

The integrator’s work is what turns a licence into a working system. It typically includes:

1. Discovery and analysis of your processes and requirements.
2. Configuration: chart of accounts, VAT codes, warehouses, price lists, approval flows.
3. Customisation and development, where standard functions are not enough.
4. Integrations with other systems.
5. Testing, including user acceptance.
6. Go-live support and the first month-end close.

Integrators price this either as a fixed price for a defined scope or on a time-and-materials basis (a daily rate for the hours worked). Neither is automatically better. A fixed price protects you if the scope is genuinely well defined; it can become a source of disputes if the scope is vague, because every change then becomes a chargeable change request. Time and materials offers flexibility but demands good project governance.

The single best way to control this line is to write your needs down before you ask for quotes. Our ERP requirements template helps with that, and the guide to ERP implementation describes the project phases in detail.

Data migration: the cost people underestimate

Moving data into a new ERP is rarely a simple copy. Customer and supplier records are duplicated, item codes are inconsistent, opening balances must reconcile with the ledger, and open orders and invoices need careful cut-over.

Budget for three activities: cleaning the data at source, mapping it to the new structure, and validating the result with the people who know the business. Decide early how much history you really need. Loading every transaction from years ago costs more and adds little; keeping an archive of the old system is often cheaper.

For a fuller discussion, see ERP migration.

Training, change management and support

A system that nobody uses properly is the most expensive system of all. Training is not only a matter of a day with a trainer: it includes documentation, key-user coaching and time for your people to practise before go-live.

After go-live, expect continuing support and maintenance. Subscription ERPs include vendor upgrades, but you will still need someone to handle user requests, small changes, report requests and the effect of each new release on your customisations. Decide whether that someone is an internal administrator, your integrator on a support contract, or a combination.

Factors that make the budget go up or down

The same product can cost very different amounts for two companies. These are the main drivers:

• Number and type of users. Full users cost more than limited ones, such as the light and Team Members profiles mentioned above.
• Scope of processes. Finance alone is a smaller project than finance, stock, manufacturing and e-commerce together.
• Customisation. Each deviation from standard adds build, test and upgrade cost. Adapting your process to the standard product is often cheaper than adapting the product to your process.
• Number of entities, sites and currencies. Multi-company and multi-currency set-ups add configuration and testing.
• Data quality and volume. Clean data is cheap to migrate; messy data is not.
• Integrations. Each connected system is a small project in its own right.
• Regulatory requirements. Making Tax Digital, VAT rules and sector rules affect configuration. For the invoicing side, see ERP and e-invoicing.
• Industry specifics. Manufacturing, distribution and construction usually need more than a services firm; our industry pages show what changes.
• Internal readiness. A decision-maker with time and a motivated project team save money.

Total cost of ownership: think in years, not in a first invoice

The right unit for an ERP budget is the total cost of ownership over the period you expect to keep the system. It should combine:

• the initial project cost: implementation, migration, integration and training;
• the recurring costs: subscriptions, hosting, support, administration;
• the change costs: new modules, new users, new entities, upgrades;
• the internal costs: staff time, and the productivity dip around go-live;
• the exit cost: what it would take to leave the system one day, including data export.

Put these side by side for each shortlisted option over the same number of years. A cheaper subscription with an expensive project can end up costlier than a dearer subscription with a lighter project, and the reverse is also true. Only a multi-year comparison reveals which.

Remember also that growth changes the picture. If your headcount is set to rise, a per-user subscription rises with it; if you plan to add a company or a warehouse, ask in advance what that does to the price.

How to compare ERP quotes properly

Comparing quotes from different integrators is difficult because they rarely look alike. A few habits make it much easier.

1. Give every bidder the same requirements. A shared document is the only way to get comparable answers.
2. Ask for a breakdown. Licences, implementation, migration, training, support and hosting should each appear on their own line.
3. Check what is excluded. Quotes often leave out data migration, integrations, training or travel. An exclusion is a cost you will pay later.
4. Ask what is fixed and what is estimated. A time estimate is not a commitment.
5. Check the assumptions. Number of users, sites, interfaces, data volumes and workshop days all drive the price.
6. Ask how changes are handled. What triggers a change request and how it is priced is worth knowing before you sign.
7. Compare over the same period. Put every offer on the same multi-year basis.
8. Look at the team. A low price with an inexperienced team is a risk, not a saving.
9. Request references in your sector. Ask for conversations with customers of a similar size and activity.

Our guide on choosing an ERP integrator covers the selection criteria beyond price, and how it works explains how we match your project to suitable integrators for free.

Budgeting mistakes to avoid

• Pricing the licence only. The project and the running costs are then missing.
• Having no contingency. Scope grows in almost every project.
• Treating customisation as free. It has to be built, tested and carried through every upgrade.
• Underestimating internal effort. Your people will spend real time on the project.
• Skipping training. Poor adoption erodes the return on the whole investment.
• Choosing on the lowest quote. An incomplete quote is a low quote.
• Forgetting the exit. Know how you would retrieve your data.

Several of these appear in our review of ERP project mistakes.

Where to start

Begin with your own needs, not a price. Write down your processes, your users and your integrations, and decide what really matters. Then gather quotes on that common basis and compare the total cost over the same period. If you are weighing several products, our comparisons and the guide on how to choose an ERP will help narrow the field before you ask for prices, and if you are a smaller company, the page on ERP for small business addresses the specific constraints.

If you would rather not approach integrators one by one, tell us about your project. We put you in touch with a suitable integrator, at no charge; the integrator then scopes and quotes the work. We are not affiliated with any software vendor, and we do not carry out the implementation ourselves.

Software names mentioned are trademarks of their respective publishers and are referred to for information only. This site is independent and is not affiliated with any software publisher.