Migration Governance, Data Privacy and Data Volume Decisions

Keep this: job aid

Migration governance card

• For each data set: run, report, retain or leave behind. Retaining is not migrating.
• Record every scope decision with owner, advisers, rule, location after go-live and retention period.
• Retention periods and legal holds come from legal, tax and compliance; never guess them.
• Plan the legacy end of life: read-only period, decommissioning decision, tested access, shutdown, destruction.
• Minimize personal data in scope; protect every copy: extracts, staging, mocks, test clients, spreadsheets.
• Design and test blocking and deletion before go-live; clean up migration copies after it.
• One accountable owner per decision; one forum per kind of decision; escalate by impact.
• Keep a decision log; version approved artifacts and change them under control.
• Evidence chain per object: scope decision, approved specification, extract totals, load logs, reconciliation, owner sign-off.
• Opening balances tie to legacy closing balances; migration clearing accounts are zero.