Getting started
How to migrate calibration data without losing history
Migrating calibration data is the part of switching tools that teams dread, and it is why so many quality programs stay on software or spreadsheets they have outgrown. The good news: a calibration dataset is small by modern standards, it has a predictable shape, and the move usually fits in an afternoon once you know the order of operations. This guide walks the migration in five steps: export, registry, history, certificates, verify. It applies whether you are coming from a spreadsheet, GAGEpack, GAGEtrak, IndySoft, or something homegrown.
The three layers of a calibration migration
A complete migration moves three layers of data, and it helps to treat them separately. The first is the asset registry: the list of instruments with their tags, descriptions, serial numbers, locations, and calibration intervals. The second is the calibration history: the record of past events on each instrument, with dates, results, and who did the work. The third is the certificate files: the PDFs from your vendors or your own bench that back those events up.
Most migrations move only the first layer and quietly abandon the other two, which is how an audit question like show me the last three calibrations for this gage ends up answered from a filing cabinet. Axiospec imports all three, and this guide covers each in turn.
Step 1: Export what you have, and keep a copy untouched
Get your data out of the current system first. GAGEpack, GAGEtrak, and IndySoft all export to CSV or Excel, and a spreadsheet already is the export. Pull three things: the instrument list, the calibration event history if your system can produce one, and the folder of certificate PDFs.
Make one copy of the raw export and never edit it. Do all cleanup in a working copy. If anything looks off after the move, the untouched original is your reference for what the old system actually said.
Step 2: Import your asset registry first
The registry goes first because everything else attaches to it. Axiospec's Bulk Import reads your CSV or Excel file, suggests a column mapping from your headers, and validates every row before anything is saved, so you see problems in a preview instead of discovering them later.
Imperfect data does not block you. Soft problems, like an unrecognized date format or a blank optional field, come through as warnings you can fix later; only genuinely broken rows are skipped, and the importer tells you which and why. If a row matches an asset tag that already exists, you choose what happens: skip it, update the existing asset, or stop and review.
Step 3: Bring your calibration history over
History is the layer teams assume they will lose, and the reason many never switch. In Axiospec it is a first-class import: one row per past calibration event, with the asset tag, the date, the result, the technician, and the certificate number if you have one. Each row becomes a real record on that instrument's timeline, not a note pasted into a comment field.
Once history is in, each instrument's next due date is computed from its most recent calibration and its interval, so your schedule picks up exactly where the old system left off instead of restarting from the import date.
Step 4: Attach certificate PDFs in bulk
Certificates do not have to be attached one instrument at a time. Axiospec's bulk certificate upload takes a whole folder at once, matches filenames against your asset tags, and shows you the matches for review before anything is registered. Files it cannot match automatically, you match by hand in the same review screen, and the rest upload in parallel.
Step 5: Verify the move, and undo if something is wrong
Verification is a short checklist, not a leap of faith. Compare instrument counts per site against your untouched export. Spot-check five to ten critical instruments end to end: the due date, the current status, the most recent calibration event, and that its certificate opens. Then skim the Due Calendar for anything obviously wrong, like half the shop coming due the same week.
If a mapping was wrong, you do not hand-fix hundreds of records. Every import lands as a batch, and a batch can be reverted, so the recovery path is revert, fix the file, and run it again. Large imports also resume where they left off if the upload is interrupted, rather than starting over.
Migrating from GAGEtrak, GAGEpack, or GageList
All three export to CSV or Excel, and that export is all the importer needs. Column names differ between tools, but the import wizard suggests a mapping from your headers and lets you correct anything it guessed wrong before a single row is saved.
The pattern is the same regardless of source: export the equipment or gage list first and import it as your registry, then export the calibration event history and import it as history. If your old tool exports certificates as PDFs, bring those in the bulk certificate step. And if the export looks messy, that is normal for a long-lived database; send it to us instead and we will map it for free.
If you would rather not do any of this
Every plan, including the free one, comes with free white-glove migration. Send us your export in whatever shape it is in, and the team maps and loads it for your review. It runs over email, asynchronously, and there is no call to schedule.
If you are still deciding whether to switch at all, start with the live demo. It opens a working calibration program with no signup, so you can see what the end state looks like before you move a single row.
Put it into practice
Import your asset registry in an afternoon, log every calibration to a tamper-evident audit trail, and produce records on demand. Prefer to see it first? Take a self-guided tour with sample data, no signup required.
Axiospec is a documentation and workflow tool. It helps you keep clean, traceable, audit-ready records; certification depends on your own processes, scope, and assessor.
More like this, by email
A short series of practical calibration guides like this one. No spam, unsubscribe with one click.