The Scenario
A South African company is migrating from a 15-year-old HR system to a modern cloud HRIS. The legacy system has 40+ tables with inconsistent naming, undocumented fields, and data quality issues. No documentation exists.
The Brief
Build a comprehensive data dictionary for the migration. Cover field mappings, data transformations, validation rules, and data quality issues.
Deliverables
- A data dictionary for at least 5 key tables: Field Name, Data Type, Description, Source (legacy), Target (new), Transformation Rule
- A data quality report: at least 5 data quality issues found (nulls, duplicates, format inconsistencies) with remediation approach
- A migration validation plan: how to verify data integrity after migration (row counts, checksum, business rule validation)
Submission Guidance
Legacy systems always have surprises: fields repurposed for unintended data, business logic embedded in field values, and undocumented codes. Show you expect this.
Submit Your Work
Your submission is graded against the rubric on the right. If you pass, you get a public Badge URL you can share on LinkedIn. There is no draft save, so work offline first and paste your finished response here.