Migrate from CRM and Deals for Zendesk to Mailchimp

CRM and Deals for Zendesk Contacts map to Mailchimp Members within a target Audience. Email address is the primary key and dedupe field. First name, last name, phone, and custom fields map to Mailchimp merge fields (FNAME, LNAME, PHONE, and any custom merge fields prefixed with *|). We validate email format and suppress invalid addresses before import to protect Mailchimp audience health scores. Opt-in status migrates to the STATUS field (subscribed, unsubscribed, cleaned). Contacts without email addresses cannot be created as Members and are flagged in the reconciliation report.

Zendesk Organizations map either to Mailchimp tags (if the customer wants segment-based company grouping) or to a COMPANY merge field (if contacts should display the organization name as a flat attribute). We configure this during scoping based on the customer's segmentation strategy. An Organization with multiple Contacts results in multiple Members tagged or fielded with the same company value. Organizations without contacts generate orphaned records flagged for customer review.

Zendesk tags on Contacts migrate as Mailchimp tags on the corresponding Member. Tags are flat string values in Zendesk and transfer directly as Mailchimp tag names. Tag-based automations in Zendesk do not migrate; we deliver a written inventory of tag-triggered automations for the customer to rebuild in Mailchimp automations post-migration.

Zendesk Deals map to no Mailchimp object. Mailchimp has no deal, opportunity, pipeline, stage, or revenue tracking schema. We flag every open Deal during scoping and document its current stage, owner, value, and close date in a written Deal Handoff Report. The customer must choose whether to close Deals in Zendesk before migration, export them to a spreadsheet, or adopt a new CRM post-migration. Deals with a linked Contact can have the Deal value stored as a custom merge field on the corresponding Member if the customer chooses, but this is optional and requires explicit customer approval.

Zendesk Pipelines and their stage definitions have no equivalent in Mailchimp. Stage names, probabilities, and ordering do not transfer. We document the full pipeline structure in the Deal Handoff Report and recommend the customer configure equivalent segments or tags in Mailchimp if pipeline-stage-based email targeting is desired.

Zendesk Activity records (call logs, emails, meeting notes) have no Mailchimp equivalent. Mailchimp tracks email opens and clicks for campaigns it sent, but historical Zendesk engagement data does not carry over. We document the volume of Activity records per Contact in the migration inventory for the customer's awareness. Email engagement history from Zendesk-stored email conversations does not migrate to Mailchimp.

Zendesk support tickets have no equivalent in Mailchimp. Ticket status, priority, requester, assignee, and conversation history do not migrate. If the customer continues using Zendesk Support separately from CRM and Deals for Zendesk post-migration, the ticket object remains in Zendesk and is outside the Mailchimp migration scope.

Zendesk Custom Objects (v2) migrate to Mailchimp custom merge fields or tag groups if the object is simple (a flat record with scalar fields). Objects with lookup relationships to other custom objects do not map cleanly to Mailchimp's flat Member schema and require flattening or decomposition. We assess each custom object during scoping and deliver a written schema mapping showing which fields become merge fields and which relationships are dropped. The destination Mailchimp plan tier (Essentials supports unlimited merge fields; Standard adds tagging and segmentation depth) determines what maps cleanly.