In the world of enterprise resource planning, a successful implementation can streamline operations, improve efficiency, and deliver strong return on investment. When things go wrong, the consequences can be devastating. One of Europe’s largest city councils budgeted £20 million for an ERP transformation. By the time the dust settled, they had spent over £115 million, and the new system was unusable. This case study examines what went wrong, why it happened, and what other organizations can learn to avoid similar disasters.
Background: A £115 Million ERP Disaster
Birmingham City Council, the largest local authority in Europe, set out to replace its long-standing SAP system with Oracle Fusion. The original budget was £20 million. The actual cost ballooned to over £115 million, and after years of work, the system could not perform critical functions like running financials or completing audits.
This was not a single bad decision. It was a chain of compounding missteps that, in aggregate, produced one of the most expensive public-sector ERP failures in recent memory. The lessons are valuable for any organization, public or private, contemplating a major transformation.
The Risk of Replacing a Long-Established System
The council’s decision to replace a system that had been in place for over 20 years marked a significant shift. When you have been using a system for that long, replacing it is never just about swapping technologies. It involves uprooting deeply embedded processes, cultural norms, and organizational competencies that built up around the original system.
Oracle Fusion is a powerful platform, but it is fundamentally different from SAP in functionality, user interface, and underlying architecture. The transition was not a technical upgrade. It was a complete operational overhaul that required cultural change as much as technology change. That second layer of difficulty was underestimated from the start.
In our experience, organizations replacing long-established platforms consistently underestimate the cultural and process work that must accompany the technology change. The technology is the most visible part of the transformation, but it is rarely the hardest part.
Understanding Digital Maturity
Digital maturity refers to an organization’s ability to leverage modern technologies effectively. Organizations with high digital maturity typically have a culture of innovation, modern infrastructure, and the experience to absorb large technology changes. Organizations with low digital maturity face significantly greater challenges when adopting new systems, especially complex enterprise platforms.
The council’s long reliance on a heavily customized SAP system suggested lower digital maturity. Their entrenched processes and customized workflows likely made adapting to Oracle Fusion’s standard approach far more difficult than the project plan accounted for. A more gradual, carefully phased transition would have been more appropriate, but the original plan did not reflect that reality.
When we advise clients on ERP selection and implementation, assessing digital maturity is one of the first things we evaluate. It directly affects the realistic timeline, budget, and approach for the project.
The Crucial Role of Project Governance
Effective project governance requires clear leadership, well-defined roles, regular oversight, and active executive engagement. The council’s governance structure did not meet those standards.
One of the most telling signs of weak governance was that the CEO only became actively involved after the project had already gone off track. Executive leaders do not need to be involved in day-to-day project management, but they do need to set strategic direction, resolve scope conflicts, and ensure the project remains aligned with organizational priorities. The absence of that engagement at the start of the project allowed it to drift, and by the time leadership intervened, the cost of recovery had multiplied many times over.
In our experience, the strongest predictor of governance failure is not the documented structure on paper. It is the actual engagement of senior leadership in the project’s hardest decisions. Strong organizational change management requires that engagement from day one.
The Dangers of Customization
Customization is often presented as a way to tailor an ERP system to an organization’s unique needs. In practice, it is one of the largest risk factors in any implementation.
The council attempted to replicate their highly customized SAP environment within Oracle Fusion. This decision compounded complexity, extended timelines, and significantly increased costs. It also introduced fragility. Customized systems are harder to maintain, harder to upgrade, and harder to integrate with future technology investments.
Heavy customization is also frequently a symptom of something deeper: resistance to change. When organizations are deeply attached to their existing ways of working, they often try to bend the new system to fit old processes rather than embracing the new platform’s standard approach. This pattern leads to expensive customization that locks in legacy thinking instead of enabling transformation.
The discipline of preserving customization for genuine differentiators while adopting standard configuration for commodity processes is one of the most valuable habits in successful business process optimization.
Revising the Business Case Mid-Project
As the project progressed, the council repeatedly revised their business case, lowering expected benefits and increasing the budget. This is a clear warning sign in any transformation. Adjusting a business case mid-project usually indicates one of two things: the original estimates were unrealistic, or the project is encountering issues that fundamentally change the cost-benefit equation.
A realistic business case is the foundation of any successful ERP implementation. It should provide a clear understanding of costs, benefits, risks, and the operational disruption the project might cause. The fact that this council’s business case had to be revised so frequently suggests they did not have a firm grasp on these factors from the start, and that the original plan failed to account for the full impact of the changes they were undertaking.
Preparing for Operational Disruption
One of the most overlooked aspects of ERP implementation is what happens when things do not work as planned. What if the new system cannot close the books? What if payroll cannot run? What if orders cannot be processed? These are not hypothetical risks. They are very real possibilities that can devastate an organization if not planned for.
For the council, the inability to use the new system for essential functions like financial reporting and audits had far-reaching consequences. The disruption could have been mitigated with more thorough testing, more deliberate change management, and a more conservative approach to go-live timing. Organizations need to weigh the cost of additional preparation against the cost of operational disruption when making go-live decisions.
Lessons Learned: Avoiding ERP Disaster
This case is a stark reminder of the challenges associated with major ERP implementations, especially for large, complex organizations. The failure was not the result of a single mistake. It was a chain of compounding decisions that, individually, might have been recoverable, but together created an irreversible trajectory.
For other organizations contemplating an ERP journey, the lessons are clear:
1. Understand the Scope of the Change
Replacing a long-established system is not a technical upgrade. It is a complete operational and cultural transformation. Plan accordingly.
2. Assess Your Digital Maturity Honestly
Lower digital maturity means a longer, more complex, and costlier project. Recognize where your organization actually sits on the maturity curve and plan your transformation accordingly.
3. Prioritize Project Governance From Day One
Active executive engagement is not optional. Governance that exists on paper but not in practice is governance that will fail when it matters most.
4. Be Cautious With Customization
Excessive customization increases cost, complexity, and long-term risk. Adapt to the new system’s standard processes wherever possible. Reserve customization for genuine differentiators.
5. Prepare for Operational Disruption
Plan for the possibility that go-live will not go perfectly. Test rigorously, build contingency plans, and resist pressure to go live before the system is genuinely ready.
6. Plan Recovery Before You Need It
Even with the best planning, transformations sometimes go off track. Knowing how to recognize the warning signs early and how to mount a structured ERP project recovery can save organizations from the kind of catastrophic outcome the council experienced.
Questions We Hear Most
How Common Are Major ERP Failures Like This One?
More common than most organizations realize. Public failures like the Birmingham City Council case make headlines, but most failures happen quietly. Industry research consistently shows that 50 to 75% of ERP projects fail to meet their original objectives in some meaningful way. Most do not result in £100 million write-offs, but they do result in delayed value, scope cuts, and operational disruption that erode the original business case.
How Do You Avoid the Birmingham Council Pattern?
The single most important thing is honest pre-implementation planning. The council’s failure was not unforeseeable. Strong Phase Zero planning would have surfaced the digital maturity gap, the customization risks, and the governance weaknesses well before the project began consuming budget at scale. Most major failures are foreseeable, but only if someone is willing to look honestly at the conditions before the project starts.
Should Organizations Avoid Replacing Long-Established Systems?
No. Long-established systems eventually need replacement. The lesson is not to avoid replacement, but to approach it with realistic expectations about cost, complexity, and the cultural change required. Organizations that treat these projects as straightforward technology swaps consistently underestimate what they are taking on. Organizations that approach them as multi-year operational transformations with the right digital transformation discipline are far more likely to succeed.
If your organization is contemplating a major ERP replacement and wants guidance on de-risking the project, contact us at eric.kimberling@thirdstage-consulting.com.
Eric is recognized globally as a leading voice in digital transformation and ERP strategy. Over the past two decades, he has helped hundreds of organizations – including Nucor Steel, Fisher & Paykel Healthcare, Kodak, Coors, Boeing, and Duke Energy – define their technology roadmaps, modernize complex operations, and deliver real business value from large-scale transformation initiatives.
As Founder and CEO of Third Stage Consulting, Eric leads an independent, technology-agnostic advisory firm focused on helping clients navigate the shift from traditional ERP to more flexible, AI-enabled Digital Enterprise Operations (DEO) models. His work spans ERP selection, implementation quality assurance, organizational change, and operating model design across a wide range of industries and geographies.
Eric is also a prolific thought leader, known for his pragmatic takes on AI, cloud, and enterprise software trends, as well as his firm’s benchmark research and frameworks for de-risking transformation. He is dedicated to helping executive teams cut through vendor hype, make confident investment decisions, and successfully reach the “third stage” of their digital evolution.
