Regulations and compliance · Practical guide

GxP legacy systems: assessing continued read-only operation

Keeping a legacy system available for read-only access can support retirement. Administrators, background jobs and database tools may still change records despite a locked input screen. Check actual access paths and dependencies, including whether automatic clean-up can remove required history.

Table of contents

At a glance

Is a read-only legacy system a suitable GxP archive?

Read-only operation can be a suitable transitional or retention state where necessary data remain accessible, understandable and protected. The “read-only” label alone does not ensure this. Test remaining write paths, technical dependencies, licence access and supportability over time. Responsibility for retention continues beyond the final production transaction.

Scope and Applicability

Here a possible decommissioning option is evaluated. There is no blanket recommendation to continue operating any legacy system indefinitely. Migration and separate archiving may be appropriate depending on the data volume.

Sources: [1] [2]

Test technical dependencies and retrieval after the transition

Access often depends on components not included in the archive plan: identity services, certificates, license servers, or legacy operating systems. If these services are later decommissioned, even a technically intact dataset may become unreadable. Therefore, continued operation requires a designated owner and a realistic preservation strategy.

After transition, can personnel with intended rights identify and interpret historical events? Is a required copy exportable? A successful administrator login alone is insufficient as evidence for subsequent audit or investigation access.

Sources: [1] [2]

What a reader actually receives in a read-only operational mode

A read-only model can enable historical querying within the original application. It preserves relationships and functionalities that a simple export would otherwise lose. At the same time, a technical environment remains active. This environment continues to require authorization, access, security, and appropriate recoverability. Therefore, a read-only status does not automatically imply maintenance-free operation.

Define the data entry actions that should be prevented. A locked input form does not confirm whether database accesses, interfaces, jobs, or administrative tools continue to enable content modifications. Identify the actual pathways and implement appropriate controls. A general assertion of complete immutability would be unwarranted without such evaluation.

Distinguish archival functionality from technical packaging. A virtual machine represents an operating mode, not independent evidence of long-term readability. A PDF collection may retain static information, but loses capability for dynamic querying. The target state must be evaluated based on required historical inquiries.

Sources: [1] [2]

A system architecture decision with ongoing dependencies is being made

Capture the application, database, operating system, identity service, license server, viewer, and keys, as required. Assess which components remain supported and recoverable. A functioning access on the shutdown date does not prove availability following a subsequent server or account change.

Compare continuous operation and an independent archiving solution based on the same technical scope. A cost-effective continuous operation may lead to prolonged maintenance or uncontrolled outages over the long term. An archiving project may initially be more resource-intensive, but it reduces technical dependencies. There is no universal winner; the decision should integrate risks, usage requirements, and lifecycle considerations.

Internal Work Aid: An architectural decision with ongoing dependencies to be made
CriterionContinuous Reading ModeIndependent archive pathway
Historical Function Original intended use may retain context The required research must be specifically documented.
Write protection Evaluate all relevant routes Takeover and subsequent integrity checks
Technical Interdependence Old runtime, license, and services remain relevant New formats and archive components will be relevant
Recovery A complete environment required Appropriate data and application recovery
Later amendment Continue operation under control Readability and potential archiving migration retained

Sources: [1] [2]

Example: Surface locked, background job modified further

An older system is set to read-only for regular users. However, a planned background job continues to clean certain historical data sets. The user interface appears unchanged, despite the inventory being modified after the intended decommissioning date. A test focusing only on button functionality fails to detect this dependency.

Inventory jobs, integrations, and technical identities. Verify the selected read-only rule with appropriate tests via the relevant pathways. For the background job, assess whether it is deactivated, controlled and limited, or still professionally required. The decision must take into account the intended target state.

After reconstructing a historical process, compare it against a known reference batch. Include a duly authorized administrative maintenance activity. Necessary technical upkeep must not go unnoticed and must not alter professional documentation. The evidence should clearly distinguish between permitted administrative actions and protected content.

Own work aid – Example: Surface locked, background job modified further
Test caseActionExpected evidence
User interface Attempting to modify historical records Selected user restriction applies
Interface Requested write-up attempt No unexplained change path
Job Assess planned background processing The intended state is not altered without detection.
Administration Perform required maintenance Data integrity is controlled
Reference search Find a known process again Required content and context received

Sources: [1] [2]

Practically test readability and recoverability

Select a normal historical process and a case with critical context, such as correction, method version, or appendix. A duly authorized employee should be able to explain both cases without assistance from the original developer. An open homepage or successful login is insufficient for this purpose.

Test a suitable recovery scenario, including the actual data and components required. Following this, assess not only the technical startup but also historical data retrieval. A backup may exist, while license access or keys may be missing. Such limitations must be known prior to the final decommissioning decision.

Document expected access times only with appropriate justification. A universal requirement in seconds or hours is not accepted. What is essential is whether the required information is adequately available for the intended tasks and that outages are appropriately managed.

Sources: [1] [2]

Maintain security and access during continued operations

