Define ownership and meaning
Create a business glossary and data asset inventory. For each critical field, assign a domain and steward who can explain the target meaning.
Classify sensitive data conservatively
Use heuristic suggestions only as a starting point. Real customer records demand a customer-approved policy, correct masking and data residency restrictions.
Trace every approved change
Track mappings, rule versions and schema revisions so a business owner can understand why a record moved or was rejected.
Separate preview from enforcement
Local stewardship decisions are ephemeral demonstration events. A production policy must be enforced server-side, tenant-isolated and supported by real authorization and audit.
Frequently asked questions
What is data lineage in a migration?
Lineage records the relationship between source fields, transformations and target fields. Conceptual lineage helps with design, but production proof also needs observed job and target evidence.
Can YapGovernance enforce retention and access policies now?
The public preview provides local glossary, heuristic classification and stewardship review examples. Production-grade retention, authorization and durable signed approvals remain under development.
Why does schema drift matter?
An added, removed or renamed column can silently affect a mapping. Drift checks should trigger documented review before a migration job is rerun.