ERP Implementation Failure Case Studies, Stories & Examples

Updated July 2026.

ERP implementation failure is common in large, complex rollouts — independent studies put the failure or overrun rate at roughly 50–75%. The most costly documented failures include Lidl (a SAP programme abandoned in 2018 after seven years and around €500M), Hershey (over $100M in unfilled orders after a rushed 1999 go-live), Nike ($100M in lost sales in 2000), and Revlon ($64M in lost sales after a 2018 SAP cutover). The recurring root causes — rushed timelines, weak testing, poor change management, and wrong-vendor fit — are all avoidable.

This page brings together the best-documented ERP implementation failures and successes in one structured, vendor-neutral resource, with named companies, dates, dollar figures, and the specific lesson each project teaches. Use it to pressure-test your own programme plan before you sign a contract.

ERP implementation failure case studies (comparison table)

The failures below are among the most thoroughly documented in ERP history. Figures are as publicly reported or estimated in press coverage, court filings, and analyst commentary; treat them as directional rather than audited.

ERP implementation failure rate and statistics

How often do ERP projects actually fail? The honest answer is that it depends entirely on the definition. Outright abandonment — walking away from the software as Lidl and LeasePlan did — is relatively rare, in the low single-digit to low-teens percent range. But "failure" measured as missing the original budget, timeline, or expected benefits is far more common:

• Budget overrun: Panorama Consulting and Gartner surveys have repeatedly found that 50–75% of ERP projects exceed their original budget.
• Schedule overrun: a majority of programmes run longer than planned, with large enterprise rollouts among the most likely to slip.
• Benefit shortfall: a significant share of organisations report receiving less than half of the business benefits they expected.

The practical takeaway is not that ERP is doomed — thousands of companies run it successfully — but that overrun is the statistical baseline, so realistic budgeting, contingency, and phased delivery should be planned from the outset rather than treated as worst-case scenarios. Benchmark your own numbers against the ERP implementation cost breakdown before you commit.

The most famous ERP failures, in detail

Hershey (1999) — the go-live timing disaster

Hershey attempted a big-bang cutover of SAP R/3, Manugistics, and Siebel CRM simultaneously, compressing a planned four-year rollout into roughly 30 months to hit a Y2K deadline. The go-live landed in the summer of 1999, right before its highest-volume Halloween and Christmas seasons. Order-processing and fulfilment broke down, and Hershey could not deliver $100M+ of confirmed candy orders despite having inventory in the warehouse. Quarterly profits fell around 19%. Lesson: never go live during peak season, and phase a rollout rather than switching everything on at once.

Nike (2000) — testing and forecasting failure

Nike's problems stemmed largely from an i2 demand-planning deployment (alongside its wider SAP programme). Inadequate testing and over-reliance on automated forecasts caused the system to order too much of some shoes and too little of others. Nike publicly attributed roughly $100M in lost sales to the supply-chain snags, and its share price fell about 20%. Nike stuck with the vendor, fixed the process, and eventually recovered — a reminder that failure is survivable. Lesson: test rigorously and keep humans in the loop on algorithmic forecasts.

Lidl (2011–2018) — the €500M process mismatch

Lidl spent seven years and a reported ~€500M building a SAP-based merchandise system (eLWIS) before scrapping it in 2018. A core issue: Lidl's long-standing practice of valuing inventory at the price it paid clashed with SAP's standard model of valuing stock at retail price. Rather than adapt its processes, Lidl tried to bend the software — and leadership churn compounded the problem. Lesson: adapt your processes to proven standard software, or accept the cost and risk of heavy customisation up front.

Revlon (2018) — the cutover that hit the shelves

Revlon's 2018 SAP S/4HANA rollout at a North Carolina facility disrupted manufacturing so badly that the company could not fulfil orders. Revlon reported around $64M in lost net sales, its stock fell nearly 7% in a day, and shareholders filed suit. Lesson: manufacturing and distribution cutovers need parallel-run safety nets and realistic hypercare capacity.

National Grid (2012) — go-live meets a hurricane

National Grid's US arm went live on SAP just days before Hurricane Sandy struck. Data and configuration problems broke payroll, vendor payments, and financial reporting; the utility relied on temporary staff and manual workarounds for months. Total remediation and losses were later estimated as high as $585M. Lesson: control your go-live timing and have a tested contingency plan for the hypercare window.

Waste Management, MillerCoors & LeasePlan — when programmes collapse

Waste Management's SAP dispute (2005–08) ended in litigation exceeding $100M, each side blaming the other for an unworkable outcome. MillerCoors sued its systems integrator for $100M in 2014 after a post-merger consolidation stalled. LeasePlan wrote off roughly €100M when its "Core" platform proved far more complex than scoped. Lesson: contracts, governance, and a realistic scope matter as much as the software itself.

ERP implementation success stories

Failures dominate headlines, but well-run ERP programmes deliver real returns. These examples show what "good" looks like.