Outdated software may pose security risks that do not disappear due to lack of active use in the process. Assess exposure, access pathways, and potential mitigation measures. Adequate isolation can provide support but does not replace controlled access or functional search capabilities. Any changes to mitigation measures must consider their data and operational impact.

Identify internal and external users. Even infrequently used accounts should have a clear and justifiable purpose. Review delegation and access pathways, particularly in the event of a future inspection. An archive accessible only through the personal account of a retired administrator presents a practical access gap.

Maintain records of necessary maintenance and changes. A new virtualization platform, an updated identity service, or a storage migration may impact readability. The extent of additional testing shall be determined based on this effect. Read-only status does not exempt from evaluation of relevant technical changes.

Sources: [1] [2]

Prepare for the final decommissioning of residual operations

A continued operation may represent a justified interim solution. Define the conditions under which its eventual replacement can be justified. This may include an appropriate archive export, a completed historical review, or a changed storage requirement. A mere calendar date lacks substantive justification.

Provide architecture, access controls, search incident cases, recovery procedures, and open dependencies. Responsibility must not vanish upon project completion. A controlled residual operation constitutes a distinct operational state with deliberate scope. Document it accordingly and ensure subsequent decisions remain traceable.

Sources: [1] [2]

Draft: Demonstrate write protection and historical usage jointly and contemporaneously

Use the table to separately document authorized inquiries, required technical maintenance, and unauthorized modifications to the historical inventory. The checks for write paths and recovery are described above; here, their results are linked to responsibility for ongoing operations.

Upon identifying a write path, first assess its impact on the process. A technical maintenance action does not need to alter the historical record. Conversely, a blanket restriction may eliminate the only remaining viable access. Therefore, after a correction, also re-evaluate the required research effort.

Sample filling example – internal work aid
Control fieldExample entryWhat the test establishes
Use in the process Investigate historical data. Content and context available.
User interface Attempt to change critical values. The intended limitation applies.
Alternative route Job, interface and direct access assessed. No unresolved write path.
Administration Required maintenance with responsibility. Data integrity controlled.
Failure Restore the identified dependency. Search functions work completely thereafter.
Replacement Condition for the subsequent end of residual operation. No unjustifyed duration dependence.

Sources: [1] [2]

Next steps

  • Purpose and duration of storage and continued operation.
  • Document workflows, automated jobs, and technical dependencies.
  • Check intended use and access protection with assigned roles.
  • Owning party, define ongoing controls and subsequent exit strategy.
Further reading:

Project experience and collaboration

Check what remains operational after the interface is locked

With IT and archive owners, we identify write access that remains possible despite a read-only user interface. Depending on the architecture, jobs, interfaces and administrator accounts may still write data. If these routes can be effectively restricted, managed residual operation may be suitable. Where dependencies can no longer be controlled, another archive solution needs assessment. We also test retrieval of historical records after restoration and identify who owns the solution beyond the project.

Frequently asked questions about Read-only operation during decommissioning

Does a read-only system require further maintenance?

Yes. Even a read-only operational mode requires appropriate technical maintenance, access control, and recovery procedures. Changes to infrastructure, identity, or licensing services may impact historical usage. The scope and solution shall be determined based on the remaining functionality, identified risks, and the intended duration of operation. A single past availability test does not confirm future, indefinite availability.

Sources: [1] [2]

Can a software usage license be terminated?

Only after it has been established whether the required data access is impaired and an appropriate alternative exists. Contractual terms must be reviewed separately.

Sources: [1] [2]

Is a screenshot of the old interface sufficient?

Typically, he represents only a single visible state. Whether he receives the required data content and context must be specifically evaluated.

Sources: [1] [2]

Is a virtual machine automatically an appropriate archive?

No. It can provide a technical operating pathway. Additionally, assess data context, write pathways, dependencies, access, and recovery. A virtual server can equally depend on legacy licenses or keys as a physical machine. Suitability is derived from the proven historical intended use.

Why does removing all specialist user write permissions not always suffice?

Other pathways such as jobs, interfaces, or administrative tools may still have an impact. Assess and evaluate the actual architecture. The required control should preserve the intended historical record, without unambiguously excluding necessary technical maintenance. Evidence must demonstrate this boundary.

How do we plan for the eventual end of a residual operation?

State the remaining requirement and a suitable alternative solution or the justified withdrawal of the requirement. Assess the target state prior to final discontinuation. A calendar date alone does not establish suitability. Archive access, retention, and technical dependencies must be aligned.

Sources and review date

The sources provide the technical foundation. Tables, checklists, and examples are derived methodological tools, not verbatim regulatory requirements. Manufacturer information must be referenced to the specific version and configuration in use.

  1. European Commission: EU GMP Annex 11, Computerised Systems (2011)Sections 7, 10, 12, 16, and 17: Data retention, modifications, access, continuity, and archiving. Current version as of EudraLex dated 14.10.2026; no universal project or deadline stipulation.
  2. 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: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Secure the reading residual operation in a comprehensible manner

We are reviewing the remaining write paths, technical dependencies, and historical investigation cases with your team. From this, appropriate controls and the required oversight can be derived.

  • 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.

Send a project enquiry Customer testimonials →