Performance, Security & Governance
Migration can expose performance and governance problems that were hidden by the legacy platform.
1. Performance baseline
Capture before and after:
- runtime
- data volume
- concurrency
- source impact
- refresh latency
- query response time
- storage growth
Do not compare only one happy-path query.
2. Security equivalence
Map:
legacy identity → target identity → role/privilege → space → object/data access → consumer
Validate both positive and negative cases: users who should see data and users who must not.
3. Governance continuity
Preserve or improve:
- ownership
- classification
- lineage
- glossary
- retention
- auditability
- data-quality controls
4. Migration-specific risks
Watch for:
- duplicated data
- duplicated pipelines
- inconsistent semantics
- temporary bypasses becoming permanent
- undocumented shared objects
- over-permissioned migration accounts
5. Architect rule
Security and governance are migration acceptance criteria, not post-go-live cleanup.