How do you test a control metadata migration?

Test both completeness and accuracy. Compare record counts before and after migration, identify blank required fields, scan for invalid values, reconcile key dashboards, confirm control-to-risk and issue links, and sample individual controls to verify that values mapped correctly.

For higher-risk changes, retain the baseline export, mapping table, test evidence, exception log, approval, and post-change validation. The goal is to show that the control library remains reliable after the change.