01 · Define the schema
Mark required fields and their destination.
Select the fields your operation requires. A field is mapped in this check only when you mark it captured and enter a destination key. The labels are examples to adapt to your schema.
Your field inventory
Required fields needing review
Mapping decisions to confirm
02 · Plan exceptions
Keep the record usable downstream.
Use these notes for field definitions, duplicate checks and records that cannot be delivered.
Field definitions
Duplicate handling
Delivery failure
How the tool works
A draft for team review.
What is counted
Only fields you mark required are counted. A required field is considered mapped in this draft when its status is 'captured in source' and a destination key is supplied. Blank or repeated keys are flagged for review.
What remains unverified
This is not a schema validation, data-quality score, integration test or proof that records arrive. Check real samples, field types and exception handling with your data and operations teams.
Put the plan to work
Bring the map to a structured-call-record review.
Lead Data Warehouse can discuss consistent inbound capture and approved downstream field mapping at volume.
Put your plan in context
Read a related guide and a worked example →
Review your assumptions with the people who own the next step before configuring a live flow.