eQMS implementation: moving from paper and spreadsheets, step by step

You have chosen an eQMS, or you are close to it. Today your SOPs live as signed PDFs on a shared drive, the training matrix is a spreadsheet that one person understands, deviations are numbered in a logbook and CAPAs are tracked in another workbook with conditional formatting nobody dares touch. The software is the easy part. The hard part is moving a working quality system from one medium to another without losing records, confusing the shop floor or giving your next auditor a gap to pull on. This article is a migration plan for eQMS implementation at a small device or pharma manufacturer: what to bring across and what to leave in an archive, how long the archive must last, how to prove migrated records are intact, the order in which to switch modules on, how to train people, and the questions an auditor will ask about the transition.

Treat the switch as a controlled change

Moving to an electronic QMS changes how you control documents, records and signatures, so it belongs under your change control procedure. Raise a change record, assess the impact and name the cut-over dates. If you need a structure for that assessment, our piece on change control impact assessment covers it.

The regulatory bar for pharma is set in the principle of EU GMP Annex 11: where a computerised system replaces a manual operation, there should be no resultant decrease in product quality, process control or quality assurance, and no increase in the overall risk of the process. Device makers have the equivalent in ISO 13485:2016 clause 4.1.6, which requires the software used in the quality system to be validated before first use, with an approach proportionate to risk. The change record is where you show you weighed that risk before switching, and it is the first thing an auditor will ask for.

What to migrate: current documents, open work and history

The instinct is to load everything so the new system is "complete". For most small manufacturers that is the most expensive and least useful option. Every record you migrate has to be checked, and fifteen years of superseded procedures add nothing an auditor cannot already see in your archive.

A workable default looks like this:

Two decisions need care. The first is how a migrated document is approved. You can either carry its historical approval across as recorded metadata with the signed original attached, or issue it as a new revision in the eQMS and approve it with an electronic signature. The second route gives every live document a clean electronic approval but means a training wave on documents that have not changed in substance. Many companies reissue documents as they come up for their next periodic review and carry the historical approval until then. Whichever you choose, write it in the migration plan so the reason is on record.

The second decision is document numbering. Keep your existing numbers if you possibly can. Batch records, device history records and supplier agreements reference SOP numbers, and renumbering breaks every one of those links. If the new system forces a new scheme, keep a cross-reference table as a controlled record.

Record retention: the archive is still a quality record

Paper files and the old shared drive do not stop being records when the eQMS goes live. ISO 13485 clause 4.2.5 requires records to be retained for at least the lifetime of the device as you define it, and never less than two years from release. For devices on the EU market, Article 10(8) of the EU MDR requires technical documentation and the declaration of conformity to be available for at least 10 years after the last device is placed on the market, and 15 for implantables. For medicines, EU GMP Chapter 4 (4.11) requires batch documentation to be kept for at least one year after the batch's expiry or five years after QP certification, whichever is longer.

So the archive needs an owner, a location recorded in your records procedure, protection against change, and an index. Make the shared-drive folders read-only for everyone except a named administrator, and record that you did it. Annex 11 section 17 expects archived data to be checked for accessibility, readability and integrity, which in practice means opening a sample of files once a year and recording that you could.

Hybrid records need cross-references. If a CAPA was opened on paper and closed in the eQMS, the electronic record should state where the paper part is, and the paper file should say where the rest went. The MHRA GxP data integrity guidance is explicit that references between physical and electronic records must be kept so the full history can be verified throughout the retention period.

Data integrity of migrated records

Annex 11 clause 4.8 says that when data are transferred to another format or system, validation should include checks that the data are not altered in value or meaning. The MHRA guidance adds a warning worth reading twice: the challenges of migrating data are often underestimated, particularly keeping the full meaning of migrated records. Meaning is the trap. A training record that says "trained" has lost its meaning if it no longer says which revision of the SOP the person was trained on.

A proportionate check for a small company has four parts. First, a migration specification: which records, which fields map to which, what happens to attachments and how dates are converted. Second, a reconciliation of counts, so you can show that the 214 effective documents in the old index are the 214 in the new system. Third, a field-by-field comparison on a sample, weighted towards high-risk records such as specifications, batch-related SOPs and training for critical roles. Fourth, a short report that records what you checked, what you found, and how each discrepancy was resolved.

If you scan paper records to replace the originals, the scanning itself needs a documented process that produces true copies. The MHRA definition of a true copy is one verified to carry the same information as the original, including the context, content and structure, and it says organisations should consider the risk of destroying originals. For a small company, the simplest answer is often to scan for convenience and keep the paper.

Spreadsheets are their own problem. Before importing a training matrix or CAPA log, freeze it, archive a dated copy and check it for merged cells, free-text dates, duplicate names and overwritten formulas. Clean the source under a recorded check, never silently during import.

Sequencing the modules

Switching everything on at once means every process changes on the same Monday and every problem lands on the same few people. Follow the dependencies instead.

Document control goes first, because everything else references documents. Training follows, since training assignments are driven by document revisions and roles; our guide to an inspection-ready GMP training matrix covers how to structure the matrix before you load it. Deviations and CAPA come next, as they depend on both, and internal audits last, since audit findings feed CAPA.

Set a cut-over date per module and a rule for it: from that date, new records of that type are created only in the eQMS. Leave a short window, measured in weeks, where open legacy records close out in the old system. Running two live systems for the same record type for months is how the wrong revision ends up on the line, and how a deviation gets logged twice under two numbers.

Plan for downtime too. Annex 11 section 16 expects continuity arrangements if the system is unavailable; for a small site, a controlled paper deviation form and a weekly printed list of current revisions is usually enough.

Training the team

The eQMS changes your procedures, so the procedures need to change first. The SOPs for document control, training, deviations and CAPA should describe the electronic process, and they should be effective on the cut-over date. ISO 13485 clause 6.2 requires training to be provided and its effectiveness evaluated. Training on the new system is training like any other and needs a record.

Make it role-based. A document approver needs to know what their electronic signature means and what happens when they reject a draft. An operator needs to find the current SOP and acknowledge training. A CAPA owner needs to know how to record an action and evidence. Pick one or two people per area as first-line helpers and give them more time with the system before go-live. Check effectiveness by watching people do a real task in the first fortnight; a quiz on where the menus are tells you very little.

What auditors ask about the transition

Notified body auditors and GMP inspectors tend to ask a predictable set of questions about a recent switch. Have the answers in one folder:

1. Show me the change record and risk assessment for moving to the electronic system.
2. How was the system validated, and where is the summary report?
3. What did you migrate, what did you leave behind, and why?
4. How did you verify migrated data were not altered in value or meaning?
5. Where are the records from before the cut-over, and how are they protected for the retention period?
6. Pick an SOP: show me its revision history across both systems.
7. Show me training on the new procedures for the people who use them.
8. What happens if the system is unavailable?

The sixth question is the one that catches people out. If the answer involves three folders and a search, write a short cross-reference into each migrated document's history before the audit does it for you. The internal audit programme is a good place to rehearse it: schedule an audit of the migration itself a few months after go-live.

The takeaway

Migrate what is current, archive what is history and protect the archive for as long as the records must live. Prove the migrated data kept their meaning with counts, a weighted sample and a short report, and switch modules on in dependency order, starting with document control. If you have a change record, a migration report and a clean revision trail for any SOP an auditor picks, the transition becomes one of the easier conversations at your next audit.

If you are planning that sequence now, the InnoQualis platform brings document control, training, deviations, CAPA and internal audits together with an append-only audit trail and EU hosting, so each module you switch on links to the ones before it.