The hook
There’s a deadline looming over every SAP shop: mainstream maintenance for Business Suite 7 core applications runs only through the end of 2027, with optional extended maintenance to 2030. That puts a wave of S/4HANA migrations and cutovers on the calendar. And according to Capgemini’s 2025–26 World Quality Report, 60% of organizations already struggle with secure, scalable test data — which is exactly the condition that turns a migration into a public failure.
What happened at TSB
In April 2018, TSB Bank’s platform migration became one of the best-documented cutover failures of the last decade. The FCA’s final notice records the pattern precisely: user acceptance testing ran on synthetic data, because a full and realistic population of customer accounts wasn’t available at that stage. Testing against actual migrated data
had to be pushed into a later, narrower window — and under time pressure, that migrated-data testing was “parallelised and compressed.” The result was serious, prolonged disruption across digital, telephone, and branch
services, followed by regulatory enforcement from both the FCA and the PRA. The official record never uses the phrase “test data management,” but the mechanism is unmistakable: the program reached the most dangerous stage of the cutover without stable, early access to representative migrated data at scale. Late-stage compressed testing is exactly where defects tied to real account structures — dormant accounts, offset mortgages, complex product bundles, historical exceptions — are hardest to find and costliest to fix.
Where Test Data Express changes the outcome
The failure here isn’t “not enough testing.” It’s the absence of the right data, in the right shape, at the right cadence. TDE addresses that directly:
- Extract referentially intact, privacy-safe migrated-account subsets before formal UAT, not after
- Mask personal data while preserving structural relationships and product logic.
- Generate replayable “cutover packs” for a fresh dress rehearsal after every major build.
- Reconcile source-platform vs. target-platform outcomes at the account level
- Automate repeated refreshes so each rehearsal runs on current data, not stale synthetic fixtures
Modeled benefit: roughly 30–50% less migrated-data preparation time, several additional dress-rehearsal cycles in the same calendar window, and — most importantly — defect discovery shifted left, before go-live rather than after it.
The takeaway
When a migration gets compressed, the margin between a safe cutover and a public failure is defect-detection timing. A managed test-data layer buys back that margin. For SAP teams staring down the 2027 deadline, that’s not a QA nicety — it’s cutover insurance.
Sources
- FCA — “TSB fined £48.65m for operational resilience failings” (press release):
- FCA — Final Notice to TSB Bank plc (full text, PDF):
- PRA / Bank of England — Final Notice to TSB Bank plc (PDF):
- Capgemini — World Quality Report 2025–26 (60% struggle with secure, scalable test data):
- SAP — Business Suite 7 maintenance strategy (mainstream through 2027; extended to 2030):
