ERP Implementation / Public Sector
Birmingham City Council Oracle ERP failure
Birmingham City Council replaced its long-standing SAP environment with Oracle Cloud in a programme that became a governance and execution failure. Costs more than doubled, critical finance functions remained impaired, and the council entered reimplementation while still dealing with operational fallout.
Why this failure matters
Birmingham City Council replaced its long-standing SAP environment with Oracle Cloud in a programme that became a governance and execution failure. Costs more than doubled, critical finance functions remained impaired, and the council entered reimplementation while still dealing with operational fallout.
Failure signals
Each signal is normalized against the approved case base. Recurrence is a deterministic count, not a claim that the cases share identical causes.
- 011 / 8 cases
skill gaps
Those governing the project lacked enough Oracle expertise to challenge implementation partners
Resource - 021 / 8 cases
excessive customization
The programme accepted extensive customizations late in the cycle
Technical - 034 / 8 cases
integration complexity
Integration and payroll issues required prolonged retesting
Technical - 043 / 8 cases
late risk escalation
Project managers did not report problems in a timely manner and bad news was unwelcome
Governance - 053 / 8 cases
vendor dependency
Heavy reliance on Oracle and consultants weakened internal control
Resource
Evidence record
- The cost expanded from roughly £39 million to around £90 million including reimplementation.
- Audit findings highlighted governance, expertise, and vendor-management failures.
- Core finance and payments functions were still not expected to work properly until years after launch.
Strong current ERP case for governance-expertise gap and late change-request risk.
Decision checklist
Actions derived from the normalized lessons in this approved record.
- 01retain in-house program expertise
Maintain enough internal expertise to act as an intelligent customer
- 02align process design before technology rollout
Protect adopt-not-adapt principles before customization accelerates
- 03match contracts and governance to delivery reality
Escalate bad news early and tie governance to technical reality
Questions answered
What happened in Birmingham City Council's Oracle programme?
The council replaced its long-standing SAP environment with Oracle Cloud ERP and HCM in a programme that became a governance and execution failure. Critical finance functions remained impaired and the council entered reimplementation while still dealing with operational fallout.
How much did the Birmingham Oracle failure cost?
Costs expanded from roughly £39 million to around £90 million including reimplementation, and core finance and payments functions were still not expected to work properly until years after launch.
Why did the Birmingham implementation fail?
Those governing the project lacked enough Oracle expertise to challenge implementation partners, extensive customizations were accepted late in the cycle, integration and payroll issues forced prolonged retesting, and project managers did not report problems in a timely manner because bad news was unwelcome.
What lessons does the Birmingham case teach?
Maintain enough internal expertise to act as an intelligent customer, protect adopt-not-adapt principles before customization accelerates, and escalate bad news early so governance stays tied to technical reality.
Source and method
This analysis uses the cited public source, controlled failure-signal and lessons taxonomies, and human approval. Cross-case comparisons are calculated only from approved, published records.