When you receive an ERP quote, the numbers look precise and manageable. Three to six months into the project, reality starts to emerge: optional modules billed separately, unanticipated custom developments, two internal FTEs mobilised without any budget allocation, data quality issues that triple the migration timeline. This is not an edge case. According to the annual benchmarks from Panorama Consulting, the leading causes of ERP budget overruns are underestimating project resources (38%), scope expansion (35%), and technical or data problems (34%).
The 5-year TCO (Total Cost of Ownership) is the only honest metric for comparing ERP vendors. This article gives you the method and comparative tables to build it, whether you are evaluating solutions for a 50-person SME or a 300-person mid-market company.
This guide covers the TCO method and comparative figures by company size. For the detailed breakdown of 8 hidden cost categories (data migration, middleware, staff turnover…), see our full ERP TCO analysis.
Why ERP TCO Is Almost Always Underestimated
The Initial Quote vs. the Final Invoice: A Structural Gap
The quote you receive from a vendor or integrator typically covers two line items: licences or subscriptions, and implementation services. These two items represent approximately 30 to 40% of what you will actually spend over five years.
This is not a question of bad faith. It is the structure of the ERP market itself: vendors sell licences, integrators sell consulting time. Neither has an incentive to front-load the costs you will bear afterwards — namely maintenance, ongoing training, system evolution, and internal resource allocation.
The industry rule of thumb: total five-year cost runs 3 to 5 times the initial budget stated in the commercial proposal. This ratio varies by company size, functional scope, and deployment model (cloud vs. on-premise).
The 4 Cost Categories That Vendors Rarely Highlight
To build a reliable TCO, you need to think in four categories, not two:
- Category 1: Licences and subscriptions (the only one quotes systematically detail)
- Category 2: Implementation and integration (partially covered in quotes, but often underestimated)
- Category 3: Training and change management (often reduced to a token package in year 1)
- Category 4: Maintenance, TMA, and evolution (rarely present in quotes, yet recurring throughout the system’s lifetime)
The 3-Envelope Rule
A useful framework for presenting TCO to an executive committee: think of 3 broadly equal budget envelopes.
- Envelope 1: Licences (SaaS subscriptions or perpetual licences)
- Envelope 2: Implementation (integration, migration, initial training)
- Envelope 3: Run (maintenance, evolution, ongoing training, managed services)
The classic trap: organisations budget envelopes 1 and 2, then discover envelope 3 after go-live. Over a five-year horizon, envelope 3 is often as large as envelope 2 — sometimes larger.
Category 1: Licences and SaaS Subscriptions
Pricing Models: Named User, Concurrent, Module, or Revenue-Based
Modern ERPs use several pricing models:
- Named user: every employee with an active account is billed. Dominant model in SaaS (Odoo, Dynamics 365, NetSuite).
- Concurrent user: only the maximum number of simultaneous users is billed. Advantageous for teams working in shifts.
- Per module: each functional application (CRM, purchasing, production, accounting) is billed separately. The bill escalates quickly once you step outside the standard scope.
- Revenue or transaction-based: less common, used by some e-commerce or distribution specialists.
Indicative Pricing Grid 2026: Ranges by Vendor
These ranges are indicative and illustrative. They vary significantly depending on scope, number of users, region, and commercial negotiations. Do not use them as a contractual basis without verification from the vendor or their partner.
SME solutions (50 to 150 users)
| Vendor | Model | Monthly range per user |
|---|---|---|
| Odoo Enterprise Standard | Named user | €19.90/user/month (official price odoo.com/pricing) |
| Odoo Enterprise Custom | Named user | €29.90/user/month |
| Microsoft Dynamics 365 BC Essentials | Named user | €65–85/user/month |
| Microsoft Dynamics 365 BC Premium | Named user | €95–115/user/month |
| Sage 100 Cloud | Per user | €40–90/user/month depending on modules |
| SAP Business One Cloud | Per user | €100–200/user/month depending on modules |
Mid-market solutions (150 to 500 users)
| Vendor | Model | Indicative range |
|---|---|---|
| SAP S/4HANA Cloud Public Edition | Per user | €200–400/user/month (full-access users) |
| Oracle NetSuite | Per user + modules | €100–300/user/month + modules |
| Microsoft Dynamics 365 Finance | Per user | €145–200/user/month |
| Sage X3 | Per concurrent user | €200–400/concurrent user/month |
Pricing Gotchas
Four recurring traps to know before signing:
- Optional modules: packages presented as “all-inclusive” have exceptions. Advanced workflow configuration, ad hoc reporting, or certain industry-specific modules are often paid add-ons.
- Light or read-only users: often free or low-cost, but with limited rights. Check whether your managers need full access.
- Test and pre-production environments: SaaS vendors sometimes bill additional environments. Verify this systematically in the contract.
- Additional storage: beyond a base quota, file storage (attachments, invoice documents) can be billed separately.
Perpetual Licences vs. SaaS: Calculating the Break-Even
For vendors that still offer perpetual licences (SAP Business One On-Premise, Sage 100 Perpetual), the break-even is straightforward:
Break-even (years) = Perpetual licence price / (Annual SaaS subscription − Annual on-premise maintenance)
In practice, the break-even falls between 4 and 7 years for most comparisons. Beyond 5 years, on-premise is often cheaper on the licence line alone. But this calculation omits infrastructure, major version upgrades, and internal skills requirements — which typically tip the balance back toward SaaS.
Category 2: Implementation and Integration
Consulting Costs: Day Rate Ranges by Integrator Type
Daily rates vary significantly depending on the integrator profile:
| Integrator profile | Indicative day rate (2026) |
|---|---|
| Global consulting firm (SAP, Oracle, Accenture-tier) | €1,200–2,000/day |
| National ERP integrator (500+ consultants) | €900–1,400/day |
| Regional or specialist integrator | €700–1,100/day |
| Independent consultant | €600–900/day |
For a 50-person SME, a realistic implementation mobilises between 100 and 400 consulting days depending on complexity. For a 300-person mid-market company, plan for 400 to 1,500 days.
Typical Duration by Company Size
- 50-person SME: 4 to 9 months, for a finance + purchasing + sales scope
- 300-person mid-market: 12 to 24 months for a multi-site rollout with production or distribution
- 1,000+ person group: 24 to 48 months for a multi-country ERP programme
Data Migration: The Frequently Forgotten Line Item
Data migration is systematically underestimated in initial quotes. The work involves two distinct phases that are often conflated:
- Cleansing: correcting duplicates, anomalies, and inconsistencies in the legacy system. This is business work, not IT — it mobilises 2 to 4 analysts over 2 to 5 months.
- Technical migration: extraction, transformation, and loading (ETL) into the new system.
Total cost range (cleansing + migration) based on data volume and quality:
| Context | Range |
|---|---|
| SME, relatively clean data | €15,000–50,000 |
| SME, heterogeneous data (multiple legacy systems) | €50,000–120,000 |
| Mid-market, single site | €80,000–250,000 |
| Mid-market, multi-site, complex data | €200,000–600,000 |
Integrations with Existing Systems
Each connection between the ERP and a third-party system has a cost. The most common for a mid-sized company:
- CRM (Salesforce, HubSpot, Dynamics CRM): €15,000–60,000 depending on complexity
- WMS or e-commerce platform: €20,000–80,000
- Banking portals (SWIFT, open banking APIs): €10,000–40,000
- E-invoicing network (Peppol, national mandate connectors): €5,000–25,000
- HR/payroll middleware (third-party payroll providers): €8,000–30,000
Maintaining these connectors (evolving APIs, third-party updates) represents a recurring cost of 10 to 20 hours per month once the system is live.
Category 3: Training and Change Management
Training Budget: Between 10% and 20% of Total Project Budget
The training line in ERP quotes typically covers initial sessions (system familiarisation, administrator training, super-users). That is not enough.
An organisation that invests properly in change management plans for:
- Year 1 (go-live): 15 to 20% of the total project budget for training and change management
- Years 2–5: 5 to 8% of the implementation budget per year for ongoing training, onboarding of new employees, and refresher cycles
Organisations that cut this line consistently experience low adoption rates, persistent Excel workarounds, and degraded ROI.
Quantifying the Post-Go-Live Productivity Loss
Productivity dips during any major system change. Here is the method to factor it into your business case:
- Estimate the trough duration: typically 3 to 6 months after go-live
- Estimate the depth: a 15–25% productivity loss is common during this period
- Apply to the payroll cost of the affected population
Example for an 80-person company, average fully-loaded salary of €50,000/year, 20% productivity loss over 4 months:
80 employees × €50,000 × 20% × (4/12) = €266,000 in lost productivity
This amount appears on no invoice, but it has a real impact on monthly closing times, delivery lead times, and customer satisfaction.
Dedicated Internal Staff: Rarely Budgeted, Always Essential
An ERP project mobilises internal resources in addition to the external consulting engagement:
| Role | Typical commitment |
|---|---|
| Internal project manager | 50–80% of time for the project duration |
| Key users by domain (finance, purchasing, production) | 20–40% of time |
| CIO or IT manager | 20–50% depending on complexity |
| Executive sponsor | 10–15% (steering committee, sign-offs) |
For a 300-person mid-market company, internal mobilisation represents 1 to 2 FTEs in total over 18 to 24 months. At a fully-loaded salary of €70,000/year, the “internal resources” envelope easily exceeds €200,000 for the project duration.
Category 4: Maintenance, Managed Services, and Evolution
Annual Vendor Maintenance Contracts
For perpetual licences, vendors typically charge 18 to 22% of the licence value per year for maintenance (updates, security patches, support). Over five years, this line represents 90% to 110% of the initial licence value.
For SaaS subscriptions, maintenance is theoretically included in the subscription fee. However, major updates may require external support to test and adapt customisations, generating a recurring managed services cost.
Upgrade Costs: Major Version Migrations Are Real Projects
Major version upgrades (Odoo 16 to 18, SAP ECC to S/4HANA, Sage 100 v18 to v20) are not automatic updates. They are mini-projects that include:
- Impact analysis of customisations and bespoke developments
- Non-regression testing across the full functional scope
- Rework or refactoring of incompatible customisations
- A fresh user training campaign
Cost range for a major version upgrade by context:
| Context | Indicative range |
|---|---|
| SME, lightly customised ERP | €15,000–50,000 |
| SME, heavily customised ERP | €50,000–150,000 |
| Mid-market, standard scope | €80,000–200,000 |
| Mid-market, heavy customisation | €200,000–600,000 |
The Technical Debt of Customisations
Every bespoke development added to the standard ERP creates recurring technical debt. Industry rule of thumb: every €10,000 of custom development generates €1,500 to €3,000 per year in maintenance cost (testing, adaptation during upgrades, documentation).
For an ERP that has accumulated €150,000 of custom developments over 3 years, the annual managed services cost attributable to customisations alone can reach €25,000 to €45,000.
5-Year TCO Comparison Table: 50-User SME
This table presents indicative ranges for a 50-user SME deploying an ERP covering finance, purchasing, and sales. Figures vary significantly depending on configuration, integrator, sector, and commercial negotiations.
| Cost item | Odoo Enterprise | SAP Business One Cloud | Dynamics 365 BC | Sage 100 Cloud |
|---|---|---|---|---|
| Licences Year 1 | €12,000 | €60–100k | €39–52k | €24–54k |
| Licences Years 2–5 (cumulative) | €36,000 | €180–300k | €117–156k | €72–162k |
| Implementation (one-off) | €40–80k | €80–200k | €60–150k | €50–120k |
| Data migration | €15–30k | €20–50k | €20–50k | €20–50k |
| Training and change management | €8–20k | €10–25k | €10–25k | €8–20k |
| Maintenance / managed services (5 yrs) | €20–40k | €30–80k | €20–50k | €25–60k |
| Internal resources | €50–100k | €80–150k | €70–130k | €60–110k |
| Total 5 years (range) | €181–318k | €460–905k | €336–613k | €259–576k |
Reading the table. Odoo delivers the lowest 5-year TCO thanks to its competitive licence pricing (€19.90/user/month on the Standard plan per odoo.com/pricing) and a lighter implementation footprint for standard scopes. SAP Business One offers deeper functionality for industrial SMEs with multi-currency or group reporting requirements, but at a significantly higher TCO. Dynamics 365 BC becomes compelling when the Microsoft ecosystem (Teams, Microsoft 365, Power BI) is already in place and bundle pricing applies.
5-Year TCO Comparison Table: 300-User Mid-Market Company
This table presents indicative ranges for a 300-user mid-market company, multi-site scope covering finance, purchasing, production, and distribution.
| Cost item | SAP S/4HANA Cloud | Oracle NetSuite | Dynamics 365 Finance | Sage X3 |
|---|---|---|---|---|
| Licences Year 1 | €720k–1.2M | €360–900k | €520–720k | €300–720k |
| Licences Years 2–5 (cumulative) | €2.2–3.6M | €1.1–2.7M | €1.6–2.2M | €900k–2.2M |
| Implementation (one-off) | €800k–2M | €500k–1.5M | €600k–1.5M | €400k–1.2M |
| Data migration | €100–300k | €80–250k | €80–250k | €80–250k |
| Training and change management | €80–200k | €60–150k | €60–150k | €50–130k |
| Maintenance / managed services (5 yrs) | €200–500k | €150–400k | €150–400k | €100–300k |
| Internal resources | €400–800k | €300–600k | €300–600k | €250–500k |
| Total 5 years (range) | €4.5–8.6M | €2.5–6.5M | €3.3–5.8M | €2.1–5.3M |
Reading the table. For mid-market companies, the gap between vendors is considerable and the ranges wide. SAP S/4HANA sits at the top of the market but offers the broadest functional coverage for international groups and regulated industries. Oracle NetSuite is frequently chosen for its cloud-native maturity and rapid multi-country deployment. Sage X3 remains competitive for industrial mid-market companies that want a proven vendor with a dense regional integrator network.
How to Present TCO to Your Executive Committee
Recommended Presentation Template
An effective TCO presentation for the executive committee articulates three dimensions:
- 5-year TCO: the tables above, with a realistic and pessimistic range for each option under evaluation
- Expected ROI: productivity gains, resource savings, error reduction, real-time data access
- Cost of inaction: what it costs to stay on the current system (legacy maintenance, regulatory risk, growth bottleneck)
The third dimension is often absent from presentations, yet it is frequently the most convincing. An ageing ERP that is not maintained also has a growing TCO: dated infrastructure, scarce internal skills, regulatory compliance risks (e-invoicing mandates, GDPR, sector-specific reporting).
For a structured ROI calculation method, see our complete ERP project ROI guide.
How to Answer “But Competitor X Is Cheaper”
Comparing on licence cost alone is the single biggest trap in ERP decisions. When a peer tells you they chose a solution “twice as cheap”, ask three questions:
- Over what time horizon were they comparing? (1 year vs. 5 years)
- Did they include internal resources and the go-live productivity dip?
- What is their actual functional scope versus yours?
In most cases, the comparison is not done on the same basis. A 5-year TCO puts solutions on a level playing field.
Including the Cost of Inaction in the Business Case
Staying on an ageing system has a cost that is rarely quantified. Factor it into your business case:
- Legacy maintenance costs: older systems carry growing support costs (scarce skills, unmaintained versions)
- Regulatory risk: mandatory e-invoicing, GDPR evolutions, and sector-specific reporting requirements can render a legacy system non-compliant
- Opportunity cost: manual processes block growth (new country, new entity, acquisition integration)
3 Fatal Mistakes in TCO Calculation
Mistake 1: Forgetting Dedicated Internal Staff
The “internal resources” line never appears on integrator quotes. Yet it represents 15 to 25% of the total 5-year TCO. Do not estimate it at zero because no one has invoiced it to you: every hour your CIO or CFO spends in project meetings has a real opportunity cost.
Mistake 2: Underestimating Data Migration
“Our data is in Excel and in our legacy system — it should be fine.” This sentence typically precedes the largest overruns. Data cleansing mobilises business resources (not just IT) over timelines that are often incompatible with the original project schedule. Systematically budget a data quality audit phase before signing anything.
Mistake 3: Not Budgeting Post-Go-Live Functional Evolution
In most decision-makers’ minds, the project ends at go-live. The reality is that the 12 to 24 months after go-live systematically generate evolution requests: adjusted processes, new reports, additional integrations. If you have not provisioned a managed services and evolution budget for years 2 and 3, these requests will either be blocked (business frustration) or funded as emergency spend outside the budget.
To deepen your analysis before signing a contract, see our guide on ERP vendor lock-in risk and exit clauses, which details what to negotiate to preserve your long-term autonomy. For detailed vendor comparisons, our Odoo vs. SAP vs. NetSuite analysis benchmarks the functionality and market positioning of these three key players.
