Dovetail
Evidence before cutover

Paper QMS to eQMS migration without losing record history

Uploading every binder, Google Doc, and tracking sheet into a new eQMS feels like progress until an auditor asks who approved revision two and where the missing appendix went. A defensible migration starts before import, when you decide what moves, what stays archived, and what evidence proves the switch is ready.

Your first quality system probably grew across physical binders, shared Google Docs, scattered PDFs, and spreadsheets that everyone understood while the team fit around one table. A paper QMS to eQMS migration is supposed to stop the version hunting and email approval chases, yet a move can stall even after the bulk uploader finishes. Counting uploaded files only proves that files landed somewhere. It never proves that approval history survived intact, that appendices and supplier links stayed connected, or that your team can pull the right record during an inspection.

Treat the transition as an evidence decision rather than a file transfer. Separate active records from controlled archives before exporting anything, test a representative trial batch against criteria you wrote down in advance, and approve cutover only when reconciliation, access permissions, retrieval, and rollback safeguards hold up. Where regulatory references appear below, they cover US FDA requirements under Title 21 of the Code of Federal Regulations as applicable, while the acceptance worksheet and cutover practices offer practical quality controls rather than a prescribed FDA form.

Choose the right eQMS before you map records

A careful record move cannot fix a poor software fit. Before exporting a single folder, make sure the destination fits the quality system you actually run.

If you are still evaluating tools for an early-stage company, start with our guide on choosing an eQMS for a medical device startup. It walks startup teams through the practical questions that settle the software choice. Does the platform support your device class, regulatory pathway, and target markets? Do seat or tier costs fit the number of people who will actually use the system? Does its learning curve match your in-house regulatory expertise or partner support, and what software validation burden are you taking on? Once the destination holds up against those questions, you are ready to set your migration boundary.

Set your paper QMS to eQMS migration boundary before exporting files

Migration headaches can start when a team tries to pour years of effective procedures, superseded revisions, scratch drafts, and open quality events into one import queue. Active documents, historical records, and in-flight work serve different purposes. Pushing obsolete PDFs into an active document-control workflow can clutter your new system and invite workarounds that recreate approvals from years ago, while importing unreviewed folders can hide duplicates behind clean upload totals.

Build a record-family inventory instead of counting folders. For each family, such as standard operating procedures, training records, supplier files, complaints, design records, and change orders, assign a single owner and list every place the records live today. Identify the authoritative record, the applicable regulatory requirement, the retention basis, and one clear disposition for every item, whether that means active import, controlled archive, or a justified exclusion. Keep justified exclusions, such as working copies or superseded drafts, explicitly separate from records that failed to transfer so every source item stays accounted for.

Shared cloud workspaces deserve extra scrutiny before you export. In Google Docs, Drive folders, or tracking spreadsheets, the document body may not capture the whole record. Revision history, review comments that drove a quality decision, email approval threads, embedded attachments, and links to related records can sit outside an exported Word file or PDF, depending on how your team worked. Export behavior varies across tools and destination systems, so test what your chosen export actually preserves before trusting it across a full folder tree.

Check which FDA electronic-record rules actually apply to your files

Moving documents into software does not automatically pull every file into 21 CFR Part 11, and buying an eQMS does not automatically satisfy the rules that do apply. Without a clear applicability assessment, you risk spending extra effort over-controlling reference templates while overlooking the regulated records an investigator will actually examine. Applicability follows the record and its regulated use, not the brand name of the software holding it.

Under 21 CFR 11.1(b), Part 11 applies to records in electronic form that you create, modify, maintain, archive, retrieve, or transmit under FDA record requirements, as well as electronic records submitted to the agency under the Federal Food, Drug, and Cosmetic Act or the Public Health Service Act. The regulation excludes paper records that are simply transmitted electronically, yet that exclusion is not a blanket pass when you maintain the electronic file as your regulated record. Document the underlying FDA record requirement for each record family and state whether you rely on the electronic copy before locking in your workflow.

Where closed-system controls apply, 21 CFR 11.10 requires procedures and controls designed to protect authenticity, integrity, and appropriate confidentiality. Those controls include system validation for accuracy, reliability, consistent intended performance, and the ability to spot invalid or altered records, along with accurate and complete human-readable and electronic copies for inspection, protected retrieval across the retention period, authorized access, and secure computer-generated time-stamped audit trails where changes never obscure earlier entries. A vendor brochure cannot demonstrate those controls for your configured workflows and migrated data on its own.

