Every inspection software evaluation reaches the same uncomfortable question: what happens to thirty years of history? The readings live in spreadsheets with local naming conventions, scanned reports, a retired database or two, and the memory of one inspector who is close to retirement. Teams sometimes conclude the history is too messy to move and start fresh. That decision quietly discards the corrosion rates, and with them the basis for every interval on the unit.
What actually has to survive
A migration succeeds or fails on three properties, none of which is "the files came across":
- Identity. The reading taken at "E-101 N2 CML-4" in 1998 must land on the same location the 2026 reading lands on. Equipment renames, re-tags, and drawing revisions all threaten this mapping, and it is the mapping that makes a corrosion rate real.
- Units and context. A 0.412 without units, instrument, or temperature context is a number, not evidence. Migration has to carry the metadata that makes readings comparable across decades.
- Provenance. The record should say where each historical value came from: the source file, the page of the scanned report, the original inspector where known. When an auditor questions a rate, the answer traces back to a document, not to "the migration".
A staging approach that works
The pattern that holds up across programs is stage, verify, then commit:
- Inventory the sources before touching data: spreadsheets, PDFs, databases, and their owners.
- Map identities first. Build and review the equipment-and-CML crosswalk as its own deliverable. This is where engineering judgment belongs; everything after it is mechanics.
- Stage with provenance. Load into a staging area where every value keeps a pointer to its source artifact.
- Verify against the field. Spot-check staged history against physical CML markers and recent readings before anything becomes the system of record.
- Commit, and freeze the sources. Once committed, the legacy files become read-only references, not parallel truths.
The question to ask any vendor
Ask to see a historical reading in the live system and then ask: show me where this number came from. If the answer is a source document on screen, the audit trail survived the move. That is the bar we hold intelliSPEC to, and the one your program should hold for any platform, including ours.
