The Scenario
An insurance firm is migrating its client management workflows to a modern SaaS platform. You need to map customer profiles from the legacy SQL database table (`TBL_CLIENT_MASTER`) to the new REST API registration payload (`/api/v1/customers`). The systems use different field names, date formats, and validation constraints.
The Brief
Create a detailed source-to-target data mapping document. Map at least 15 fields (including names, addresses, contact details, policy types, and status flags). Define transformation rules for data types, formatting, and default values.
Deliverables
- A data mapping spreadsheet/table: Legacy Field Name → Legacy Type → Target JSON Key → Target Type → Transformation/Validation Rules.
- JSON payload example of the target schema after transformation.
- A field-level data dictionary detailing validation constraints (e.g. regex for emails, phone numbers, state abbreviations).
- A mapping exception playbook detailing what to do if mandatory fields are null in the legacy source.
Submission Guidance
Present the mapping grid using a clean Markdown table. Provide validation rules and JSON examples in code blocks.
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.