Appearance
Data mapping worksheet
Template: Copy the tables for each dataset. Validate against the destination system's current specification.
| Field | Value |
|---|---|
| Project | [Project name] |
| Source / destination | [Systems] |
| Mapping version | [v1.0] |
| Owner / reviewer | [Names] |
| Effective date | [YYYY-MM-DD] |
1. Field mapping
| Source field | Source type | Destination field | Destination type | Required? | Transformation / default | Validation |
|---|---|---|---|---|---|---|
| [employee_id] | [Text] | [worker_id] | [Text] | [Yes] | [Trim whitespace] | [Unique, nonblank] |
| [start_date] | [Date] | [hire_date] | [Date] | [Yes] | [Format YYYY-MM-DD] | [Valid date] |
| [status] | [Text] | [employment_status] | [Code] | [Yes] | [Map via lookup] | [Approved codes] |
2. Reference-value translations
| Source value | Destination value | Rule / exception |
|---|---|---|
| [Active] | [A] | [Example only] |
3. Processing rules
- Deduplication key: [Field or composite key]
- Blank value behavior: [Reject / default / preserve]
- Date, time zone and locale: [Rules]
- Invalid-record handling: [Quarantine / correct / reject]
- Unmapped columns: [Drop / retain with approval]
- Reprocessing/idempotency: [How duplicate imports are prevented]
4. Verification and approval
- [ ] All required destination fields mapped
- [ ] Lookup values and transformation rules reviewed
- [ ] Sample records reconciled with expected destination output
- [ ] Rejected-row handling tested
- [ ] Source and destination owners approve mapping
Approvals: [Names, dates]