Why ERP Implementations Fail and the five causes you can control
Why ERP implementations fail: the failure rate depends on how you define failure. See the five causes you control and what to write into the contract.
Key takeaways
- Fine print: Gartner forecasts and Prosci 2025 study as published by each firm; Panorama 2026 ERP Report (170 respondents); Info-Tech ERP strategy research. Several of these firms sell ERP advisory or change management services.
- Waste Management (settled around 2010): SAP.
- It depends on what you count as failure.
- Godlan’s 2026 compilation of discrete-manufacturing projects ranks the drivers as inadequate change management (about 42%), poor data migration (about 38%), inexperienced implementation teams (about 35%), lack of executive sponsorship (about 31%), scope creep (about 26%) and over-customization (about 23%).
How many ERP implementations fail?
It depends on what you count as failure. Gartner predicts that by 2027 more than 70% of recently implemented ERP initiatives will fail to fully meet their original business case goals, and as many as 25% will fail catastrophically. Prosci’s 2025 study counts failure as delivering under 70% of expected benefits, and finds that happens 11% to 31% of the time, about 1 in 5 on average.
Both can be true at once. A project can go live on time and still miss the business case, and a project can run late and still deliver most of the value. Ask which definition a statistic uses before you quote it to your board.
Cost and schedule are a third measure. Panorama’s 2026 ERP Report found that more than a quarter of organizations were over budget and almost a quarter over schedule, and Info-Tech reports roughly 55% over budget. Across all of these studies, most disappointments trace to delivery and adoption, not to the software.
- Fine print: Gartner forecasts and Prosci 2025 study as published by each firm; Panorama 2026 ERP Report (170 respondents); Info-Tech ERP strategy research. Several of these firms sell ERP advisory or change management services.
| Definition | Source | Reported rate | What it measures |
|---|---|---|---|
| Business-case miss | Gartner | More than 70% miss goals; up to 25% catastrophic | Did the program deliver the original business case? |
| Benefits miss | Prosci 2025 | 11% to 31% deliver under 70% of expected benefits | Did the organization capture the promised value after go-live? |
| Budget or schedule overrun | Panorama 2026; Info-Tech | Over a quarter over budget, almost a quarter late (Panorama); about 55% over budget (Info-Tech) | Did the project hit planned cost and time? |
The five causes that matter for a 20 to 100 person company
Godlan’s 2026 compilation of discrete-manufacturing projects ranks the drivers as inadequate change management (about 42%), poor data migration (about 38%), inexperienced implementation teams (about 35%), lack of executive sponsorship (about 31%), scope creep (about 26%) and over-customization (about 23%). Treat those shares as directional, since they come from complex manufacturing and a firm with a commercial interest. An academic review of 55 studies (Rajapakse and Thushara, 2023) puts lack of top management support first, so the list is consistent across sources. Each cause below gives the symptom, the cost and what the partner contract should say.
1. Adoption was nobody’s job
Symptom: staff keep Excel workarounds and call go-live "IT’s project". Cost: you pay for a system whose reports nobody trusts, and the business case quietly stalls. Contract: change management is a named workstream with an owner, role-based training waves before go-live and an adoption measure reviewed after launch.
2. Data migration was left to the last month
Symptom: duplicate customers, orphaned items and balances that do not tie out on day one. Cost: users lose trust in the first reports and go back to spreadsheets. Contract: a named data owner per domain, a cleanse before cutover, a trial migration you can inspect, and migrated balances that you check and sign off before anyone relies on them.
3. The delivery team changed after the sale
Symptom: senior people demo the system, then junior staff configure it. Cost: rework, slipping dates and a partner who needs the project to keep running. Contract: the lead consultant is named in the statement of work, replacements need your approval, and you speak to references of similar size before you sign.
4. The sponsor signed and disappeared
Symptom: open decisions pile up, departments argue about process and nobody enforces the new way of working. Cost: a stalled schedule and a project that drifts back to old habits. Contract: a named sponsor with budget authority, a standing steering meeting, and a rule that decisions are due within a set number of days.
5. Scope and customization grew without a decision
Symptom: every department adds must-haves mid-build, and custom code appears for processes that do not set you apart. Cost: overruns, fragile upgrades and dependence on one developer. Contract: configure first, customize only where the business case pays for it, and route every change through a written change request with a price and owner.
Four ways a failing project shows itself
Failure appears as a budget overrun, a timeline slip, shadow spreadsheets after go-live, or benefits that never arrive. The Hershey case is the classic timeline slip: a recommended 48-month program compressed to about 30 months, with cutover timed against the peak season and training cut short. The warning signs are covered in detail in ERP project warning signs; the cost of each is in the section on what failure costs below.
The change management budget gap
Prosci reports that projects with excellent change management met or exceeded objectives 88% of the time, against about 13% with poor change management, and that most organizations spend roughly 92% of an ERP budget on technical work and about 8% on change management. If your budget shows the same split, fund the people side before you sign. The full design of that workstream is in the ERP change management guide.
Where Microsoft Dynamics 365 implementations break
Dynamics 365 failures trace to partner execution and governance more often than to the platform. Metcash, the Australian wholesaler, saw its Dynamics 365 program (Project Horizon) grow from an $80 million budget to a reported $290 million, with completion slipping from December 2023 to 2025 or later. A management review reportedly found flaws in the governance of the project.
ScanSource sued Avanade in 2013 over a Dynamics AX project estimated at about $17 million over 11 months that was projected to grow to nearly $66 million over three years, and it was still not live when ScanSource filed suit. The complaint cited about 500,000 lines of custom code. Adding consultants did not speed delivery when scope and customization were uncontrolled.
Two technical areas deserve a line in your contract. Dual-write between Finance and Operations apps and Dataverse has extensive official troubleshooting documentation from Microsoft, so ask who owns its configuration and testing. Microsoft’s FastTrack and Success by Design program supplies architects and checklists to eligible customers, but it is designed to support an implementation partner, not replace one. Lifecycle detail is in the ERP implementation guide.
Where Odoo implementations break
Odoo is modular and popular with smaller companies, so failures tend to come from customization overload and uneven partner quality, not from nine-figure overruns. Heavy custom code outside the standard framework creates fragile modules and painful upgrades. Ekofluid GmbH in Austria is a documented case: a first implementation failed on broken customizations and near-zero adoption, and a later standardized Odoo v17 rollout by Portcities fixed it.
The Community Edition and the free plan are free in license only. Community needs self-hosting, developers and carries no official support, so the total cost is higher than the price suggests. No independent research gives an Odoo-specific failure rate, and most public evidence comes from rescue providers with a commercial interest, so read these patterns as consistently reported, not proven. For a contract, ask for standard modules first, a written list of every customization with an owner, and an upgrade plan.
Famous failures that are not Dynamics or Odoo
Much ERP failure content attaches the wrong platform to a famous case. Waste Management’s lawsuit (more than $100 million spent, settled out of court around 2010) involved SAP, as did Target Canada’s rushed rollout and National Grid’s US project. Hershey was an SAP-era program too. These are real lessons about timelines, testing and governance, but they are not evidence against Dynamics 365 or Odoo.
- Waste Management (settled around 2010): SAP.
- Target Canada: SAP ECC.
- National Grid US, with integrator Wipro: SAP.
- Hershey: SAP-era stack, timeline compression.
Readiness first
Many of the causes above are fixed before a contract is signed: process maturity, data quality, internal time and a sponsor with authority decide most of the outcome. A free discovery call checks those four areas before you spend on a partner, so this guide does not repeat the checklist.
What to put in the partner contract
Fix scope in phases with a price each
Ask for a defined scope and price for each phase, with a first phase that delivers a working part of the system. Panorama advises an executive steering committee that sets the digital strategy, so name one before kickoff.
Put data migration and acceptance testing in writing
List who cleanses data, how many trial migrations run, and who signs off migrated balances and user acceptance tests. Do not let testing shrink when the date moves.
Name the team and the references
Require the lead consultant by name, approval rights over replacements, and references from companies of your size. Run scripted process demos, not generic ones.
Limit customization and keep a register
Configure first. Record every custom item with a business owner and the return that justifies it.
Fund the weeks after go-live
Prosci notes that organizations treating go-live as the finish line misjudge when ERP value arrives. Plan hypercare, super-users and adoption measures for the weeks after cutover, and agree in writing how long the partner stays.
If your project is already failing
Five questions tell you how deep the problem goes. Do users still run parallel spreadsheets? Can the finance lead tie migrated balances to the old ledger? Has the lead consultant changed since the sale? Is the scope document still the one you signed, or has it drifted through undocumented changes? Is a named sponsor attending steering meetings?
If the answers point to data and adoption, pause new features, fix the data and retrain by role before spending more on build. If they point to scope and team, a restart of the plan with a written scope and a new fixed-price phase is usually cheaper than continuing a drifting contract. Our guide to taking over a failed ERP implementation walks through the decision, and how to choose an ERP implementation partner covers the replacement.
What failure costs
The public record gives scale, not a price list for a 20 to 100 person company. Metcash reportedly overran an $80 million budget by about $200 million, and ScanSource’s estimate grew about fourfold. At smaller scale the same pattern shows as extra months of paid consultants, a second round of data cleanup and a team that stops using the system. Panorama’s 2026 report found that the leading cause of overruns was an unexpected need for additional technology.
For planned figures, see the ERP implementation cost guide and the total cost of ownership guide, then compare them against the phases in ERP implementation phases.
How Flectic can help
Flectic implements Odoo or Dynamics 365 for companies of 20 to 100 people in the US and Canada, led by a named senior consultant through five stages you approve. Each phase has a defined scope and price before it starts, and the first one delivers a working part of the system. That answers causes 3 and 5 above directly, and our ERP implementation service has you check migrated balances before anyone relies on them. Book a free discovery call.
Sources
Gartner predicts that by 2027, more than 70% of recently implemented ERP initiatives will fail to fully meet their original business case goals, and as many as 25% will fail catastrophically.
gartner.comChecked Gartner public ERP topic page; exact wording confirmed via Gartner's insights page on disappointing ERP initiatives (denis torii research).Prosci’s 2025 ERP implementation research study: human factors matter 6x more than technical factors; ERP 'failure' (deliver <70% of expected benefits) occurs 11 to 31% of the time (~1 in 5 average); People/Change Management was the top (36%) recommendation category.
prosci.comChecked Prosci blog published April 17, 2026 summarizing the 2025 ERP implementation research study; white paper at prosci.com/erp-implementation-research-white-paper.Prosci research found that projects with excellent change management met or exceeded objectives 88% of the time versus about 13% with poor change management, making excellent change management approximately 7x more likely to deliver project success.
prosci.comChecked Prosci-published correlation between change management effectiveness and project success; exact 88%/13%/7x figures confirmed. Scope is general projects, not ERP-specific data collection.Prosci reports that most organizations allocate roughly 92% of ERP budget to technical activities and only about 8% to change management.
prosci.comChecked Prosci blog on ERP investment allocation citing Best Practices in Change Management; commercial interest noted (Prosci sells change management services).Panorama Consulting's 2026 ERP Report found that more than a quarter of organizations reported their ERP project was over budget (leading cause: unexpected need for additional technology) and almost a quarter were over schedule (leading cause: organizational issues).
4439340.fs1.hubspotusercontent-na1.netChecked Primary PDF of Panorama Consulting Group's 2026 ERP Report (170 respondents, data collected Jan 2025 to Jan 2026); figures cross-checked against Panorama announcement March 2026.Godlan 2026 discrete-manufacturing ERP failure statistics: ~68% industry / ~73% discrete objective-miss rates; root causes include inadequate change management (~42%), poor data migration (~38%), inexperienced teams (~35%), lack of executive sponsorship (~31%), insufficient training (~29%), scope creep (~26%), over-customization (~23%), vendor selection errors (~19%).
godlan.comChecked Godlan Learning Center page (Infor partner, commercial interest noted); cites Panorama 2026 ERP Report and internal compilation across 2,400+ discrete manufacturing implementations Sep 2025 to Jan 2026. Treat manufacturing rates as directional.Info-Tech Research Group states that roughly 55% of ERP projects reported being over budget, and two-thirds of organizations realized less than half of their anticipated benefits.
infotech.comChecked Info-Tech Research Group research blueprint on building an ERP strategy and roadmap; exact 'roughly 55%' / 'two-thirds' wording confirmed in executive summary.Panorama Consulting lists prioritizing technology over people first among eight ERP failure reasons, advises an executive steering committee, and says change management issues contributed to failure in each of the 30+ ERP lawsuits it has testified in or written reports for.
panorama-consulting.comChecked Panorama article fetched 2026-10-19; the article says it is often impossible to pinpoint one reason. Panorama sells ERP consulting.A 2023 systematic literature review (Rajapakse & Thushara, covering 55 articles 2000-2022) identified lack of top management support as the top critical failure factor for ERP implementations globally.
jbt.slj.infoChecked Peer-reviewed open-access article in Journal of Business and Technology (SLJOL), DOI 10.4038/jbt.v7i1.109; 55 articles and top-five failure factors confirmed verbatim.Hershey’s late-1990s ERP program compressed a recommended ~48-month timeline to ~30 months and went live ahead of peak Halloween/Christmas season with inadequate testing, classic timeline-compression failure (SAP-era stack, not D365/Odoo).
panorama-consulting.comChecked Panorama Consulting Hershey case write-up; timeline 48→30 months and peak-season cutover confirmed in Pemeco and other case analyses.Metcash's Project Horizon (Microsoft Dynamics 365) was reported to have grown from an $80M budget to about $290M, with completion slipping from December 2023 to 2025 or later; a management review reportedly found governance flaws.
technologyforyou.orgChecked Reported by Technology for You (syndicating AFR coverage, March 2024), seen in search results this session; the original $80M baseline is not confirmed (an earlier iTnews report put the first stage at $70M). Treat as reported.ScanSource sued Avanade in 2013 over a Dynamics AX project estimated at $17M over 11 months, later projected at nearly $66M over three years and not yet live, with 500,000 lines of custom code.
scansource.comChecked Official ScanSource press release, fetched 2026-10-19: $17M initial estimate, nearly $66M projected, about $37M spent to date, 500,000 lines of code.Microsoft maintains extensive official troubleshooting documentation for dual-write between Dynamics 365 Finance & Operations and Dataverse / Customer Engagement.
learn.microsoft.comChecked Microsoft Learn official documentation on dual-write troubleshooting.Microsoft's FastTrack (Success by Design) program provides architects, workshops, reviews, and checklists for eligible D365 customers but is designed to support, not replace, experienced implementation partners.
learn.microsoft.comChecked Microsoft Learn Success by Design framework page.Ekofluid GmbH's first Odoo implementation failed due to broken customizations, near-zero adoption, missing bilingual features, and daily operational failures; it was rescued by Portcities with a clean Odoo v17 standardization.
portcities.netChecked Portcities (Odoo partner) case study; commercial interest noted (rescue provider framing).The famous Waste Management vs SAP ERP lawsuit (over $100M spent, settled out of court around 2010) was an SAP implementation, not Dynamics/D365.
panorama-consulting.comChecked Panorama Consulting write-up of the Waste Management vs SAP ERP failure; SAP platform confirmed via Computerworld settlement reporting and SEC filings.
Frequently asked questions
What is the main reason ERP implementations fail?
People and process, not software. Panorama Consulting lists prioritizing technology over people first among eight failure reasons, and a 2023 review of 55 studies found lack of top management support to be the most-cited failure factor. Prosci’s 2025 study found that human factors matter six times more than technical factors for benefits.
What percentage of ERP projects fail?
It depends on the definition. Gartner predicts more than 70% will miss part of their business case by 2027, with up to 25% failing catastrophically. Prosci finds that 11% to 31% deliver under 70% of expected benefits, about 1 in 5 on average. Treat any single "75% fail" figure with caution unless it states its definition.
How many ERP implementations go over budget?
Panorama’s 2026 ERP Report found that more than a quarter of organizations were over budget and almost a quarter were over schedule. Info-Tech reports roughly 55% over budget. The gap comes from different samples and definitions.
Why do ERP systems fail after a successful go-live?
Go-live only proves the system runs. Failure afterward usually means shadow spreadsheets, untrusted migrated data, no super-user network and no reinforcement of new processes. Prosci counts this as a benefits miss: the project can hit its budget and date while the business case quietly dies.
Do Dynamics 365 and Odoo fail for the same reasons?
The root causes are similar: people, process, governance and customization. Dynamics 365 failures tend to involve partner execution and large-program governance, as in the Metcash case. Odoo failures center on customization overload, partner variance and the hidden costs of the self-hosted Community Edition.
How can a small company reduce the risk of ERP failure?
Complete a readiness review before choosing a vendor, fund change management as a workstream, and name the delivery team in the contract. Put data migration and acceptance testing in writing, configure before you customize, and agree in writing how long the partner stays after go-live.
Is the Waste Management ERP failure a Dynamics 365 case?
No. Waste Management, Target Canada and National Grid US were SAP implementations. Public Dynamics cases include Metcash in Australia and ScanSource's 2013 lawsuit against Avanade over a Dynamics AX project.