Migrating Your Calibration Spreadsheet to Software: A Practical Guide

You have decided to move your calibration register off the spreadsheet — the decision of when to switch is made. The next question is the practical one: how do you actually move years of equipment records and certificates into new software without losing data, breaking the audit history, or spending a week on it? This guide is the migration playbook for a UK quality team.

The good news is that for a typical SME register — twenty to a few hundred instruments — migration is an afternoon's work, not a project, provided you do one thing first: clean the data before you import it.

The Golden Rule: Clean Before You Import

If you have already weighed calibration software against a spreadsheet and decided to move, the migration itself comes down to one rule: software imports exactly what you give it. This is the single most important thing to understand about migration. If your spreadsheet has duplicate rows, three different date formats, and an instrument that appears once as "Micrometer 0-25mm" and once as "Mic 25mm," the new system will faithfully reproduce all of that. The new tool does not clean your data; it inherits it.

So the first step is not import — it is cleanup. Before you export anything:

• Remove duplicates. The same instrument entered twice is the most common spreadsheet artefact. Resolve to one record per instrument.
• Standardise dates. Pick one date format and apply it across every date column. Mixed formats are the most frequent cause of an import putting a due date in the wrong year.
• Fill or flag blank required fields. Every instrument needs at least a unique identifier and an interval. Blank serial numbers or missing intervals either get filled now or get flagged so you know what is incomplete after import.
• Standardise names. Make instrument types, locations, and calibration providers consistent, so the imported register groups and filters cleanly.
• Resolve split identities. Any instrument that appears under two different identifiers gets merged to one.

An hour of cleanup here saves a day of confusion later. It is also a quietly valuable audit of your own register — you usually find a few instruments that should have been retired, and a few that were never properly recorded.

Decide What History You Are Bringing

A subtle migration decision: are you importing the current state, or the full history? Most spreadsheets hold only each instrument's latest calibration date and next due date — not the full run of past calibrations. Decide up front which you are doing:

• Current state only — fastest. You import each instrument with its latest calibration date, due date, and interval, and start the full history from now. The older certificates stay in their existing folder as historical reference.
• Full history — more work, but cleaner long term. You bring across past calibration dates where you have them and upload the historical certificates against each instrument, so the complete history lives in one place from day one.

Neither is wrong. For an instrument fleet with good records, full history is worth it. For a messy archive, current-state-forward plus a clearly-labelled folder of old certificates is a pragmatic choice. The point is to decide deliberately rather than discover the gap at the next audit.

How CSV Import Works

The mechanism itself is simple. You export your cleaned spreadsheet to CSV — a plain comma-separated file that every spreadsheet tool can produce. The software then maps the CSV's columns to its own equipment fields: serial number, instrument type, manufacturer, location, tolerance, calibration provider, interval, and due date. You confirm the mapping, run the import, and your register is live.

Then comes the certificates. The CSV brings the records; the certificate PDFs are uploaded and attached to each instrument so the evidence sits with the record. This is the step that turns a list of instruments into an audit-ready register — a certificate-to-instrument link the spreadsheet-and-folder system never enforced.

For an accredited laboratory, there is one extra consideration. ISO/IEC 17025:2017 §7.11 requires that an information management system is validated for functionality before introduction — so part of adopting new software is confirming, and recording, that it produces correct outputs for your use (for example, that an imported due date and a generated report read correctly). For an ISO 9001 manufacturer the bar is lower, but checking the import landed correctly is just good practice either way.

After the Import: Confirm and Move On

Once imported, spot-check. Pick a handful of instruments and confirm their key fields and due dates came across correctly. Confirm the certificates are attached to the right records. Set the reminder lead time so the recall system starts working. Then — and this matters — stop maintaining the spreadsheet. Running both in parallel "just in case" is how data diverges and the migration's benefit is lost. Once you have confirmed the import, the software is the system of record.

And confirm the exit before you settle in: check you can export everything — records plus certificate PDFs — back out as CSV and files. Your compliance evidence should never be locked to one vendor, and the time to verify that is at the start, not when you eventually want to leave.

How CalProof Fits

CalProof is built for this migration. You import your cleaned register by CSV, mapping your columns to the equipment fields, and upload your existing certificates against each instrument so the history is preserved, not just the current state. From there the recall reminders, audit trail, and compliance reporting run automatically. And you can export the whole record set — CSV plus the underlying PDFs — back out at any time, so there is no lock-in on your audit evidence. A typical SME register is live in an afternoon.

GBP pricing from £29 a month. No per-user fees on Pro and above. UK data hosting. No long-term contract.

To see the shape of the output before you migrate, the sample audit pack is ungated and downloads as a single PDF.

Sources

• ISO/IEC 17025:2017 — General requirements for the competence of testing and calibration laboratories (§7.11 control of data and information management)
• ISO 9001:2015 — Quality management systems — Requirements (Clause 7.1.5)

This guide applies to UK manufacturers and laboratories under ISO 9001 or ISO/IEC 17025. It is general guidance based on the published standards; the requirements that apply to your organisation depend on your certification scope and your auditor's interpretation. Verify against your certification body or UKAS assessor. This is not legal or compliance advice.