Migrate from Salesforce Sales Cloud to Mailchimp

Salesforce Contacts migrate to Mailchimp Audience Subscribers using Email as the dedupe key. We map FirstName, LastName, and Email directly. The HasOptedOutOfEmail flag maps to Mailchimp's unsubscribe status for GDPR and CAN-SPAM compliance. The Account Name maps to a custom merge field or COMPANY tag if the customer specifies preserving the account relationship. The Account Contact Relation junction is resolved before migration: each Contact with multiple Account relationships receives a tag for each related Account Name.

Salesforce Leads migrate to Mailchimp Audience Subscribers as a separate pass after Contacts. Leads with an existing converted Contact (already migrated as a Subscriber) are skipped during the Lead pass to prevent email-based duplicates. We map Email, FirstName, LastName, LeadSource, and Status. The original Lead Status values are preserved as a tag (e.g., Open-Converted, Working-Contacted) for segmentation in Mailchimp.

Salesforce Campaigns are evaluated for Audience strategy. If the org uses one global marketing list, all Campaigns map to a single Mailchimp Audience. If the org maintains distinct audience segments by region, product line, or membership tier, each Salesforce Campaign becomes a separate Mailchimp Audience. We make this determination during scoping based on Campaign Type and the customer's segmentation requirements. Campaign Status and Start Date map to Mailchimp Audience settings and campaign archive status.

Salesforce Campaign Members link individual Contacts and Leads to Campaigns. We import Campaign Members as Mailchimp Tags on the matching Subscriber, with the Campaign Name as the tag value. This preserves which campaigns a subscriber participated in without requiring separate Mailchimp Audiences per campaign. If the customer uses Campaign Member Status (Sent, Responded, Opened, Clicked), we create sub-tags using campaign_status format for finer segmentation.

Salesforce custom fields (Custom__c) on Contact and Lead map to Mailchimp Merge Fields subject to Mailchimp type constraints. Text fields map to Mailchimp text merge fields, number fields to number merge fields, and date fields to date merge fields. Phone and address fields map to the corresponding Mailchimp phone and address merge fields. Salesforce picklist fields map to text merge fields with the original picklist values preserved. Boolean fields map to Mailchimp dropdown merge fields with Yes/No options. Fields that exceed Mailchimp's 40-character merge field name limit are truncated or renamed during scoping.

Salesforce OwnerId on Contact and Lead represents the assigned sales rep. We import the Owner's Full Name and Email as a Mailchimp tag on the Subscriber record (e.g., Owner: [email protected]). This preserves which Salesforce user owned each contact without creating separate Mailchimp user accounts. The Owner lookup requires the User record to exist in Salesforce; we validate Owner IDs during data audit before migration begins.

Salesforce Tasks, Events, and EmailMessages are individual engagement records with per-interaction timestamps, body content, and disposition codes. Mailchimp does not store individual email engagement as subscriber records; it stores aggregate campaign open, click, bounce, and unsubscribe rates per campaign. We do not migrate individual engagement records into Mailchimp. We deliver a written engagement inventory listing the total count of Tasks, Events, and EmailMessages per Contact and Lead so the customer's team has a full record of what existed and can decide whether to retain Salesforce in read-only mode for historical activity reference.

Salesforce Workflow Rules, Process Builder processes, Flow automations, and Sequences are automation code that does not migrate to Mailchimp Automations. These two platforms use fundamentally different automation models with different trigger types, action sets, and branching logic. We deliver a written inventory of every active Salesforce automation with its object, trigger condition, actions, and a recommended Mailchimp Automation equivalent (e.g., welcome series, abandoned cart, re-engagement). The customer's team or a Mailchimp implementation partner rebuilds these post-migration.