Map CSV columns to a destination template

Load two different layouts

Download the three-contact source and the destination header template. These are original generic examples, not a platform-certified format. Add the source to the CSV Cleaner & Import Checker, then load the destination template and press Prepare column mapping.

Review suggested matches

The tool suggests matches where names differ only in case, spaces, underscores or hyphens. It cannot know that Name should become Full name or that Customer ID means External ID. Select those sources explicitly. Leave empty only when the destination accepts an empty value. Remove a target column only when intentionally leaving that field out of the export.

Choose External ID as the unique key for this generic example. IDs 001, 002 and 003 are distinct strings. If your destination matches by email instead, select Email. A key rule is your instruction; the tool cannot discover the destination’s update policy.

Separate incomplete records

1. Mark Email, Full name and External ID as required. This checks for nonblank text; it does not validate the email syntax or identity.
2. Run the check. Cara has no email, so the clean download is blocked. All three records remain visible.
3. Enable Move missing required fields and repeated-key records into a separate unresolved file and recheck. Two rows remain in the reviewed output; Cara remains in unresolved rows with the reason.
4. Download both files and the report. Confirm the two-row preview, then compare it with the expected mapped result.
5. Download a mapping recipe to reuse the same headers and rules. Recipes contain column names and settings, not customer records. The next source must have the same header layout.

Avoid an unsafe import

Renaming Company to Company name does not create a company association. Converting a field into an ID does not establish that the ID belongs to the destination. The tool keeps strings as strings and does not transform dates, currencies or country codes. Decide these semantics with the destination owner.

A template update can change required fields or accepted values. Review it again rather than trusting an old recipe. For recurring imports, plan a preview, permission checks, audit history and recoverable failure handling with custom data import and integration development. See also how conflicting customer IDs should be reviewed.

Watch the mapping workflow

Silent demonstration using the synthetic source on this page. Workflow transcript: load source and destination headers; explicitly map Full name, External ID and Company name; mark Email required; check and observe the missing-email blocker; separate unresolved records; review the two uncontested contacts; save the mapping recipe.

Download the demonstrated mapping recipe and the demonstrated unresolved row. This recipe marks Email, Full name and External ID required. Review the required-field settings for your destination before reuse.