Data & migration8 min read

Incident data migration into Intelex: a practical checklist

Every incident data migration starts the same way. The client says "we want all of it," someone exports fourteen years of records out of a legacy database, and the file arrives with 380 columns and no data dictionary. Six weeks later you are still reconciling injury codes that stopped being used in 2017.

The honest answer is that you should almost always migrate less than the client asks for. A 2011 incident record has close to zero analytical value inside a 2026 reporting model, and forcing it in costs something real: it pollutes your lookup lists and permanently blocks business rules you have not written yet. Worse, it puts records into a system of record that nobody can defend when an auditor asks how they got there.

How far back is worth migrating?

Start from the legal floor, then argue the analytical case on top of it.