When should you move from a paper QMS to an eQMS, and how do you migrate?

1No regulation requires an eQMS.

Paper is an accepted medium. EU GMP Chapter 4 says documentation “may exist in a variety of forms, including paper-based, electronic or photographic media”.¹ Under 21 CFR 11.2, firms “may use electronic records in lieu of paper records”, in whole or in part, provided Part 11 is met.² For record retention and review, FDA holds paper and electronic record-keeping systems to “the same requirements”.³

So the question isn’t whether you may stay on paper. It is whether paper still controls the work at your size. ICH Q10 asks for a quality system applied in a way “appropriate and proportionate to each of the product lifecycle stages”, and for “the size and complexity of the company’s activities” to be considered when one is developed or modified.⁴

2Signs that paper has stopped scaling.

Paper control is work that grows with every document. PIC/S expects each document to carry a unique identifier and version, to be checked, approved, signed and dated, and to be issued under control so that superseded forms can’t be used.⁵ Where numbered sets of blank forms are issued, FDA expects them to be reconciled once all are complete, and incomplete or erroneous forms to be kept with a written justification for their replacement.³

A quality system’s value is in the links between records. ICH Q10 expects corrective and preventive actions to come from complaints, product rejections, non-conformances, recalls, deviations, audits, inspections and trends from monitoring.⁴ 21 CFR 211.180(e) requires at least an annual review of a representative number of batches and of the complaints, recalls, returned or salvaged products and investigations for each drug product.⁶ On paper, people make those links by searching binders.

The last sign deserves weight. Chapter 4 says the relationships and controls for master documents, official copies, data handling and records “need to be stated for both hybrid and homogenous systems”.¹ PIC/S says hybrid systems “require specific and additional controls”, that their use “is discouraged” and that they “should be replaced whenever possible”.⁵ Training follows the same logic: 21 CFR 211.25(a) requires training in the operations each person performs and in the written procedures that apply to them,⁷ so every procedure revision creates training to assign and record.

3What the new system has to keep.

Annex 11 sets the bar for any move from manual to computerised work: “there should be no resultant decrease in product quality, process control or quality assurance”, and “no increase in the overall risk of the process”.⁸ It asks for validation scaled by “a justified and documented risk assessment”, user requirements “based on documented risk assessment and GMP impact”, a formal agreement with each supplier that states its responsibilities, and arrangements for continuity if the system breaks down.⁸

For records FDA requires, Part 11 sets the controls: validation, access limits, audit trails and authority checks.⁹ Each electronic signature must be unique to one person,¹⁰ and linked to its record so it can’t be excised, copied or transferred.¹¹ Before or when you first use electronic signatures, you must certify to FDA, in a letter signed by hand, that they are “intended to be the legally binding equivalent of traditional handwritten signatures”.¹⁰ Records held in a hosted system can still meet the inspection requirement: 211.180(c) accepts records “that can be immediately retrieved from another location by computer or other electronic means”.⁶

4How to migrate.

Move one process at a time, so that each process has one system of record from a set date.

Document migration needs particular care. Annex 11 asks that validation check data “are not altered in value and/or meaning during this migration process”.⁸ MHRA warns that “the challenges of migrating data are often underestimated, particularly regarding maintaining the full meaning of the migrated records”.¹² PIC/S expects migration “in accordance with documented protocols” with “appropriate verification of the complete migration of data”.⁵ A matched file count alone doesn’t show that; revision history, approvals and references need checking too. For paper kept as the record, 211.180(d) allows “original records or true copies”,⁶ and MHRA expects references between physical and electronic records to be kept so that events can be fully verified.¹²

5The EU rules are being revised.

The European Commission consulted from 7 July to 7 October 2025 on a revised Chapter 4 and Annex 11. Its summary says the revised Chapter 4 supports “new technologies, hybrid solutions, and new services” in documentation, and the revised Annex 11 reinforces obligations on system requirements and supplier oversight.¹³ The draft Annex 11 would also have contracts define “an exit strategy by which the regulated user may retain control of system data”.¹⁴ Both are drafts: on 6 November 2026 EudraLex Volume 4 still lists Chapter 4 and Annex 11 of January 2011.¹⁵

6How it runs in Seal.

Seal can start with one process beside paper. Paper keeps running for everything else, and your team agrees which system holds which record while the move is under way; see paper and spreadsheets. Existing procedures can be imported in bulk and kept as PDFs at first, then converted to structured documents as they are revised. For records that move, relationships, attachments, versions and available audit context are preserved within the agreed scope, and representative records are reconciled before you rely on the new workflow; see the QMS.

Neil can reconcile a controlled-document migration: it matches source documents, revisions, approvals and references against the migration inventory and drafts a gap list. The migration and quality owners verify fidelity and accept the target. Retention obligations continue for the historical records that stay on paper.