Data and migration · ASRR Tech
How do you manage issues found during migration?
Record the issue, source record, impact and owner. Separate blocking defects from improvements that can wait until after launch.
A practical example
A missing customer link blocks follow-up; an old spelling is less urgent.
This is an illustrative situation for assessing your own process.
Checklist for your team
- Describe impact.
- Prioritise issues.
- Verify corrections.
What does success look like?
The launch decision rests on known and assessed discrepancies.
Test this with a recognisable record and have a colleague review the outcome. Note missing information or decisions. Use that finding to improve a working agreement before applying the process more broadly.
Data and migration: the wider process
Migration moves a working process, not just a file. Decide which data is still active and which should remain historical. Define fields and statuses before converting them. Start with a representative sample and have future users review it. Compare record counts and inspect individual records. Agree when changes in the old system stop and who resolves errors. Verify the import options available for your configuration before treating a file as the final handover.