What the TSB Migration Still Teaches Banks About Transformation

In April 2018, the UK lender TSB moved its operations onto a new IT platform as part of its separation from Lloyds Banking Group. The data itself migrated successfully. The platform did not hold up. Branch, telephone, online and mobile banking were all affected, and a significant share of TSB's 5.2 million account holders ran into problems.

The bank did not return to normal operations until December 2018. TSB paid £32.7 million in compensation, and in December 2022 the Financial Conduct Authority and the Prudential Regulation Authority fined it a combined £48.65 million. The regulators found that TSB had failed to organise and control the migration adequately, and that it had failed to manage the operational risks arising from its outsourcing arrangements.

Eight years later, the case is still worth studying closely. Why? Because most of the failures came down to planning, governance and risk decisions that any bank could make again.

Moving Data Is Only Part of Moving a Bank

The detail that the data migrated successfully is easy to skip past. It shouldn't be. It shows that a transformation program can hit its technical milestones and still let down the people it exists to serve. A migration plan that tracks records moved and test cases passed can look green right up to the moment account holders try to log in.

So the more useful question for any program is whether the bank can still serve its account holders on the first day, under real load, across every channel. That is a harder test to design. It is also the one that decides whether the program succeeded.

Third Parties Do Not Carry the Accountability

TSB relied on a critical third-party supplier for the migration. The regulators found fault with how the bank managed that relationship. In 2023, the PRA separately fined TSB's former chief information officer for failing to take reasonable steps to oversee the outsourcing arrangement.

This is an uncomfortable point for many banks, because so much transformation work is now delivered through partners. A bank can hand the build to a supplier, but supervisors will still hold the bank responsible for what happens to its account holders. Boards need evidence that a supplier is ready. Assurances are not enough.

Concentrated Risk Needs a Way Back

Any cutover that moves everything at once concentrates the risk into a very short window. Phased approaches take longer and cost more to run, because old and new systems have to operate side by side for a while. But they let a bank find problems with a small group of users before those problems reach millions.

Where a single cutover is unavoidable, the rollback plan deserves as much attention as the go-live plan. Who decides to reverse the change, and on what evidence? If that question has no clear answer before the weekend starts, it will not get a good one during it.

What This Means for Transformation Work Today

Most banks are in the middle of some kind of change, whether that means moving workloads to the cloud, replacing a core banking system or rebuilding their digital channels. Sound digital transformation for financial services starts from the account holder and works backward. It asks what the bank must never stop doing during the change, and it plans the technology around that.

A few habits make a real difference. Test with production-scale volumes and realistic user behaviour, not tidy samples. Define rollback criteria before go-live and give a named person the authority to use them. Put supplier readiness under the same scrutiny as internal readiness. And report progress to the board in terms of service risk rather than delivery milestones alone.

The final notices from both regulators are public documents. They make better reading for a transformation steering committee than most slide decks do.

Author - Shefali Vasave

Shefali manages content marketing at Opus Technologies, a domain-native engineering partner for banks, payment providers, and fintechs, and writes on the various aspects of financial institutions navigating change in a real-time, digital-first world.