Test digital solution portability before committing
Check exports, dependencies, access and recovery in another solution with a documented trial and decision worksheet.
Read the practical method →Government Digital Service guidance for examining technical dependencies, cloud service value and exit preparedness. UK public procurement requirements are not French obligations.
Resource identity and purpose checked against the source on . This check does not verify all service conditions or individual data records.

IT, cybersecurity and cloud · UK · technical method
Open the original resourceSeparate the value delivered by the service from the effort of changing providers. List dependencies, then test a small export and recovery in an authorised environment.
This UK reference concerns cloud management. Its technical reasoning can inform selection; its institutional requirements are not transposed to French law. An exported file does not prove successful recovery.
Data, relationships and functionality needed for recovery.
Documented skills, costs and switching times.
Distinction between technical guidance and UK public procurement requirements.
Fictional example: two solutions support the same task but export different data. The team tests limited recovery and documents what must be recreated before comparing cost and dependency.
Check exports, dependencies, access and recovery in another solution with a documented trial and decision worksheet.
Read the practical method →Service-design methods covering user research, structure, prototypes, interface writing and simple journeys.
Explore this resource →Government Digital Service · Cloud lock-in — primary source. Link checked . The checklist is editorial guidance; link availability does not guarantee completeness or suitability.
Read the editorial method · Report a correction with its source