Record content matters just as much as system controls. Under 21 CFR 820.10(a), applicable medical-device manufacturers document a quality management system that complies with incorporated ISO 13485 requirements and the remaining applicable provisions of Part 820. Current 21 CFR 820.35 supplements ISO 13485 Clause 4.2.5 with specific required fields for particular records, including complaint details, device identifiers, unique device identifiers (UDIs) or universal product codes (UPCs) where applicable, investigation rationale, corrective actions, and complainant replies, along with defined servicing-record details and UDI capture.

If a flat import drops required device identifiers, the migrated record loses information the regulation calls for even when every row imports without an error message. Flattening complaint evaluations into a single notes field may still keep the text, yet you should test whether reviewers can still locate, read, and tie that evaluation back to the right complaint cleanly. Our medical-device complaint records guide under QMSR lays out the evidence that complaint files need to keep connected.

Preserve approval history without rewriting the past

Today's import verification is not yesterday's approval, and blurring the two can undermine confidence in your migrated records. When a cutover deadline gets tight, it is tempting to let a quality administrator click approve on legacy procedures so every document shows an active status in the new eQMS. That shortcut can stamp the administrator's name and this week's date onto an older decision, obscuring who actually approved the procedure and when it took effect.

Where Part 11 governs signed electronic records, 21 CFR 11.50 requires signed records to clearly indicate the printed name of the signer, the date and time of execution, and the meaning of the signature, such as review, approval, responsibility, or authorship, including in human-readable displays and printouts. 21 CFR 11.70 requires signatures to remain linked to their records so they cannot be excised, copied, or transferred to falsify a record by ordinary means. Those provisions do not mandate one universal migration mechanism, yet they draw a sharp line around honest historical preservation.

Keep original approval evidence associated with the exact source revision, and record today's import check as a separate verification entry with its own verifier, date, and scope. If the new eQMS cannot store a legacy approval field faithfully, document that limitation in your migration record and define how your protected original or controlled archive supplies the underlying proof. Never invent a missing signer, turn an uncertain month into an exact timestamp, or assume a scanned PDF of a wet-ink signature counts as a newly executed electronic signature.

Prove the mapping with a trial batch before moving everything

A trial migration earns its keep when it catches missing appendices, broken supplier links, and ambiguous statuses across ten tricky records before you repeat the same defect across five hundred. Testing one clean, text-only procedure proves very little. Record moves can fail at the edges, where a document carries attachments, a supplier assessment points to external certificates, an obsolete revision moves to archive, or a change order is still waiting for final sign-off.

Select a deliberate trial set that exercises every format, revision pattern, attachment type, cross-record relationship, and approval state you expect to migrate. Write down the checks and acceptance criteria before running the trial so you cannot quietly lower the bar after seeing the results. Explain your verification coverage based on record risk and file-conversion complexity rather than copying an arbitrary sampling percentage from a generic vendor checklist.

The fictional acceptance worksheet below shows the level of detail worth capturing before you trust a full import. Every identifier, defect, and outcome in this table is illustrative, not a customer record or a regulatory acceptance rule.

Source record and dispositionDestination and checkTrial result and next decision
SOP-014 revision 3, current approved procedure, active importDocument D-014; verify complete content, revision, status, and source approval evidence; test authorized retrievalBody and revision match, yet one appendix is missing. Exception EX-01 blocks acceptance of this record until you restore the appendix and recheck the record
SOP-014 revision 2, obsolete procedure, controlled archiveArchive A-014-2; verify legibility, revision identity, approval evidence, and a retrieval link from the mapping registerRetrieval succeeds for the designated reviewer. Retain under documented archive and retention arrangements
Supplier assessment SA-08 with two attachments, active importAssessment Q-208; verify both attachments, supplier association, and approval evidenceBoth attachments arrive intact, yet the supplier link points to the wrong entity. Exception EX-02 remains open until you fix the mapping and rerun the affected checks
Change CH-021 awaiting approval, in-flight workKeep the authoritative workflow in the source system until the approved transition pointDo not claim a completed approval. The owner records how the eventual decision and resulting revision will enter the destination

For your real register, add columns for source path or URL, destination ID, format-conversion notes, verifier, verification date, evidence link, and exception status. Look closely at that third row too. Supplier files stay easier to review and defend when assessments, certificates, and approval scope remain linked to the right supplier record rather than sitting loose in a folder, a structure we walk through in our medical-device supplier qualification guide.

