By Thaddée Leblond · Published · Updated: June 2026
An ERP's price is not the licence. The real items are integration, data migration, training and change management, then recurring maintenance — often far more than the licence itself. The only figure that matters is the total cost over 3 to 5 years, contingencies included.
The licence is only the visible part
Focusing on the headline price leads straight to budget overrun. The licence (or subscription) is only a fraction of the real spend. It is the "surrounding" items that make the final bill.
The items to include
A realistic ERP budget adds several lines: the licence or subscription; integration and configuration (often the heaviest item); data migration and cleaning; any custom development; interfaces with your other tools; user training; change management; and recurring maintenance. On top of that, internally, the time of your teams mobilised on the project.
SaaS or licence: two cost logics
A SaaS ERP spreads spend into a recurring subscription, usually per user, including hosting and updates. A classic licence implies a larger upfront investment and infrastructure costs. The right choice depends on your cash flow, your strategy and your data constraints — not a universal rule.
The hidden costs to anticipate
Overruns often come from the invisible: underestimated internal time, custom development discovered along the way, data quality worse than expected, interfaces more complex than announced, and a temporary drop in productivity during the switch. Naming them upfront avoids nasty surprises.
Building a defensible budget
Reason in total cost over several years, include every item, and allow a margin for contingencies. A precise requirements specification is your best ally: the clearer your needs, the more reliable and comparable the quotes. An honest budget beats an optimistic one that will explode mid-project.
Costs vary widely by size, sector and scope. Refine these orders of magnitude with quotes based on your requirements specification.
Frequently asked questions
No, often far from it. Integration, data migration, training and change management, then recurring maintenance, generally weigh more than the licence itself.
SaaS spreads the cost into a recurring subscription (often per user, per month) and includes hosting and updates. A licence implies a heavier upfront investment and infrastructure costs. The choice depends on your cash flow and strategy.
The internal time your teams spend, unforeseen custom development, data migration and cleaning, interfaces with your other tools, and a temporary drop in productivity during the transition.
By reasoning in total cost over 3 to 5 years, including every item (licence, integration, data, training, maintenance, internal time) and allowing a margin for contingencies. A precise requirements specification makes the estimate more reliable.
Sources
- Total-cost-of-ownership methodology for an ERP project