Data Migration — Bug Tracking

Findings raised while migrating legacy data into the new platform, with the account used to reproduce each one.

Where the migration breaks most often

In-flight applications are by far the most fragile part of the migration. An application that was still moving through the legacy workflow when the data was cut over — typically Pending Modification or Pending External Approval — carries workflow state that has no direct equivalent in the new platform, so it lands without its current approval node, its pending task, or the form snapshot the customer was asked to correct. Completed and rejected applications migrate cleanly; the in-flight ones need to be re-checked case by case after every migration run.

Status Summary

Click a card to filter the list below.

All items

#GroupItem StatusAccount

Legend

DoneMigration issue fixed and verified against the migrated data.
TodoStill open — either not started or waiting for the migration to be re-run.
In ProgressBeing worked on right now.
Pending MigFix is ready; waiting for the next migration run to confirm it on migrated data.
Pending DeveloperHanded to a developer; the fix is being built or is waiting for deployment to be verified.
Known IssueAccepted difference between the legacy and the new system — no change planned.
GroupHeading row for a set of related items; the tracked state sits on the items underneath it.

UMC — NMA data migration. Internal working document.