Resources · 52
Portability: verify an exit from a digital supplier
Test export, reconstruction and continuity before contractual or technical dependencies make an exit impractical.
· 4 min
What this guide helps achieve
- Identify dependencies
- Test usable exports
- Estimate reconstruction
- Prepare a controlled cutover
Quick check
- What disappears without the supplier?
- Who can rebuild the service?
- Does export preserve relationships and rights?
- Which costs are absent from the initial quote?
- Can a failed cutover be reversed?
Step-by-step method
- 01
Define the service to preserve
List essential tasks and assets: data, attachments, configuration, automations and permissions. State what a replacement must deliver and what may temporarily operate in a degraded state.
Deliverable: exit scope.
- 02
Qualify dependency
Separate commercial commitment, proprietary formats, technical integration and skill shortages. GOV.UK recommends weighing service value against portability; avoiding every dependency is not always the best choice.
Deliverable: value and portability trade-off.
- 03
Test a representative export
Export authorised data including relationships, history and edge cases. Check format, encoding, identifiers and absence of secrets. Downloading a file does not prove it can be understood or imported.
Deliverable: export and completeness check.
- 04
Rebuild elsewhere
Import the sample in an isolated environment and execute an essential task. Record adaptations, metadata losses and manual steps. Include configuration and permissions, not just content.
Deliverable: replayed task and gaps.
- 05
Estimate and order the transition
Estimate extraction, transfer, parallel operation, training and support. Separate measured costs, quotes and assumptions. Set cutover order, change freeze and rollback if acceptance fails.
Deliverable: plan and cost assumptions.
- 06
Keep evidence current
Repeat after new integration or format changes. Check asset return and copy handling under the service’s applicable rules. An exit clause does not replace a technical demonstration.
Deliverable: schedule and exit dossier.
Four situations for testing the method
Fictional teaching cases. Each situation connects a signal, a check and a decision bounded by evidence; none represents a client outcome.
| Fictional situation | Concrete check | Decision and limit |
|---|---|---|
| Separate recurring value from avoidable dependency — An agency charges ongoing maintenance while the client does not know which accounts, domains and settings its own team can access. | Connect each recurring service to observable work and inventory access held by the client and provider. | Assess the service alongside ownership and continuity. A lasting relationship should also permit a documented handover to another team. |
| Exercise an exit clause — The agreement allows data recovery, but a supplied sample omits links between products, media and history. | Test reconstruction of a small authorised set in a separate environment. Record missing fields, identifiers and adaptations. | Specify the expected result, timescale and remediation owner. A written clause does not replace a verified recovery exercise. |
| Measure retention that preserves choice — A client renews after good support, but its domain and data remain managed through accounts it cannot control. | Separate satisfaction from exit barriers. Check administrative access, documentation and transfer of an authorised scope. | Improve support and transparency without making inaccessible assets the mechanism for retaining the relationship. |
| Plan how a recommendation will be handed over — A consultant recommends a new tool, but only one person knows how to change its rules or handle incidents. | Ask the future operating team to perform a small change and recovery scenario using the intended documentation. | Include skills, permissions and ownership in the recommendation. Resolve a blocked handover before expanding use. |
Reusable worksheet
Complete with your authorised observations. These fields are a working template, not observed results.
| Field | Information to record |
|---|---|
| Asset | Owner, volume and dependency |
| Export | Format, relationships, attachments and rights |
| Reconstruction | Tested task, result and gaps |
| Cutover | Costs, time, stop and rollback |
Worked example
Illustrative situation
Fictional example: a CRM exports contacts but omits attachment relationships.
Decision and expected evidence
Acceptance records the gap before cutover; extraction and attachment reconciliation are added rather than claiming readiness.
Distinguish the mechanisms
| Mechanism | Purpose | Check or limitation |
|---|---|---|
| Exit clause | Define commitments for review | Does not demonstrate technical continuity |
| Export | Retrieve assets | Check relationships and metadata |
| Tested reconstruction | Demonstrate use elsewhere | Document lost functions |
Management indicators
| Indicator | What it measures | First action |
|---|---|---|
| Exportable assets | Critical assets retrieved and readable | Address omissions |
| Rebuilt tasks | Journeys replayed outside the supplier | Fix residual dependencies |
| Transition effort | Observed or estimated time and cost | Separate measurement from assumptions |
Common pitfalls
- Confusing termination with continuity
- Checking exports only after commitment
- Forgetting attachments and permissions
- Claiming a certain cost without testing
Frequently asked questions
Should every dependency be rejected?
No. Dependencies can provide value. Record what you accept, exit costs and conditions that would change the decision.
Is a CSV enough?
Only if it covers necessary data and relationships with an understood schema and tested import.
When should exit be tested?
Before committing critical functions and after changes that increase dependency.
Pagination: consistency and recovery
Reconcile collection identities and revisions
An exit inventory or OSINT collection can reach the last page while missing an object or mixing its revisions. A total alone does not establish that expected data is present.
- Fix order, scope and consistency reference before reading.
- Compare IDs and revisions beyond row counts.
- Retain discrepancies and recovery decisions when the reference changes.
Compare computed reads and recoveries →
Sources reviewed on · Google · AIP-158 Pagination · PostgreSQL 18 · LIMIT and OFFSET · PostgreSQL 18 · Row constructor comparison · PostgreSQL 18 · Transaction isolation · OWASP · API1:2023 Broken Object Level Authorization
API deprecation and retirement
Announced retirement and continuity to verify
A Sunset field signals intent; it establishes neither actual shutdown nor guaranteed continuity until then. Prepare dependencies, data and access to move.
- Identify the announcement’s exact scope and owner.
- Keep dates and updates with receipt evidence.
- Test exit, in-flight operations and removal of obsolete access.
Compare deprecation and retirement announcements →
IETF · RFC 9745 · Deprecation · Standards Track · March 2025 · §2–5 · consulted 2026-10-23
IETF · RFC 8594 · Sunset · Informational · May 2019 · §3–5, §8 · consulted 2026-10-23
Official references
References consulted: . The method and worksheet propose checks to adapt to your context; they do not constitute certification.
