Table of contents
At a glance
What belongs in a GxP exit plan for a cloud system?
A GxP cloud exit plan defines how processes and required records will survive a supplier change or contract end. Cover export scope, formats, context, time windows, support and future access. Test data usability before final access is withdrawn. A contractual promise to export data does not establish a successful transfer.
Scope and Applicability
This article addresses operational and quality-related handover processes. Contractual, data protection, and retention requirements must be appropriately supplemented. It does not replace individual legal contract review.
Annex 11 calls for formal agreements with service providers who operate systems or retain data (3.1) and access to the data throughout retention (7.1). When transferring data to another format or system, demonstrate preservation of value and meaning (4.8). Section 17 also applies to archived data.
Plan cloud exit as a data and operational task prior to contract end
A cloud exit involves data access, processes, technical identities, and remaining obligations. A standalone export button does not constitute a complete exit strategy. Early clarification is required regarding which information will be available, in what format, and by when. Contract end dates and professionally appropriate end states must align in sequence.
Capture supplier deliverables and internal responsibilities. Who provides exports, who reviews them, and who is responsible for the target? Which access rights remain available during the investigation of deviations? Identify potential additional costs and time windows specified in the specific contract. This article does not establish general contractual claims, but rather raises questions for your agreements.
Distinguish active migration, historical archiving, and technical decommissioning. A successor system can support the new process, while historical audit information must remain accessible through an appropriate alternative pathway. The final decision on deletion or access follows only after evaluation of the actually required records.
Define an exit scope with formats and context
Review business objects, appendices, metadata, relationships, and required change information. Also assess configuration, methods, and selection logic, to the extent they provide historical context. An export containing only current, visible data sets may shorten the required lifecycle.
Request a specifically defined format description and a pilot run. Files must be technically processable and professionally interpretable. A proprietary format may be suitable if controlled access is available; an open format is not automatically complete. Assess the actual content and required tools.
| Exit question | Subject matter to be clarified | Evidence to produce |
|---|---|---|
| Scope | Which objects and versions are provided? | Compare inventory against export list |
| Context | How are relationships and history maintained? | Reconstruct complete processes |
| Format | Which software or keys are required? | Read along the intended pathway |
| Time point | Which data date is included? | Extraction and Delta Withdrawal |
| Subsequent delivery | How are differences resolved prior to contract end date? | Agreed Error and Correction Procedure |
| Remaining access | What information remains with the supplier? | Assessed professionally and contractually valid state |
Example: complete main data export without appendices
A SaaS QMS provides a CSV file containing all events. Attachments are only accessible via time-limited download links. The succeeding team successfully imports the main data. After contract termination, the links expire, resulting in the loss of required documents for historical investigations.
The pilot run should detect this scenario prior to contract end. Select events with multiple attachments, versions, and relationships. Verify actual file content access in the target, not merely the existence of a link. Document which information remains externally stored and justify why this approach remains sufficiently appropriate.
Following the export, the reconciliation is repeated. Retrieve identifiers and relationships to ensure that attachments are correctly assigned to the respective process. A collection of similarly named files lacking context is equally unsuitable. The exit closure confirms the verified total scope, not merely the successful import of the master table.
| Test case | Action | Expected finding |
|---|---|---|
| Main object | Take over a known process | Unambiguous source-to-target mapping |
| Several annexes | Open files in the target directory | Correct content and reference |
| Previous version | Investigate historical records | Required previous context available |
| Expired link | Supplier access controlled to exclude | The intended pathway functions as expected. |
| Difference | Intentionally introduce missing file | Alignment identifies and tracks the gap |
Schedule time window and remaining access for exit
Plan the time window between the last productive operation and the end of system access. During this phase, additional records may generate or export errors may become apparent. The plan therefore requires authorities for replenishment, reconciliation, and, if necessary, a time-limited residual access.
Consider costs and dependencies in the decision-making process. An efficiently running service may result in significant expenses during data release if data is only available in proprietary formats. This is not a blanket criticism of cloud services, but rather a question of preparedness for data transfer.
Delta, operational transition and rollback are linked
Between test export and final exit, new or modified processes may arise. Define when the source remains authoritative and how subsequent changes are incorporated. An early successful pilot run does not validate the final data state. Particularly, status, open tasks, and attachments require a clear and traceable handover.
Plan the handling of a failed final export. Can the supplier access be extended? What costs and decisions would be required for that? A rollback must not be discussed once the contract has been terminated. The specific option will be evaluated on a contractual and technical basis.
Upon initiation of the target system, new records are generated. Therefore, a rollback affects more than merely the reactivation of an account. Describe how currently processed activities are reconciled. Concurrent, uncontrolled use of both systems may result in inconsistent lead records.
Close access and deletion in a controlled manner
Retire technical identities, interfaces, and authorizations in the correct sequence. Premature deactivation of a service account may prevent a final export. Conversely, an unnecessarily active account may enable unauthorized access. The checklist should specify the purpose, counterpart, and responsible person for each access.
Evaluate the provider's confirmation for deletion or remaining storage in the concrete contractual and storage context. A deletion confirmation does not prove the suitability of your target archive. Conversely, a good archive does not answer any question about remaining copies at the provider. These decisions are linked to each other, but can be proved separately.
Obtain the necessary documentation relating to the export procedure and known limits. A subsequent review can only be conducted if the source, run, and mapping remain traceable. The exit record should therefore include more than just a termination notice and a file list.
Operational use and historical investigation handed over
Identify personnel responsible for active data and historical access records. An employee should be able to demonstrate where a prior process can be located following an employee exit and specify the applicable boundaries. Verify this with a person who did not perform the export themselves, demonstrating practical usability rather than mere file transfer.
Integrate ongoing archiving tasks into operations. Viewer, key, and storage settings can be modified later. The required statement must be retained. Appropriate checks are derived from actual technical dependencies and planned retention requirements.
An exit can inform the next SaaS selection. Before contracting with a new supplier, ask what the export includes, whether you can test it and which historical evidence you can retrieve. Plan for an orderly exit as part of long-term operation.
Draft: Verify exit readiness prior to revocation of supplier access
The table summarizes the exit decision for a complex process. Perform the pilot run while queries and follow-up deliveries are possible, and thereafter designate the primary source and the final delta capture point. If an exportable audit trail is missing, an alternative target architecture may be required. The required access may only be withdrawn once the selected solution and final inventory have been adequately demonstrated.
| Exit field | Example entry | Acceptance question |
|---|---|---|
| Scope | QMS Event with multiple attachments. | Do all required components are included? |
| Format | Documented export structure. | Is the intended target readable? |
| Relationship | Source identification links the main object to files. | No loss of professional alignment? |
| Remaining access | Supplier link will be checked and not used. | Is the actual path truly independent? |
| Delta | Changes following the pilot run have been recorded. | Final version fully describes? |
| Withdrawal | Interfaces, connections, and agreements will be properly terminated. | No too early critical shutdown? |
Distinguish a planned exit from sudden loss of the provider
For a planned change of provider, prepare the export, transfer of subsequent changes and approval for shutdown. A sudden outage may remove normal provider access. Establish which functions are affected and whether independent data access remains. A technical incident, contract termination and permanent loss of the provider call for different actions. Assess contractual or regulatory deadlines for the individual case.
The first decision relates to the process: Which activity must be interrupted, and which can be continued using an already approved alternative procedure? Retain available records and establish the most recent reliable data point. An early exported package may be outdated. Avoid ad hoc takeover actions that present incomplete information as current. The following matrix serves as a dedicated triage tool, not a universal emergency response plan.
| Situation | First inspection question | Next controlled action |
|---|---|---|
| Service temporarily unavailable | Which processes and data are missing? | Clarify the emergency concept and status |
| Termination announced | Until when does secure access exist? | Define the export and acceptance plan |
| Supplier permanently inaccessible | What independent data are available? | Assess completeness and limitations |
| Only old export data available | What changes are missing since then? | Investigate Delta and process impact |
| Alternate system available | Does it carry the required statement? | Check suitable take-over and use |
Sources: [1]
Test independence practically before it is needed
Allow a duly authorized reviewer to answer a significant historical question without current supplier access. The reviewer requires a known reference package and the intended alternative procedure. Verify content, relationships, attachments, and required history. A successful file download test is insufficient for this purpose. If login, viewer, or key access continues to depend solely on the supplier, the claimed independence is compromised.
Derate targeted improvements from the following: appropriate exports, verified restoration procedures, clear accountability, and regular evaluation of relevant changes. Efforts should be proportionate to criticality and available resources. A second copy lacking essential contextual information may merely double the same deficiency. Therefore, the exit strategy must demonstrate which professional usage can be independently sustained and which residual dependencies are intentionally retained.
Next steps
- Define the required data scope and subsequent intended use.
- Agree the specific export and support services.
- Perform representative test export with professional data retrieval capability.
- Final handover, residual access, and closure decision to be documented.
Project experience and collaboration
Test the exit while the provider is still available
We plan a trial export with the process owner, IT and archive staff before access to the existing system ends. We trace one complex transaction in the target system, including its attachments, history and relationships. Missing files may be recoverable. A function that cannot be exported may require a different retention solution. We also identify changes made between the trial export and the end of the contract. The responsible person bases the closure decision on the actual test results.
Frequently asked questions about Cloud exit planning
Is an exit plan required only upon termination?
Does a ZIP file provided by the supplier suffice?
Must data be immediately deleted after export?
Is an open export format automatically sufficient?
No. A format can be easily processable and yet incomplete. Review content, relationships, metadata, and required history. A proprietary format may be appropriate in reverse if long-term access is effectively controlled. The technical suitability arises from specific search and reconciliation tests.
Can we first terminate and then clarify the data export?
This eliminates avoidable dependence on remaining time windows and access periods. Clarify and validate the required scope prior to final withdrawal. Contractual provisions, supply follow-up, and an appropriate target state should be aligned. The deployment of a technically implemented successor system does not automatically ensure the retention of historical records.
Why should a Cloud exit include a test without vendor access?
If future access is to be independent, this review verifies whether files and relationships have been actually transferred or merely point to external links. Select appropriate complex workflows. A successful access during active login may mask future dependencies.
What should be included in the handover following a cloud exit?
State the intended use, historical access paths, known limitations, key personnel and responsible parties. Include source-to-destination references and reconciliation evidence. The team should be able to identify and explain an older process without the original export team. Technical termination alone does not constitute completion of this task.
What to do first when a cloud provider is suddenly unavailable?
Identify affected processes, available data, and their most recent reliable snapshot. Use the prescribed emergency procedure and prevent uncontrolled decisions based on outdated information. Clarify supplier status and required escalations. An ad-hoc export or system switch does not substitute a formal assessment of functional usage.
Is an external viewer already provided for independent archive access?
Only if it remains genuinely usable under the planned conditions and presents the required information. Verify login, license, key, format, and context. A viewer that still depends on an unreachably accessible supplier service cannot fully demonstrate the desired independence.
Sources and review date
Annex 11 and PIC/S provide the framework for service providers, data transfer, and data retention. The described pilot runs and exit decisions are internal implementation proposals; the actual export scope must align with the contract, system, and subsequent audit purposes.
- European Commission: EU GMP Annex 11, Computerised Systems (2011)Annex 11, January 2011: 3.1 regarding agreements with contractors, 4.8 concerning the preservation of data integrity and significance during data transfer, 7.1 relating to access during storage, and 17 on archiving. Exit checklists are standalone work aids.
- PIC/S: PI 041-1, Good Practices for Data Management and Integrity (2021)Inspection Guidance on Data Integrity; in particular electronic data, transmission, access, and review.
Sources checked: .
Data and responsibility organized from the cloud and transferred
We support you in assessing the current situation, clarifying responsibilities, and implementing appropriate evidence within operations. The type of support that is most effective depends on your system, your team, and the specific objective.
- GxP system decommissioning →
Retire legacy systems while preserving data, context and auditability. We plan and manage the decommissioning so that data, metadata and audit trails remain readable and retrievable after shutdown.

