Back to the archive

The encyclopedia · Software & IT · Technical decision · 2018

TSB's 'big bang' IT migration locked 1.9 million customers out of their money for weeks

In April 2018 the UK bank TSB moved its customers to a new IT platform in one go. The migration failed catastrophically; 1.9 million customers were locked out.

TSB Bank · Sabadell · 2018-04-20

What happened

TSB is a British retail bank, owned since 2015 by Spain's Sabadell Group. For years after the acquisition, TSB's customers still ran on the IT platform of its former parent, Lloyds Banking Group. In 2018, Sabadell decided to move TSB onto its own banking system, Proteo — a migration of about 5.4 million customers and billions of records, attempted in a single 'big bang' cutover over one weekend in April 2018.

The migration went catastrophically wrong. Within hours, huge numbers of customers were locked out of online and mobile banking; the outage stretched into days, then weeks. Worse, some customers could see other customers' account details, including balances and transactions — a serious security and privacy failure. At its peak, about 1.9 million customers were affected, unable to access their money or make payments.

The fallout was severe. TSB's chief executive, Paul Pester, resigned in September 2018. The bank spent hundreds of millions of pounds on compensation, fixing the systems, and lost business, and it was fined by regulators. The episode became a textbook case of how not to run a critical IT migration: a high-risk, all-at-once cutover of a bank's core systems, with inadequate testing and no working fallback, turned a planned upgrade into a weeks-long crisis that locked customers out of their own money.

Why it happened

  • TSB attempted a high-risk 'big bang' migration of millions of customers and billions of records in a single cutover, rather than moving incrementally.
  • The new platform was not adequately tested at scale, and there was no working fallback when the cutover failed.
  • The migration exposed customers' data to other customers, a serious security and privacy failure that compounded the outage.
  • A bank's core systems are critical infrastructure; an all-at-once cutover with no rollback plan turned a planned upgrade into a crisis.
What it cost1.9M locked out; hundreds of £ millions; CEO outcostly

The lesson

Don't bet the bank — literally — on an untested, all-at-once cutover. TSB moved millions of customers to a new platform in one weekend, with no working fallback, and locked them out of their money.

Aftermath

The TSB migration is taught as a textbook case of how not to run a critical IT migration. It cost the bank hundreds of millions of pounds, its chief executive's job, and lasting damage to customer trust, and it prompted regulatory fines and scrutiny of how banks manage major technology changes. The lesson is durable: in critical systems, an incremental migration with a tested rollback is not caution — it is competence. A 'big bang' cutover of systems your customers depend on, with no way back, is a gamble you cannot afford to lose.

Sources

spotted an error? The club wants to know.

Comments · 0

    Sign in to join the comments.

    More like this

    Somewhere, someone solved the problem this company failed at. 2nd Opinion →