How to Calculate the Real Cost of an ERP Project
What does an ERP project really cost?
ERP cost is the sum of licence or subscription, configuration development, data migration, integration, training, the parallel-run period and post go-live support. In practice most of the budget is not the software itself but the effort required to move the data and settle the process into the new system. Comparing vendor quotes on the licence line alone is the most common cause of mid-project budget overrun.
The seven lines that make up the budget
Ask every vendor to quote each item as a separate line; a single total is not comparable.
- Licence or subscription: user type, concurrent versus named, annual increase rate.
- Configuration development: every non-standard screen, report and business rule. This line generates cost again at each version upgrade.
- Data migration: accounts, stock items, bills of material, open orders, open balances, historical transactions.
- Integration: bank, e-invoicing, shipping, marketplace, shop floor, time attendance. Each endpoint needs its own testing and reconciliation — see the [bank integration guide](/en/blog/bank-integration-guide) for that line in detail.
- Training and documentation: role-based training, user guides, transaction records.
- Parallel run: duplicate data entry effort while the old and new systems run together.
- Post go-live support: intensive correction in the first month, normalising maintenance afterwards.
Put internal effort in the budget
Most ERP budgets only contain what is paid externally. The hours key users spend in analysis workshops, data cleansing and testing are a real cost. A simple method: number of key users per department × hours committed per week × internal hourly cost. Writing this line down also makes scope decisions easier, because the price of each "extra module" request becomes visible.
Measure migration cost before you sign
Migration effort correlates with data quality, not record count. Take three measurements before contracting: the share of duplicate account records (how often does the same tax number appear?), the share of stock items with inconsistent unit of measure or product code, and the share of accounts whose open balance does not match its source document. If these ratios are high, the migration line will grow well beyond the first quote.
Also calculate the cost you avoid
Judging ERP only on the expense side is incomplete. Measurable items sit on the other side: accounting hours spent on reconciliations that will not close, stock count variance, delayed collection caused by late invoicing, and the time needed to prepare manual reports. Measure these before the project and repeat the same measurement three months after go-live. Without measurement there can be no claim of improvement.
Frequently asked questions
Which budget line is missed most often?
The parallel-run period. While the old and new systems operate together the same data is entered twice, the period usually lasts longer than planned, and all of it is internal effort.
Fixed price or time and materials?
Fixed price works for scope that has been analysed and signed off. For areas where analysis is incomplete, a fixed price produces either a high risk premium or a scope dispute. A common approach is to price the analysis separately and fix the development price after it.
How should cloud and on-premise costs be compared?
Compare over five years, including subscription increases, server refresh, backup, uninterruptible power, system administrator time and the disaster recovery scenario. A single-year comparison favours cloud; a five-year comparison depends on the workload.