Zintara contact export field mapping: understand what the CSV contains

Define the decision

The reviewed export contains Name, Email, Company, Title, Status, Score, Tags and Last Activity. It is not a full database dump and does not include every custom field, campaign enrollment or message history.

Work through the procedure

1. Inspect the exact header row from the current deployment.
2. Map each field to a destination type and record transformations.
3. Handle pipe-separated tags deliberately.
4. Preserve spreadsheet formula escaping instead of stripping it blindly.
5. Compare a synthetic exported record with its destination representation.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

Name → display name, not automatically first and last name
Email → matching candidate, subject to destination policy
Tags → split on the documented pipe separator if appropriate
Last Activity → descriptive activity text, not a guaranteed timestamp

Read the result

The mapping avoids silent semantic changes. Splitting every display name on the first space or treating activity text as a date can corrupt a seemingly successful import.

Check before moving on

1. Check rows with commas, quotes and line breaks.
2. Document fields absent from the export.

Limits and next action

Use a separate approved method when stable IDs, custom fields or history are required. Do not claim a reversible full-fidelity migration from this CSV alone.

Source: Zintara implementation and product context