The Real Cost of a Bad ERP Implementation — and How to Avoid It
- Gartner estimates that 55–75% of ERP implementations run over budget. The average cost overrun for mid-market ERP is 40–60% above the original quote — typically because the original quote excluded data migration, staff training, and integration development.
- The most expensive implementation failures share a common pattern: the technical delivery was fine, but the business requirements were never properly defined. The system does what was built, not what the business needed.
- Three specific decisions account for the majority of implementation failures: insufficient data migration planning, customisation addiction (customising instead of adapting the business process), and underestimating the change management cost.
- The cheapest ERP decision is choosing not to implement until the business is ready — the costs of a bad implementation (re-implementation, morale damage, lost customer trust during transition) can exceed £500k for a mid-size operation.
ERP implementation horror stories are a genre. The £2 million SAP implementation that took 4 years and was never fully adopted. The NetSuite project that went live 18 months late and corrupted the financial data during migration. The Dynamics 365 rollout that cost three times the quote and resulted in key staff leaving. These are not outliers — they are representative of a market where failure is genuinely common. Understanding why helps avoid it.
The Three Implementation Killers
Every ERP implementation involves moving historical data from wherever it currently lives (spreadsheets, an old system, several disconnected tools) into the new system. This is not a technical problem — it is a data quality problem. Technical teams can write migration scripts. They cannot decide what to do with 12 years of customer records that have duplicate entries, inconsistent country codes, invalid email addresses, and missing tax IDs. That requires business decisions, and businesses consistently underinvest in making them before migration starts.
ERP systems encode opinionated processes. NetSuite has a way of handling purchase orders. It is not always the way your business currently handles purchase orders. The right answer is usually to adapt the business process to the ERP’s model — it is what the system is designed for. The expensive answer is to customise the ERP to replicate your existing process. Every customisation is a maintenance liability that must survive every ERP upgrade.
ERP implementations are change management projects that happen to involve software. The software is the easy part. Getting the finance team to stop using the spreadsheet they have used for 10 years, getting the warehouse staff to use a new pick-and-pack workflow, getting senior managers to trust the new system’s numbers — these are human problems. Implementations that treat change management as a one-day training session consistently underperform.
References
- Gartner ERP ResearchGartner — ERP implementation success rate research and cost overrun data.
- NetSuite ERP Implementation GuideOracle NetSuite — official implementation methodology and project planning guidance.
- Forrester ERP AnalysisForrester Research — enterprise application implementation research including failure mode analysis.
Leave a Reply