A contract can grant the bank an exit right without giving it an executable exit. The data may be exportable but unusable, the replacement provider may lack capacity, or the people who understand the service may work for the supplier being replaced. Exit testing should expose these practical dependencies before a strained relationship becomes a crisis.
For EU financial entities within scope, DORA Article 28(8) requires exit strategies for ICT services supporting critical or important functions, with documented plans that are sufficiently tested and periodically reviewed. UK firms should assess the PRA's SS2/21 and applicable rules. Its current November 2024 text addresses continuity and stressed and non-stressed exits for material outsourcing. On 15 November 2026, the published March 2026 version is future-effective in March 2027. These regimes have different scopes; “DORA compliant” is not a substitute for a UK assessment.
Define the service you must preserve
Begin with the business outcome, not the supplier name. Identify what customers and internal users need to continue receiving: access to accounts, payment processing, screening, reporting or another service. Map the data, interfaces, people, licences and downstream dependencies needed to produce that outcome.
Define acceptable operating conditions during transition. A replacement can be technically available but unable to process the expected volume or maintain essential controls. Document the minimum viable service, the expected degraded period and the controls that must remain effective. Keep recovery, temporary workaround and permanent migration distinct; they solve different problems.
Test the data, not just the export button
Obtain a representative export and attempt to use it in the destination environment. Check record completeness, identifiers, timestamps, attachments, audit history, retention labels and relationships between tables. Reconcile the export against a known source total. Include records that are closed, disputed, archived or subject to special handling.
For a compliance case-management system, a list of customer names is not an adequate migration. Investigators may also need historic decisions, supporting material and a reliable chronology. Determine which fields must remain searchable and which need restricted access. Test those requirements with the people who will use the migrated service.
Challenge replacement assumptions
Ask whether another supplier could onboard the bank under the scenario being tested. A market-wide outage can make spare capacity scarce. An existing framework contract may not cover the necessary volume, geography or data category. Bring procurement, legal, security, technology and business owners into the exercise early enough to change the plan.
Budget the overlap period. The bank may need to pay both providers while migrating data, validating interfaces and training users. Include internal resource constraints: the same specialist team may be responsible for several exits. A plan that assumes unlimited staff and instant procurement is a dependency statement disguised as a solution.
Run a bounded practical exercise
In a hypothetical test, a bank moves a controlled subset of screening cases to an alternative system. Basic records transfer successfully, but escalation history does not. The exercise reveals that the receiving team cannot explain why a previous decision was made.
The finding should trigger a data specification, an amended export process and a retest. It should also prompt consideration of whether current records are adequately retained. The bank need not create an uncontrolled live migration to learn this lesson; a carefully isolated test can demonstrate the critical failure safely.
Make the exit decision usable
Define who can activate the plan, what evidence they need and how the decision interacts with incident management and regulatory engagement. Distinguish a commercial exit over several months from a supplier failure requiring immediate continuity arrangements. Include fallback choices where the preferred destination cannot operate.
The closure evidence should show what was actually exercised, the scale achieved, the unresolved assumptions and the next test trigger. Report remaining limitations in service terms: for example, a backlog could exceed processing capacity for two days. This helps management decide whether to invest, diversify, renegotiate or constrain reliance on the arrangement. The useful result is an evidenced ability to move or sustain the service under defined conditions.

