Migrate from Zendesk Sell to Mailchimp

Zendesk Sell Contacts map to Mailchimp Members in the target Audience. We extract name fields (first_name, last_name), email address, phone, and address fields, and write them to the corresponding Mailchimp Member properties. The Member status is set to subscribed by default; we flag any Contacts with a Do Not Contact or suppressed flag in Sell and set the Mailchimp Member status to unsubscribed or cleaned accordingly. Email addresses serve as the dedupe key during import.

Zendesk Sell Leads map to Mailchimp Members in the same manner as Contacts. Lead source, lead status, and unqualified reason fields migrate as Merge Fields on the Member record. We apply any existing Sell Tags to the Member using Mailchimp's tag API endpoint. Leads that have not been converted retain their source attribution in the migration. Note that Sell Leads and Contacts are separate object types in the source; Mailchimp has no such distinction, so both land as flat Members in the Audience.

Sell Users (sales reps and admins) with email addresses migrate to a separate internal Mailchimp Audience or to a dedicated tag segment. This preserves the internal team list for Mailchimp-based internal communications or team broadcasts if the organization uses Mailchimp for internal marketing. Role and territory assignments from Sell do not map to Mailchimp and are exported as a reference document.

Sell Companies (Organizations) do not map to a dedicated Mailchimp object because Mailchimp has no Company or Organization record type. The company name associated with each Contact or Lead migrates to the FNAME and LNAME merge fields or a custom organization_name merge field in Mailchimp. The existing Sell-to-Mailchimp connector has a documented gap where company name does not populate ORGNAME; we resolve this by creating a custom organization_name merge field in Mailchimp and writing company data from Sell's dbo.organization.name field directly to it during import.

Sell custom field values on Leads and Contacts migrate to Mailchimp Merge Fields. We create Merge Fields in Mailchimp matching the field types from Sell (text, number, date, dropdown, phone, address) and map the values during Member import. Sell custom field IDs must be resolved to field keys during scoping; the Fanatical Labs SugarChimp field mapping reference confirms this as the standard pattern for CRM-to-Mailchimp field translation. Merge fields are audience-specific, so we repeat the mapping per Mailchimp Audience if the customer uses multiple lists.

Sell Tags applied to Contacts and Leads migrate to Mailchimp Tags. We export the full tag taxonomy and apply tags to the corresponding Members via Mailchimp's tag API in a batched import. Tags are used in Mailchimp for segmentation and audience filtering, so the tag vocabulary from Sell carries directly into campaign targeting. Tag-based filtering in Sell Smart Lists maps to Audience Segments in Mailchimp using the same tag logic.

Sell Deals have no Mailchimp equivalent because Mailchimp is an audience and campaign platform, not a sales pipeline tool. We export all Deal records (name, value, stage, owner, close date, loss reason, associated Contact references) as a structured CSV reference document for the customer's admin to review. This preserves the deal history for audit purposes even though it cannot be loaded into Mailchimp. If the customer intends to use a separate CRM alongside Mailchimp post-migration, the Deal CSV serves as a clean import source.

Sell Sequences (cadence-based email automation) do not migrate. As documented in Sell's own support articles, Sequence enrollment state and step history are not exportable as discrete records. We export Sequence metadata (name, step count, cadence type, associated contacts) as a written reference document. The customer's admin uses this to rebuild equivalent Customer Journeys in Mailchimp. Sell Sequences tied to in-progress cadences cannot be resumed in Mailchimp and require rep outreach re-enrollment.