Few technology programmes carry as much risk, or as much board attention, as an ERP implementation. They are expensive, they touch every part of the business, and when they go wrong they go wrong expensively and visibly. The uncomfortable truth is that a great many of them do go wrong: study after study finds that most ERP programmes overrun on time or budget, and a meaningful share fail to deliver what was promised at all. The named disasters, the retailers and manufacturers whose ERP failures made the headlines, are only the visible tip of a much larger pattern.
The more useful truth, and the one boards rarely hear, is that a failing ERP programme is almost always recoverable, and you rarely need to start again. This is a board-level guide to why these programmes fail, the warning signs to watch for, and how recovery actually works, whichever platform you are on.
Why ERP implementations fail
Strip away the platform and the failure modes are remarkably consistent. In my experience recovering these programmes, the same root causes appear again and again:
- Unclear or runaway scope. What began as an ERP rollout quietly becomes a business-wide transformation, without the budget, time or governance to match.
- Weak governance. No single accountable owner, a steering group that reviews slides rather than makes decisions, and a status report that is optimistic long after reality has diverged.
- Configuring the old world. The system is bent to mirror exactly how the business works today, including its broken processes, instead of adopting the platform's proven standard ways of working. On some platforms this shows up as runaway customisation that becomes a cost and upgrade millstone.
- Data left too late. Migration is treated as a technical task for the end, when it is almost always the single highest-risk item in the whole programme.
- An absent business. The people who will actually use the system are not engaged, testing is done by the project team, and nobody has genuinely signed off what good looks like.
- The wrong delivery setup. Sometimes the partner is not up to it. More often a capable partner has been set up to fail by everything above.
Notice what is not on that list: the software. ERP platforms, whether SAP, Oracle, Dynamics 365, NetSuite or others, are proven across thousands of businesses. Implementations fail for reasons of scope, governance, data and leadership, not code.
The warning signs your ERP programme is in trouble
If three or more of these are true, you have a programme that needs intervention, not reassurance: the go-live date has moved more than twice; the partner is billing steadily but working functionality is scarce; customisation or scope keeps growing; the business has disengaged from testing; data migration is an unknown; and no single person truly owns the outcome. Boards that act on these signals early recover far more cheaply than those that wait for the go-live to fail.
How to recover a failing ERP programme
Recovery is not mysterious, but it is disciplined. The same 90-day reset works across platforms.
In the first 30 days you establish the truth: an honest, independent assessment of where the programme actually stands, and a stabilised governance structure with a single owner and a re-baselined view of scope, cost and risk. In the next 30 days you rebuild the plan: re-anchor to a clear target operating model, adopt standard functionality wherever it is good enough, re-scope ruthlessly to a credible first release, and bring data migration forward as a first-class workstream. In the final 30 days you deliver: business-led testing, a go-live decision based on agreed criteria rather than a date, intensive hypercare, and a genuine handover so the business owns the system rather than renting the confidence to run it.
The other decision that surfaces in most recoveries is whether to change the implementation partner. The honest test is whether the partner is delivering poor-quality work, or competent work against a broken brief. Replacing a capable partner resets the clock for no gain; keeping a failing one repeats the mistake. That call should be made independently, in the business's interest.
Platform-specific rescue playbooks
The principles are universal, but the failure patterns and fixes have platform-specific detail. I have written focused 90-day recovery plans for the platforms I am most often called to rescue:
- Rescuing a struggling SAP or S/4HANA programme
- Recovering a failing NetSuite implementation
- Recovering a failing Dynamics 365 implementation
Whatever the platform, the pattern holds: stabilise, re-plan, deliver.
Frequently asked questions
What is the ERP implementation failure rate?
Industry studies consistently find that most ERP programmes overrun on time or budget, and a significant proportion fail to deliver the expected benefits. The exact figures vary by study and definition, but the direction is not in doubt: ERP failure and overrun is common, not rare.
Why do most ERP implementations fail?
Because of scope, governance, data and business engagement, not the software. Unclear scope, weak decision-making, configuring the system to mirror broken processes, late data migration and a disengaged business are the recurring causes.
Can a failed ERP implementation be recovered?
In the large majority of cases, yes, and without starting again. A disciplined 90-day reset with an honest baseline, a re-planned scope, and data brought forward is usually enough to return a stalled programme to delivery.
Should we change our ERP system or our partner?
Usually neither is the first answer. Most failing programmes are recoverable with the current system and often the current partner, once scope, governance and data are fixed. Change the system only when it is genuinely the wrong fit, and the partner only when quality is poor and trust has gone.
How long does ERP recovery take?
Stabilisation and re-planning are typically achievable in 30 to 60 days, with a controlled go-live inside 90. Larger, multi-entity programmes may need a longer second phase, but the recovery itself is fast because it is about discipline, not rebuilding.
Recover the programme, not just the system
A troubled ERP implementation is a governance and leadership problem wearing a technology costume. Solved in that order, the platform does exactly what you bought it for.
If your ERP programme has stalled and you need an experienced, independent pair of hands to get it back on track, book a confidential conversation. I have recovered failing ERP programmes across SAP S/4HANA, NetSuite, Dynamics 365 and Oracle, including for PE-backed businesses where time to value is everything.