Situation and intended use
An organization migrates ten years of eQMS records into a new cloud platform and plans to retire the old service. Users must retrieve historical CAPAs, attachments, approvals, linked changes, and relevant history for ongoing quality work and inspections.
Define the record before transferring it
Inventory record types and relationships. Identify historical states, exceptional records, attachment formats, signatures, user identities, and time representations. Decide which information remains in an archive and how users will retrieve it after the old service ends.
Evidence design
Counts help detect missing records but do not prove content and relationships. Combine population-level checks where feasible with risk-informed detailed review and justified coverage of exceptions. Define reconciliation rules and tolerances before execution; do not invent a convenient tolerance after mismatches appear.
| Check | What it can reveal |
|---|---|
| Record counts by type and state | Missing populations or unexpected duplicates |
| Field and content comparisons | Altered values or truncated text |
| Relationship checks | Attachment or approval associated with wrong parent |
| Historical retrieval | Records inaccessible under the intended archive workflow |
| Identity and time interpretation | Lost approval meaning or misleading chronology |
| Exception review | Unsupported formats, orphan records, unresolved failures |
Worked outcome — fictional
All main-record counts match. Detailed checks find that several attachments are linked to the wrong CAPA because the migration used a nonunique display number. The team corrects the key strategy and expands reconciliation to the affected relationship population. It does not accept matching counts as sufficient evidence.
Cutover and release
Define source freeze or controlled delta handling, final reconciliation, authorized go/no-go decision, user access, support, and recovery. Test retrieval through the intended post-retirement route before terminating the legacy service. Keep unresolved exceptions visible with their impact and disposition.
Ongoing responsibility
Assign an archive owner. Monitor retrieval issues and format/access changes. A cloud contract does not transfer accountability for understanding and retrieving the organization’s records.
Challenge: Is a PDF export of every CAPA enough?
Worked answer: Only if the approved record and retention assessment supports that representation and retrieval arrangement. Examine attachments, relationships, relevant metadata/history, signatures, and interpretability before deciding.