Migration playbook · GAGEtrak

The GAGEtrak Escape Plan: out in one afternoon.

An afternoon is a reasonable target for preparing and checking a small GAGEtrak export, not a promise to replace a regulated system. Start with a few known gages. Export the register and history separately, map the asset columns, and verify the counts before treating anything as migrated. The CaliberOS import wizard is planned; the beta pilot includes help reviewing an export for your first 100 assets.

1. Decide what moves and back up the original

Ask the register owner to back up GAGEtrak and confirm the copy can be opened. Write down the version, site, export time, and applied filters. Choose an initial group with an active gage, a retired one, several serial numbers with leading zeros, and at least one instrument that has multiple calibration events. Include an unusual interval so you can see whether the export preserves its unit.

Split the inventory into three deliverables: an asset register, calibration history and measurements, and the original certificates or attachments. Keep the untouched source files and approved backup separate from your working copies. If the pilot only moves asset records, the archive must still let your quality team retrieve the other evidence.

2. Export the asset list and history to separate CSV files

In your edition, use a gage detail or inventory view for assets and an appropriate calibration detail or history report for events. Select fields that identify each gage and event, and record which date range the report covers. Export data directly to CSV if your view supports it. In the GAGEtrak 7.0.5 Report Viewer, the documented Output To options include Excel; export to Excel and save a data-only copy as CSV when needed.

Inspect both CSVs as text before opening them in a spreadsheet. Keep Gage IDs and serials as text, use one header row, and write dates unambiguously as YYYY-MM-DD in the working files. Preserve a gage-to-event key and, when available, a source event ID. Export certificate PDFs and attachments separately; a CSV is not a backup of those documents or signatures.

3. Map the asset columns before using the planned wizard

Use the sample below to prepare a destination mapping, not as a list of fields your report is guaranteed to export. Older and newer GAGEtrak layouts vary. For example, a report may contain a calibration frequency and a separate unit of measure. Copy a whole-month interval only if it accurately represents your approved schedule. Do not turn 90 days, usage cycles, or end-of-month instructions into approximate months without approval.

The planned CaliberOS import wizard would take a header row, let you match columns to the asset register, and show rows that need review. That workflow is not available today: prepare the mapping with the pilot team and use supported entry for test assets. The current register does not import event history or link archived certificates to a migrated asset.

Sample column mapping
GAGEtrak fieldCaliberOS fieldWhat to check
Gage IDAsset tagPreserve leading zeros. Check case-insensitive duplicates across the destination workspace.
Gage S/NSerial numberKeep as text. Do not use the model number or report row number as a serial.
Current LocationLocationKeep the site and specific area when a location name is shared.
Make / ModelMake / ModelUse separate columns if available; do not guess a missing value.
Calibration Frequency + UOMInterval (months)Only map an approved whole-month interval. Hold exceptions for review.
Next Due DateNext due dateUse the actual source due date; retain any overdue date rather than moving it forward.
Calibration history / certificateSeparate controlled archiveKeep the old Gage ID and event key with the original records. Not an asset field.

4. Reconcile counts and spot-check due dates

Record the gage count in the source, the number of data lines in the export, the number of distinct gage keys, and the number approved for entry. After a test load or manual pilot entry, reconcile the number created, skipped, and held. If a duplicate was deliberately excluded, keep both its key and the reason. A total that happens to match can still hide two instruments swapped under the same tag.

Compare a handful of asset tags, serials, statuses, locations, and due dates side by side. Count history separately; compare events per gage and retrieve a certificate from its archive reference. With the due-date calculator, you can independently check an asset on a simple month-based schedule, but never override a source date on that calculation alone.

5. Call the sample done only after someone else can use it

Ask a technician who did not prepare the files to find a gage and confirm its due date. Ask the quality lead to retrieve a historical calibration and its certificate from the retained source. Note which reports and permissions remain in GAGEtrak. A pilot is done when both people can complete their tasks, all count differences are resolved, and there is an owner for any exceptions.

For a full cutover, plan a short freeze or a final export of changes and decide who can roll back. Keep the legacy records accessible until your validation and retention requirements are met.

References: GAGEtrak Pro 8 introductory guide · GAGEtrak 7.0.5 Report Viewer user guide.

FAQ

Frequently asked questions

Can I move out of GAGEtrak in one afternoon?

You can often prepare a small sample in an afternoon if permissions, backups, and clean reports are ready. Full migration, validation, and archive review may take longer.

Does every GAGEtrak version export directly to CSV?

No. Check your version and report. For example, the 7.0.5 Report Viewer documents Excel output; you can convert a clean data-only copy to CSV.

Is the CaliberOS import wizard available today?

No. The wizard is planned. The free beta pilot includes help reviewing an export for the first 100 assets; do not assume an automated import of history or certificates.

Should I combine assets and calibration events in one CSV?

Keep them separate and link them by source Gage ID. Several events can belong to one gage; combining rows risks creating duplicate assets.

Start with a sample GAGEtrak export.

Join the free beta waitlist to discuss what can move in your first group of assets.

Join the waitlist