Table of contents
At a glance
What evidence supports retirement of a validated GxP system?
Define how records and their context will remain accessible after active use ends. Set acceptance criteria for the archive or successor system and test realistic retrieval requests. For a migration, demonstrate that the data retain their value and meaning, as addressed in Annex 11 section 4.8. Assign responsibility for the shutdown decision and evaluate any later data deletion separately.
Scope and regulatory context
This article concerns computerised systems used in EU GMP for human medicinal products. Determine retention periods and other obligations from the record type, product and applicable requirements. No single retention period applies to every record.
Switch-off is the last technical step
Before terminating accounts, licences or connections, demonstrate how users will access the records they still need. Define the target state and test cases first. That establishes a sequence for export, transfer and technical shutdown.
A decommissioning plan identifies dependencies and responsible parties. Base the final decision on tested outcomes. A contractual shutdown date alone cannot establish that data and evidence are adequately preserved.
Plan decommissioning as a controlled lifecycle activity
Define what will happen to the data and processes after retirement. Before technical shutdown, assess and demonstrate the necessary prerequisites. Identify the system owner, data owner, QA, IT operations and other relevant functions. Apply the responsibilities defined in your quality system.
Annex 11 covers data storage and archiving. Chapter 4 addresses documentation and records. Neither prescribes a document universally titled “decommissioning plan”. A traceable plan can connect scope, sequence, evidence and decisions in a format that fits your existing QMS.
Inventory the system, version, sites, data types, interfaces and ongoing tasks. A system with no active transactional users may still support historical searches, licences or background services. Check actual data flows and dependencies before terminating contracts or access.
Choose migration, archiving or read-only legacy access
Migration makes selected information usable in a successor system. An archive preserves records for long-term access. Read-only operation can retain the original application's historical search capability. Each option carries different risks and operating responsibilities.
Assess content, context, accessibility, technical dependencies and ongoing support. PDF export may suit simple static records but can lose essential relationships in dynamic data. A read-only system may preserve context while depending on old software, hardware or licensing services. Include these limits in the decision.
| Target state | Possible benefit | What to assess |
|---|---|---|
| Migration | Use the data in the new process. | Transformation, relationships and history. |
| Suitable archive | Retain historical information independently. | Readability, context, access and long-term maintenance. |
| Read-only legacy operation | Retain the original search functions. | Write paths, security, licences and recovery. |
| Combined approach | Choose an appropriate treatment for each record type. | Clear access routes and complete overall coverage. |
A decommissioning plan with eight verifiable outcomes
Start with a reviewed inventory. For each data area, determine future use and retention. Define the target state, test method and acceptance criteria before transferring records or making the archive available. This prevents premature loss of source access.
Test the target against real historical questions. Can an authorised employee explain a past decision using its data and methods? Can they retrieve attachments and relevant change history? Neither a file count nor a successful database backup demonstrates this.
Before shutdown, assess remaining tasks and dependencies. Carry out controlled technical steps, update the inventory and hand over archive or operating responsibilities. Assign a named owner for the state after project closure.
| Step | Deliverable | Question to answer |
|---|---|---|
| 1. Scope | Reviewed inventory of systems and data | What is actually being decommissioned? |
| 2. Obligations | Justified retention and use requirements | What must remain accessible? |
| 3. Target state | Assessed architecture decision | Why is the chosen approach suitable? |
| 4. Test plan | Criteria and specific historical retrieval cases | What will demonstrate suitability? |
| 5. Implementation | Identified transfer or archive deployment | Which dataset and version were produced? |
| 6. Verification | Reconciliation, retrieval results and assessed findings | Can the user interpret the content and context? |
| 7. Shutdown | Approved sequence of technical actions | Are there no unresolved critical dependencies? |
| 8. Handover | Owners and ongoing tasks | Who will maintain access and usability? |
Example of retiring a legacy LIMS
A laboratory exported its result values. A historical complaint also needs the method version, specification in force at the time and a change to the result. None of these is in the export. Shutting down the LIMS now would make reconstruction difficult even though all the numerical results are present.
The data owner adds methods, specifications, relevant audit information and attachments to the inventory. The team chooses an archive for some records and controlled read-only access for the remainder during a transition. Verify the necessary relationships and technical dependencies before accepting the combined approach.
The team selects a completed routine order, a corrected result and an investigation with an attachment. An authorised employee reconstructs each case from the target, records the information and links found and identifies gaps. Correct the gaps and repeat the checks. The authorised owner then decides whether the demonstrated target state supports final shutdown.
| Retrieval case | Information required | Expected result |
|---|---|---|
| Routine order | Sample, result, method and assessment | A reviewer can understand the historical decision. |
| Corrected result | Original and changed values with their context | The change is traceable. |
| Investigation | Attachments and related transactions | No necessary business relationship is lost. |
| Loss of access | Suitable recovery route | The required use can resume. |
| Unauthorised access | A specified role without authorisation | The intended restriction prevents access. |
Retire services, connections and contracts in the right order
Check dependencies on licence servers, identity providers, certificates, encryption keys and external storage. An export can become unreadable without a key or viewer licence. A virtual machine may lose authentication when another service is switched off. Assess the dependencies before terminating services.
Inventory interfaces and scheduled jobs. A retired sender can leave recurring failures in a successor system, while an obsolete service account may remain active. Identify every connection and the accountable owner on the other side. “Server off” is insufficient evidence.
Erasing media and retaining data require separate decisions. Identify which records are still needed and whether suitable copies have been verified. Set deletion and retention timing from the data type, product, applicable rules and any further obligations.
Project close-out and ongoing archive ownership
Connect scope, target state, tests, assessed findings and actual shutdown steps in the closure record. Identify outstanding activities explicitly. Technical project completion may still leave a read-only environment needing support and monitoring. Document that dependency.
Hand over access, retrieval instructions, recovery arrangements and ownership. A later storage or operating system change may impair readability. Determine checks and intervals from the format, risk and planned retention period.
During handover, ask someone outside the original project team to retrieve a historical case. Preserve a route for future data requests and any necessary archive migrations. The project record should still explain the decision after the technical work ends.
Link shutdown approval to the tasks that remain
Use the table in the closure meeting. Record the verified destination and supporting evidence for each data area. Link the result of the practical historical retrieval exercise to the shutdown decision.
For a failed case, identify whether content, context or authorised access is missing. Another export will not solve every problem. Use one reference for the correction, retest and outstanding action so nothing is lost at handover.
| Closure item | Example entry | Evidence needed |
|---|---|---|
| Scope | Legacy LIMS with results, methods, attachments and relevant history. | Reviewed inventory with destinations. |
| Target | Archive with justified, limited read-only legacy access. | Specified historical retrieval cases passed. |
| Dependency | Viewer, key and identity service identified. | Access and recovery tested. |
| Outstanding action | Defined open task with a named owner. | No concealed critical gap. |
| Shutdown | Jobs, connections and accounts terminated in the approved sequence. | Traceable evidence of execution. |
| Ongoing operation | Archive ownership and the data request process handed over. | Practical handover using a historical case. |
Archive approval and deletion require separate decisions
After archive or migration acceptance, copies may remain on servers, export directories, test environments or with service providers. Inventory them at closure. Approval to switch off the application does not authorise deletion of all linked information. With the responsible people, check retention, open investigations, other holds and the information required to reconstruct records.
A deletion plan identifies the data class, location, prerequisite, owner and evidence. Backups and immutable storage may follow different technical lifecycles from working copies. Address them in the retention and security arrangements. Determine the applicable deletion requirements and privacy considerations for the case. Uninstalling a server application does not establish that all copies are gone.
What still needs attention after switch-off?
The example LIMS is off and its required archive has passed the checks. A temporary export remains on a shared project drive and an old supplier account is active. The archive may be suitable while both items still require action. Record each outcome and assign its owner.
Retire access and services in the right order. Preserve any licence or identity service still required for approved archive retrieval. Verify which dependencies remain after implementation. Check what a supplier's written confirmation actually covers. A statement about active storage says nothing by itself about every backup or subcontractor.
| Record or access route | Check before closure | Suitable evidence |
|---|---|---|
| Approved archive | Retention and ongoing ownership | Evidence of retrieval and authorised access |
| Temporary export | Required transfer complete and no holds apply | Documented, controlled removal |
| Test copy containing historical records | Whether it remains necessary and what may be retained | Justified treatment of the specific copy |
| Backup or immutable storage | Technical lifecycle and applicable retention arrangements | Documented treatment assigned to the records |
| Supplier access | No required archive function still depends on it | Evidence the access was actually terminated |
| Legacy licensing service | The archive can operate without it or its replacement was tested. | Evidence of retained operation or authorisation to terminate |
Practical next steps
- Define system scope and remaining retention requirements.
- Plan the target state and necessary migration or archive checks.
- Verify the preservation of data, context and access.
- End dependencies in sequence and hand over operating responsibility.
Project experience and collaboration
Decide when the system can be switched off
Before decommissioning, we choose a historical transaction with the process owners, QA and IT that someone will need to investigate later. If the proposed archive supplies the evidence needed to answer that question, we use the case to test transfer and handover. If an essential interactive function is missing, controlled read-only operation of the old system may be a better interim option. We help compare the options and sequence data transfer, account removal and shutdown. Your authorised owners decide on the basis of the results. Any later deletion is a separate decision.
Frequently asked questions about GxP system decommissioning and data disposal
Is a backup sufficient for decommissioning?
Must every legacy system run until all retention periods expire?
Who authorises shutdown?
Is a separate decommissioning plan mandatory for every system?
The cited requirements do not prescribe a universal document title. Decisions and evidence must remain traceable. Use a dedicated plan or integrate the work into existing change control and data lifecycle procedures. Choose the form and scope to suit system, data and risk.
Can we switch off the legacy system as soon as the new application runs?
That alone is insufficient. Check historical records, retention, outstanding transactions and technical dependencies. The new system may run successfully while essential information is accessible only in the legacy system. Approve shutdown on the evidence for the target state and remaining needs.
Does an archive need ongoing checks?
Yes. Annex 11 section 17 addresses the accessibility, readability and integrity of archived data. When relevant changes are made to the system, the ability to retrieve the data must be ensured and tested. Section 7.1 addresses access during retention. Annex 11 does not set a fixed annual interval. Justify the ongoing plan and additional triggers from format, infrastructure, retention needs and failure risks.
What should the decommissioning closure record say?
Identify scope, target state, tests, assessed findings, actual shutdown measures and remaining responsibilities. A technical switch-off record cannot establish the continued usability of historical data. Keep outstanding tasks visible, including support for read-only operation or archive maintenance.
Can we discontinue an expensive legacy licensing service after shutdown?
Only after showing that the required historical use no longer depends on it or a suitable alternative works. Test retrieval and restoration. Without the viewer or key, an available export may still be unusable. Assess cost alongside business needs and dependencies.
May we erase all old copies once the archive is approved?
Check the approval scope, retention, open investigations, other holds and required reconstruction information. Base each deletion decision on specific data classes and locations. Archive approval, application shutdown and handling residual copies are related but distinct decisions.
Does uninstalling the application prove no GxP data copies remain?
No. Exports, test copies, backups and supplier-held data may remain elsewhere. Identify locations and assign their treatment. Check residual accounts, keys and technical dependencies. Describe the actual state at closure, including justified retained copies.
Sources and review date
Sources were checked on 15 October 2026. The text was revised on 17 October 2026. We developed the numerical examples, criteria and tables as planning aids. Assess shutdown, archive release and eventual disposal separately for the records in scope.
- European Commission, EU GMP Annex 11: Computerised Systems (2011)Sections 7 and 17 cover data storage and archiving. EudraLex listed this edition as current on 14 October 2026. The decommissioning plan and sequence are our practical suggestions. These sections set no universal project or retention period.
- European Commission, EU GMP Chapter 4: Documentation (2011)Documentation, record context and retention. Establish periods and responsibilities for the actual records concerned.
- PIC/S, PI 041-1, Good Practices for Data Management and Integrity (2021)Inspection guidance on data integrity, particularly electronic data, transfer, access and review.
Sources checked: .
Discuss the next decision in your decommissioning project
We help you assess the starting point, define responsibilities and put suitable checks into operation. The support depends on your system, team and intended outcome.
- 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.

