Mon – Sat: 9:00 AM – 7:00 PM IST
ERP Basics

ERP total cost of ownership

The five-year number, including the lines that never appear in a vendor proposal.

In short

Total cost of ownership for an ERP covers licence or subscription, implementation, data migration, integration, infrastructure, training, support, upgrades and internal staff time, across a defined period — usually five years. The costs most often omitted are internal effort and upgrades, and they are rarely small.

Why It Matters

Why this matters in practice

Vendor proposals quote what the vendor sells. They do not include your people's time, the integration to systems the vendor does not supply, or the upgrade in year three. Comparing two options on proposal totals therefore compares two incomplete numbers, and the gap between them is not necessarily in the same place for both.

Five years exposes differences a first-year comparison hides
Internal effort is a real cost and usually the largest omission
Upgrades belong in the model, not as a future surprise
Makes licence-free and subscription options genuinely comparable
How It Works

How it works in practice

1

Software

Licence and maintenance, or subscription. For per-user models, project user growth across the period.

2

Implementation

Configuration, data migration, integration, testing and training. Normally the largest single line.

3

Infrastructure

Servers, storage, backup, disaster recovery and the environments for test and development — or the hosting that replaces them.

4

Internal effort

Your project team, the business time in workshops and UAT, and data cleansing. Omitted from almost every comparison.

5

Ongoing

Support, enhancements, upgrades and the internal administration the system needs each year.

Worked example

A worked example: a five-year model with the usual gaps closed

A hundred-user mid-market ERP decision, modelled over five years, has five cost lines and most comparisons include only the first two.

Licence or subscription is visible and negotiated hard. Implementation is quoted and scrutinised. Infrastructure is often omitted for on-premise and genuinely near zero for SaaS. Run cost — the administrator's time, the support contract, the internal super-users — is almost always omitted entirely, and over five years it is frequently comparable to the implementation cost. Upgrades are omitted on the assumption that they are included, which is true for SaaS and not for on-premise.

A model that includes all five, with the internal time costed at a realistic rate, usually produces a different ranking than the quoted-cost comparison. It also produces a more useful conversation, because the largest controllable line is often run cost, and that is affected by choices — how much customisation, how standard the processes, how well documented the system — made during implementation.

Key terms

The vocabulary, briefly

Term What it means
Licence or subscription The cost of the software right, recurring or perpetual.
Implementation Configuration, development, migration, testing and training.
Infrastructure Servers, storage, network, database and their refresh cycle.
Run cost Support, administration, and the internal time nobody budgets.
Upgrade cost The periodic cost of staying current, which on-premise is a project.
What Goes Wrong

Common mistakes worth avoiding

Ignoring internal time

Data cleansing and UAT are client work. Excluding them understates every option, and unevenly.

Comparing year one only

A low entry cost with a high subscription inverts over five years. Model the whole period.

Omitting upgrades

On-premise upgrades are projects with real cost. Cloud updates need regression testing each cycle.

Forgetting integration

Few ERPs stand alone. Interfaces to banking, eCommerce, payroll and carriers all cost to build and to maintain.

What to measure

Numbers worth tracking

Metric What it tells you What distorts it
Cost per user per year, fully loaded A comparable figure across options, once everything is included.
Implementation as a multiple of licence A high multiple signals heavy customisation and future maintenance.
Internal effort hours The cost treated as free, which over five years rarely is.
Cost of change requests after go-live Whether the system fits or is being continuously adjusted.
FAQ

Questions we are asked about this

Five years is the common convention and long enough to include at least one upgrade cycle. Shorter periods flatter options with low entry cost and high ongoing cost.
Usually yes, and the saving is concentrated in licensing rather than spread across the model. Implementation, integration and support cost broadly the same.
Three things consistently: data migration effort, internal staff time, and the cost of change after go-live. Migration is underestimated because the cleansing work is invisible until someone looks at the data. Internal time is underestimated because it is not invoiced. Post-go-live change is underestimated because the business case assumes the system is finished at go-live, which it never is.
Model both over the same realistic horizon, including everything: maintenance as a percentage of licence for the perpetual option, infrastructure and its refresh, administration effort, and upgrade projects. Then consider what the money is worth to you — capital preserved versus predictable operating cost. The arithmetic rarely produces a decisive gap, which means the decision usually turns on cash flow preference and risk appetite rather than on total cost.
It is worth stating even if it is not modelled precisely. The internal people assigned to an ERP implementation are usually your most capable operational staff, and whatever they would otherwise have been doing is not happening. Quantifying this is difficult and ignoring it entirely makes the project look cheaper than it is. Naming it keeps the conversation honest about what the business is actually committing.
Five years is standard and seven is more honest for on-premise, because it captures the infrastructure refresh and at least one major upgrade. Three-year models systematically favour options with high upfront and low ongoing cost, which is why vendors selling perpetual licences tend to propose them. Pick the horizon before seeing the quotes, so the choice of horizon is not itself part of the negotiation.
Related

Where to read next

Cloud vs on-premise ERP

Read more

How to choose an ERP

Read more

Open-source ERP cost and TCO

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.