When you scale from the trial to full reconciliation, define your counting unit before comparing totals. A single quality record can include multiple PDFs, appendices, and revisions, while a single destination object may bundle several files, so matching file counts can hide missing pages or duplicate entries. Account for every source item across four buckets, imported records, controlled archives, justified exclusions, and unresolved failures, then follow those totals with hands-on checks for legibility, status, cross-record links, and user retrieval.

Approve cutover on evidence rather than a calendar date

Cutover is a controlled quality decision with an accountable owner, not the afternoon the bulk import finishes. Post-migration confusion can arise during an overlap window when one person edits a procedure in Google Drive while another approves a newer revision inside the eQMS. Naming the single authoritative system of record for each record family, paired with a freeze point and clear rules for in-flight changes, helps prevent parallel versions from diverging while the team transitions.

Use this cutover checklist as a practical transition aid alongside your applicable system-assurance and quality procedures, adapting each item to your records and risk profile.

  • Name one decision owner for cutover approval and a specific owner for every open exception.
  • Reconcile each record family across imported items, controlled archives, and justified exclusions, backed by objective evidence.
  • Resolve open exceptions or evaluate them formally against your pre-set cutover criteria without quietly turning a failed criterion into a pass.
  • Capture final delta changes created after the trial or freeze point, including new approvals, revised documents, and newly opened quality events.
  • Test live role permissions for authors, reviewers, approvers, and read-only users, and train the team on how the new workflow replaces the old one.
  • Lock down and protect source originals and controlled archives, then verify the exact retrieval paths your team expects to rely on.
  • Define rollback triggers, reversion authority, and a written method for preserving work created after cutover. Blindly restoring yesterday's backup can erase today's approvals and quality decisions.

This checklist supports a controlled operational switch, not a complete validation protocol or a universal legal mandate for a rollback plan. Keep it paired with your documented assurance and record-control procedures.

Protect archive access and originals after the team moves on

A record that sits in storage when your team cannot retrieve it six months later during an audit is not a completed migration. After the implementation push ends, team roles can shift, legacy cloud subscriptions come up for renewal, and the person who built the mapping spreadsheet may move on to other work. Without periodic checks, broken archive links or closed user accounts can leave records unavailable when you need them for an audit.

Store your mapping register, trial verification records, and exception decisions under document control so future quality leads can trace how legacy files entered the eQMS. Re-test archive links and read permissions whenever you adjust user groups or retire a legacy folder.

Do not delete paper binders or original electronic files simply because an import completed cleanly. Retention periods and conversion rules depend on the record family, applicable regulations, and your documented retention arrangements. Protect historical files and audit trails so they stay legible and retrievable long after a source subscription expires or a colleague leaves the company.

Sources and further reading

Questions before you approve the move

Check the evidence before approving your migration.

No. Separate records that need active workflows from historical revisions that belong in a controlled archive with protected storage and tested retrieval. Document your retention basis and keep a clear link from the mapping register to the archived file rather than treating non-import as permission to discard history.

A fixed percentage on its own does not justify your verification coverage. Define the record population, file-conversion steps, and failure risks first, then design targeted checks that can actually catch missing appendices, broken links, or altered metadata alongside full count reconciliation.

No. Never record a present-day administrator signature as a historical approval. Keep original approval evidence tied to its source revision, log migration verification separately with today's verifier and date, and handle missing historical details as documented exceptions instead of reconstructing them from memory.

A vendor package can serve as a useful input, yet you still need to check what it actually covers and assess any gaps tied to your configured workflows, intended use, and migrated records. Where 21 CFR 11.10(a) applies, validation concerns accuracy, reliability, consistent intended performance, and the ability to discern invalid or altered records in your actual setup.

Do not close an open quality event just to make the import tidier. Assign its authoritative location, named owner, and transition plan so open investigations, evidence, and pending approvals move cleanly without claiming work is finished before it actually is.

Test your acceptance worksheet against QMS Plus

Bring a handful of your real procedures, linked supplier records, and legacy approvals when you evaluate QMS Plus, our verified eQMS. Check how the migration path preserves content, history, and retrieval before you commit to a cutover date.

About the author

Dr Spencer Todd is the CEO and co-founder of Dovetail, a regulatory partner for medical device companies. Before founding Dovetail, he spent years at the FDA and as a medical device consultant.