Infrastructure Modernization / Financial Services
TSB core banking migration disaster
TSB's migration of millions of customer accounts from Lloyds-hosted systems to Sabadell's platform failed publicly and immediately. Customers lost access, saw incorrect information, and the bank later faced heavy regulatory penalties tied to governance and outsourcing failures.
Why this failure matters
TSB's migration of millions of customer accounts from Lloyds-hosted systems to Sabadell's platform failed publicly and immediately. Customers lost access, saw incorrect information, and the bank later faced heavy regulatory penalties tied to governance and outsourcing failures.
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.
- 013 / 8 cases
weak governance
The migration programme was not organized and controlled adequately
Governance - 023 / 8 cases
vendor dependency
Operational risks from the third-party supplier arrangement were not managed well
Resource - 032 / 8 cases
legacy dependencies
Millions of customer accounts moved in one ambitious cutover
Technical - 041 / 8 cases
testing gaps
The bank was not ready to implement and run the new platform
Technical - 053 / 8 cases
late risk escalation
The programme carried high operational risk but resilience controls were inadequate
Governance
Evidence record
- Customers were locked out and in some cases saw other customers' accounts.
- Regulators tied the event to governance and outsourcing-risk failures.
- The bank paid customer redress and its CEO departed after the incident.
Good reference for migration, resilience, and third-party control risk.
Decision checklist
Actions derived from the normalized lessons in this approved record.
- 01strengthen testing and rollback plans
Treat resilience and continuity of service as first-order launch criteria
- 02retain in-house program expertise
Own outsourcing risk instead of assuming supplier readiness equals programme readiness
- 03pilot before full deployment
Control high-risk cutovers with stronger planning and governance
Questions answered
What happened in the TSB migration failure?
TSB migrated millions of customer accounts from Lloyds-hosted systems to Sabadell's platform in one ambitious cutover. The migration failed publicly and immediately: customers were locked out and in some cases saw other customers' accounts.
What did regulators find about the TSB failure?
Regulators tied the event to governance and outsourcing-risk failures. The migration programme was not organized and controlled adequately, and operational risks from the third-party supplier arrangement were not managed well.
What were the consequences for TSB?
The bank faced heavy regulatory penalties, paid customer redress, and its CEO departed after the incident.
Why did the TSB migration fail?
Weak programme governance, unmanaged vendor dependency, a single high-risk cutover of millions of accounts, and a bank that was not ready to implement and run the new platform.
What lessons does the TSB case teach about migrations?
Treat resilience and continuity of service as first-order launch criteria, own outsourcing risk instead of assuming supplier readiness equals programme readiness, and control high-risk cutovers with stronger planning, piloting, and governance.
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.