Importing

How to import a calibration register from CSV or XLSX

The fastest way to start in GagePilot is to import the register your team already maintains. GagePilot validates each row before it becomes part of the workspace, so you can fix the source data before relying on it for reminders.

GagePilot quality operations team · Last reviewed September 12, 2026
GagePilot instrument register showing six instruments with status filters and export controls12
Instrument register captured from the live GagePilot desktop app. The numbered callouts are explained below.
  1. 1Import a CSV or XLSX register, or add a single instrument manually.
  2. 2Search, filter by status, and export the current register view.

Required fields

FieldWhy it matters
Asset / gage IDA unique identifier used to find the instrument and prevent duplicates.
DescriptionA human-readable name for the instrument or equipment.
Next due dateThe date used to calculate current, due-soon, or overdue status.

Useful additional fields

  • Serial number
  • Manufacturer and model
  • Category
  • Location
  • Owner or assignee
  • Calibration provider
  • Calibration interval
  • Notes

Start with a small import example

Copy these headers and example rows into a blank worksheet to see the structure. Replace the examples with your own instruments and approved due dates before importing your working register. Keep IDs formatted as text if they contain leading zeros.

Asset IDDescriptionNext due dateOwner
CAL-001Digital caliper2026-12-12Quality
MIC-002Outside micrometer2026-09-26Inspection

Prepare the file before uploading

  1. Use one header row and one instrument per rowIn CSV, put the headers on the first line. Keep the instrument rows together: a completely blank row ends the register, so remove blank separators between instruments.
  2. Make dates unambiguousUse YYYY-MM-DD, for example 2026-12-12. A CSV date such as 03/04/2026 is ambiguous. Excel day-first dates may be interpreted as DD/MM/YYYY; review the displayed date warning and confirm the result.
  3. Keep a single register in the import copyFor XLSX files, GagePilot looks for a worksheet with recognized register headers. Review the selected sheet name. Removing instruction and example sheets from an import copy avoids selecting the wrong register.
  4. Check column namesUse Asset ID, Description, and Next due date for the simplest import. Do not include two columns for the same field, such as both Asset ID and Gage ID.

Import steps

  1. Open InstrumentsChoose Import and select a CSV or XLSX file from your computer.
  2. Review the recognized fieldsUse clear headers and keep one instrument per row. The importer recognizes common aliases such as asset ID, gage ID, equipment ID, and instrument ID.
  3. Resolve errors before submittingRows with missing required values or invalid dates should be corrected in the source file and imported again.
  4. Review the registerAfter import, filter by status and check a few records against the source spreadsheet before sharing the workspace with the wider team.

Avoid duplicate records

GagePilot compares asset IDs case-insensitively and can skip existing IDs during import. Keep the asset ID stable when an instrument moves, changes owner, or returns from calibration.

Troubleshoot common import problems

What you seeWhat to check
Missing description or next due dateCheck both the value and the header. In the free workbook, rename Instrument / Gage to Description and Next Due to Next due date in your import copy.
Invalid or ambiguous dateUse a real calendar date in YYYY-MM-DD format. Check last-calibrated dates as well as next-due dates; avoid text such as pending or TBC in date columns.
Fewer instruments than expectedLook for a completely blank row inside the list and confirm which Excel worksheet was selected. Compare the preview count with the populated rows in the source.
Duplicate column headerKeep one column per field. Asset ID and Gage ID map to the same field, even though the headings look different.
Missing owner warningAn owner can be assigned after import. Confirm who will act on due work before relying on reminders.
Follow the free workbook preparation steps

Verify the migration before retiring the spreadsheet

Compare the imported count and a few representative records with the source file. Include an overdue instrument, a future due date, and an instrument with a leading-zero ID if your register uses one. Check description, owner, location, and next due date—not only that the upload succeeded.

  • Keep the original spreadsheet while you resolve any discrepancies.
  • A register import does not attach certificate files or recreate every historical calibration event. Review the calibration history separately and attach evidence to the relevant records.
  • Confirm the selected recipients and lead times before relying on email reminders.
Record a calibration and attach its certificate

Next step for your workflow

Connect this guidance to the working register.

See how GagePilot applies this process to instruments, due dates, records, reminders, and evidence.

See calibration register software

See it in GagePilot

Keep the register, reminders, certificates, and history together.

Start a 14-day trial