CSV column mapping for outreach: verify meaning before import

Define the decision

Exports use similar labels for different data. Name may mean a person, company or account owner. A technically successful import can therefore create unusable personalization. A mapping review should end with a saved contact that means what the source author intended, not merely a green completion badge.

Work through the procedure

1. Inspect several rows, including a missing name and a company containing punctuation. Identify the column with the recipient's actual email address.
2. Map person and organization fields separately. Preserve a full name when reliable components are unavailable rather than guessing a split.
3. Use deliberate custom keys for additional context. Avoid collisions with standard fields and labels that conceal uncertain research as fact.
4. Import a reviewed sample when practical, inspect saved records and preview mapped fields before processing the broader list.

Worked example

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

Work email → email
Contact given name → first name, if supplied
Account name → company
Account owner → internal context, not recipient name
Research note → custom field after relevance and accuracy review

Read the result

The account-owner row is a common trap: it may contain your colleague's name rather than the prospect's. A header-only review misses that. A research note also should not automatically become an opening sentence. Mapping stores data; copy review determines whether the data can support a truthful message to this recipient.

Check before moving on

1. Confirm a saved email exactly matches its source row.
2. Preview names with accents and multiword company names.
3. Ensure an unmapped column is intentionally omitted rather than expected by a later template.

Limits and next action

Zintara requires an email column mapping in its CSV processing path. Mapping does not verify that an address belongs to the intended person or that outreach is appropriate. Preserve the original source and inspect validation results before considering the import launch-ready.

Source: Zintara product and contact workflow context