Make the field map usable
| Source field | Target field | Rule | Owner |
|---|---|---|---|
| Customer code | Customer ID | Required; preserve C-0007 as text; reject repeated IDs for review | Customer records owner |
| Joined on | Registration date | Confirm 03/04/2026 means 3 April before converting to 2026-04-03 | Customer records owner |
| Credit limit | Credit limit (HKD) | A blank is unknown; do not silently change it to zero | Accounts owner |
This map is an example, not a supported import format for a named product. Check your target’s actual field types and import rules. Keep a reference to the source row so a rejected record can be corrected without losing its identity.
Turn each gap into a named task
A team has documented field owners and formats but has not tested a duplicate import or agreed a freeze window. How should the checklist be answered?
Show the worked answer
Mark ownership and formats as defined and checked. Mark the test import and freeze window as not ready. Leave other unverified items unanswered; the result lists their specific follow-up tasks without a readiness score.
An all-yes result only means no gaps were reported for these seven items. It does not establish production safety, access control, backup completeness or compatibility. Verify the actual dataset, target system and recovery exercise before a cutover decision.