• Cadbury — after the confectionery giant's earlier rollout struggles, its disciplined later SAP programme is frequently cited as a turnaround: phased deployment, strong governance, and heavy user training restored supply-chain control.
• Nestlé USA — its multi-year "BEST" SAP standardisation, after an early misstep, ultimately consolidated fragmented divisions onto common processes and reported hundreds of millions in savings. Its own lesson: treat ERP as a business-change programme, not an IT project.
• Fulton & Roark — a men's grooming SMB replaced spreadsheets with NetSuite, gaining real-time inventory and financial visibility that let it double year-over-year growth without adding headcount.
• Discover Financial Services — used a phased ERP modernisation to standardise finance operations and improve reporting speed, a common pattern in successful large-enterprise rollouts.

What separates these outcomes from the failures above is rarely the software brand — several used the same SAP or NetSuite platforms that appear in the failure column. The difference is execution. Successful programmes tend to share five habits: they invest heavily in requirements and process design before configuration; they migrate a clean, reconciled data set rather than dumping legacy records; they phase the go-live by site or module instead of switching everything on at once; they schedule cutover away from peak trading periods; and they fund change management and training as a first-class workstream rather than an afterthought.

The through-line in every success story is the mirror image of the failures: realistic timelines, phased go-lives, clean data, executive sponsorship, and serious investment in training and change management. For a structured way to capture what "good" requires for your business, start with a documented ERP functional requirements list and a defensible ERP selection criteria framework.

Common causes of ERP implementation failure

Across every case study above, the same failure modes recur. Tag your own risk register against these five.

1. Data migration and data quality. Garbage-in migrations (Lidl's valuation mismatch, Target Canada's broken master data) are among the most common killers. Assess and cleanse source data early — it is far cheaper than fixing it during UAT.
2. Scope creep and over-customisation. Bending standard software to legacy processes multiplies cost, testing effort, and upgrade risk. Adopt standard functionality wherever the business can flex.
3. Change management and user adoption. Systems that users reject fail regardless of technical quality. Invest in training, communication, and super-users from day one.
4. Inadequate testing. Nike's forecasting errors and National Grid's payroll break both trace to insufficient testing. Budget for end-to-end and peak-load testing, not just unit tests.
5. Weak executive sponsorship and timing. Hershey's peak-season go-live and National Grid's hurricane timing show that governance and go-live scheduling are executive responsibilities, not IT afterthoughts.

For a deeper analysis of the underlying reasons, see our companion guide on why ERP projects fail. To keep these mistakes out of your own programme, work through the ERP implementation checklist and budget realistically with the ERP implementation cost breakdown.

How to avoid becoming a case study

The companies above were not careless — they were large, well-resourced organisations that underestimated the discipline ERP demands. The protective pattern is consistent: define detailed requirements before you shortlist vendors, choose software whose standard processes fit your business, migrate clean data, test end to end, phase your go-live away from peak periods, and fund change management properly. Every dollar spent on rigorous requirements and selection up front is cheaper than a nine-figure remediation later.

Don't become the next ERP failure case study. Build a documented requirements checklist and a vendor-neutral selection framework before you talk to a single salesperson.

Start the ERP Requirements Wizard Define your functional requirements Compare ERP systems side by side

Frequently Asked Questions

Why do ERP implementations fail?

ERP implementations fail mainly because of organisational and planning issues rather than the software itself. The most common causes are poor data migration and data quality, scope creep and excessive customisation, weak change management and low user adoption, inadequate testing, and poor go-live timing or executive sponsorship. In almost every famous failure — Hershey, Nike, Lidl, Revlon — the technology worked, but the surrounding process, testing, or timing did not.

What percentage of ERP implementations fail?

Independent research consistently puts ERP failure or significant overrun rates at roughly 50–75%, depending on how "failure" is defined. Studies from Panorama Consulting and Gartner have long found that a majority of projects exceed their original budget, timeline, or expected benefits. Outright abandonment (as with Lidl or LeasePlan) is rarer, but budget and schedule overruns are the norm rather than the exception.

What is the most famous ERP failure?

Hershey's 1999 SAP implementation is the most frequently cited ERP failure. A rushed big-bang go-live just before the Halloween and Christmas seasons broke order fulfilment, leaving over $100M of confirmed orders undelivered and cutting quarterly profit by around 19%. Nike's 2000 supply-chain failure and Lidl's ~€500M abandoned SAP programme are the other two most-cited examples.

How much did Nike's ERP failure cost?

Nike attributed roughly $100M in lost sales to problems with its i2 demand-planning deployment in 2000, and its share price fell about 20% at the time. The root causes were inadequate testing and over-reliance on the system's automated demand forecasts, which led to over-ordering some products and under-ordering others. Nike kept the vendor, fixed the process, and recovered over the following years.

Can you recover from a failed ERP implementation?

Yes. Nike, Cadbury, and Nestlé all recovered from early ERP setbacks and went on to run successful programmes. Recovery usually requires a hard reset: stabilise the business with manual workarounds, run an independent root-cause review, re-scope realistically, fix data quality, strengthen governance and testing, and re-plan the go-live in phases. The key is to treat the relaunch as a business-change programme with executive ownership, not a technical patch.

What are examples of successful ERP implementations?

Well-documented ERP successes include Cadbury's disciplined phased SAP rollout, Nestlé USA's "BEST" standardisation programme, and SMB wins such as Fulton & Roark's move to NetSuite, which let it double growth without adding staff. The common factors are realistic timelines, phased go-lives, clean data migration, strong executive sponsorship, and heavy investment in training and change management — the mirror image of what causes failures.