Table of contents
At a glance
How should audit trails and electronic signatures be handled during migration?
Preserve the relationship between the record, its change history and its signature. Historical events must not appear as actions newly performed in the target system. Check that name, time, meaning and link to the record remain readable and traceable. An import timestamp does not replace the original approval or its context.
Scope and Applicability
The specific obligation is determined by the applicable record-keeping and signature regulation. Part 11 is applied only within its scope of applicability. A general technical transferability of any signature method is not asserted.
Historical significance over mere table-based replication achieved
An audit trail event can identify who modified a data record, when, and why. An electronic signature can link a decision to a specific individual and record. During migration, the required attribution must be preserved. This does not automatically imply that every historical event can be imported as a native action within the target system.
Capture the data model and technical scope of both systems. Audit fields, user IDs, time zones, and signature models may differ. A direct field mapping is insufficient when the target field generates a different meaning. An appropriate solution may combine migration, a linked archive, or controlled source access.
Separate historical records from new decisions. A copied signature shall not be considered re-performed by the previous signer solely due to importation. Similarly, a current technical identity must not be presented as the original operator. Origin and transfer relationship must remain appropriately identifiable.
Build a context matrix for audit data and decisions
Start with specific investigation questions. Which change should later be justifiable? Which decision depends on the then-existing record status? From these, the required fields and relationships are derived. The scope is determined by the applicable records and requirements, not by a universal list for every system.
Also check for deleted or deactivated user accounts. A historical user may no longer be active, yet must still be assignable to their original role at the time. Simply replacing the account with a current system administrator may distort the evidence. An appropriate reference or archive solution should preserve this historical record.
| Context | Question to resolve | Evidence to produce |
|---|---|---|
| Person | Who actually carried out the action or made the decision? | Historical identifier and appropriate assignment |
| Time | What is the relevant time point and time zone? | Traceable presentation and transformation |
| Content | Which record hold was modified or confirmed? | Unique version and object reference |
| Significance | Testing, approval or other action? | Received professional statement |
| Origin | What is original history, and what is a migration action? | Clear labeling and referencing |
Example: historical name is replaced by import user
A QMS exports a prior approval initiated by user U-8. In the target system, an import account creates the record. The default view now displays the import user as the author. Without additional historical context, a reviewer might incorrectly interpret the import user as the original decision-maker.
Define how the original decision and current acceptance differ. The historical record may remain in an appropriate field, document, or archival pathway. Review the display from the perspective of the intended reviewer. Technical information alone is of limited value if it remains hidden or ambiguous within the standard retrieval process.
Complete a corrected record and several decisions about the same process. The test should show which content belongs to which decision. A list of names and timings without record version can be insufficient. The chosen destination path is assessed on the basis of the complete historical question.
| Test case | Action | Expected finding |
|---|---|---|
| Historical Approval | Identify the original decision-maker | Not to be confused with import account |
| Record amendment | Open the earlier and later versions | Audit reference explains the change |
| Several decisions | Assign approvals to the same process. | Content and meaning remain distinguishable |
| Time zone change | Compare the specified time event | No unresolved chronological displacement |
| Deactivated user | Look up the previous identifier | Historical assignment remains available |
Signature display and legal characterization limit
A graphical name representation is not automatically an electronically executed signature. Verify the required linkage between person, intent, time, and data set. For applications relevant to Annex 11, particular attention should be given to signature manifestation and record linkage within the applicable framework. Annex 11 also includes requirements regarding electronic signatures in the GMP context.
The migration plan should specify which functions will remain active in the target environment and which will be retained as historical evidence. A PDF may serve as part of a document trail, but it does not inherently satisfy any specific technical signature requirement. A general equivalence to handwritten or qualified eIDAS signatures would likewise be imprecise.
Obtain required original linkages until the appropriate target pathway is demonstrated. The technical impossibility of a native import does not relieve retention or traceability requirements. It does affect the architectural decision. Clearly define boundaries, rather than treating export as fully equivalent to target system functionality.
Define test selection and acceptance criteria specifically
Select cases with simple decision logic, corrections, multiple versions, and potentially disabled users. Consider different historical formats where applicable. A review limited to new, fully completed data sets may overlook previous special considerations.
Define which transformation is acceptable. A unified time zone representation may be appropriate when the original reference and conversion logic remain transparent and traceable. Simply removing time zone information, on the other hand, may lead to ambiguity regarding the sequence of events. The decision should jointly consider value and significance.
Document expected historical statements and actual search results. A technical line counter is not enough. The reviewer should be able to answer the question on the basis of the intended access. Unexplained critical gaps are dealt with before shutdown or appropriate use.
Access and long-term availability ensured
An integrated archive must remain accessible even after the completion of the migration project. Verify links, viewers, permissions, and technical dependencies. A temporary export storage in the personal work folder is not an adequate long-term solution if it contains only the required history.
Name responsible parties for future investigations and changes. A new archiving platform may trigger further transformations. Obtain source-target mapping and appropriate reference cases to ensure historical significance can be assessed during this transition. Archival migration represents another stage in the data lifecycle.
Provide known boundaries clearly. A user should be able to distinguish between a current target system decision and a historical archived record. This clarity supports both audit inquiries and the routine handling of past activities.
Historical record and new importer qualification have various responsibilities
For historical signatures, the linkage to the actually signed content is essential. Verify whether subsequent changes to this state can be distinguished. If the target application cannot natively represent the original technical signature, a suitable verifiable preservation and access solution must be evaluated.
Audit trail exports also require context. Event codes without clear meaning, missing time zones, or lost object references can render the history practically unusable. Therefore, test a complete change event and its subsequent representation, rather than merely verifying the existence of a CSV file.
Draft: Retrieve historical decision in target or archive for reconstruction
Verify the target or archive path using a previously signed record that was subsequently modified. The table ensures that the original content, the individual responsible at the time, and the later modification remain distinguishable throughout the retrieval path. Source access rights are only revoked once adequate evidence of compliance in the intended final state has been provided.
| Context field | Example entry | Acceptance question |
|---|---|---|
| Record | Document referenced in an earlier version. | Which content was confirmed? |
| Person | Historical identifier U-8. | Is it differentiated from an import account? |
| Significance | Approval under the then-existing procedure. | No new plot faked? |
| Time | Original reference with declared time zone. | Is the chronology understandable? |
| Change | Later record status with its own history. | Separate old and new statements? |
| Pathway objective | Approved access to required documentation. | Will it remain usable after shutdown? |
Next steps
- Define historical records, signatures, and required events.
- Plan how records will appear in the target and how alternative archive references will work.
- Review linked release and change cases.
- Distinguish between import documentation and historical documentation unambiguously.
Project experience and collaboration
Migrate historical decisions with their context
With your team, we select historical records that must show the person who worked on them, the version, the meaning of the signature and the change history. We trace those links through export into the target system or archive. If a complete native transfer is possible, we test it on known cases. Where technical limits remain, an alternative controlled access path must preserve the required evidence. A current import account must never appear as the historical signer. We assess retention, usability and the original meaning of the record together.
Frequently asked questions about Migrating history and signatures
Must historical events remain in the native audit trail of the target system?
Can missing signatures be retyped?
Are PDF outputs always sufficient?
Do historical records need to be signed again in the target system?
A new signature would be a new act and not automatically the replacement of a historical decision. Evaluate which statement and connection must be received and how the target or archive path proves this. Origin, record level at that time and current migration action should not be confused with each other.
Can we archive audit trails as a separate file?
This could constitute part of an appropriate solution if the required linkage to data, individuals, and time is maintained and remains searchable. Review format, access, and completeness based on specific cases. A standalone file lacking unique record references or long-term readability does not automatically meet this objective.
Why is a historical user not simply replaced by a current name?
This may lead to distortion of the assignment of the previous action. Ensure appropriate historical references and provenance are available. A current user may be responsible for the migration, but does not automatically have authority to have made the prior decision. Evidence must distinguish between these roles.
How do we verify an exported signature slip?
Compare individual, significance, time, and linkage to the correct record status. Additionally, assess required context and subsequent access. A graphical name representation alone does not validate any technical or regulatory signature requirement. The statement is referenced to the specific historical traceability purpose.
Sources and review date
The classification is based on the listed regulatory and authority sources. The context matrix and migration example are standalone reference tools; they do not replace evidence of specific transfer or archiving.
- European Commission: EU GMP Annex 11, Computerised Systems (2011)Section 4.8, together with Sections 7, 9, 14, and 17: Transfer, history, signature reference, and archiving. Current version as of EudraLex on 14.10.2026; no universal project or deadline specification.
- eCFR: 21 CFR Part 11 – Electronic Records; Electronic SignaturesCurrent regulatory text. Applicability and additional documentation obligations must be assessed on a process-by-process basis.
- 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: .
Historical context regarding the system transition received
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.

