Zintara CRM CSV handoff: preserve exclusions and define the destination action

Define the decision

A CSV handoff transfers a snapshot. It does not continuously synchronize opt-outs, ownership, replies or deletions. Decide whether the destination should create contacts, update existing ones or hold records for review before exporting.

Work through the procedure

1. Define the purpose and approved recipient system.
2. Export only the required contact subset.
3. Map columns and choose the destination’s duplicate policy.
4. Review suppression and eligibility outside the ordinary descriptive fields.
5. Test with synthetic rows, then reconcile counts and rejected records.

Worked example

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

Source columns: Name, Email, Company, Title, Status, Score, Tags, Last Activity
Destination decision: update existing contact by reviewed email match
Separate control: excluded contacts remain ineligible for outreach
Export time recorded as the snapshot boundary

Read the result

The handoff should state what will not remain synchronized. A later unsubscribe in Zintara needs an explicit route into the destination if that system can also send.

Check before moving on

1. Protect the exported file and delete temporary copies under the organization’s retention process.
2. Check formula-escaping behavior when opening CSV in a spreadsheet.

Limits and next action

Do not describe this as a native CRM connector or complete backup. The current export omits some identifiers and custom context needed for a lossless round trip.

Source: Zintara implementation and product context