Migrate from Mailchimp to Salesforce Sales Cloud

Each Mailchimp Audience maps to a Salesforce Campaign. The Audience name becomes the Campaign Name, and Audience settings (opt-in workflow, double opt-in) are noted as Campaign Type and CRM opt-in fields. All contacts within the Audience enroll as Campaign Members linked to the Salesforce Campaign. We resolve the Salesforce Contact or Lead record by email match before creating the CampaignMember. Audiences without any contacts still generate an empty Campaign record for historical reference.

Mailchimp Contacts with a sales-qualified status (any contact the customer has flagged as a customer, client, or prospect in a CRM context) map to Salesforce Contact tied to an Account. Unqualified marketing contacts map to Salesforce Lead. We compute the split using a combination of Mailchimp contact tags (customer, client,prospect), segment membership, and the customer's guidance during scoping. All contacts receive the original Mailchimp email status (subscribed, unsubscribed, non-subscribed) mapped to Salesforce HasOptedOutOfEmail and a custom field mailchimp_status__c for audit.

Mailchimp subscribed status maps to HasOptedOutOfEmail = false. Unsubscribed maps to HasOptedOutOfEmail = true. Non-subscribed maps to a custom field mailchimp_non_subscribed__c = true with HasOptedOutOfEmail = false (they have not opted out but are not actively subscribed). Cleaned addresses (bounced) map to HasOptedOutOfEmail = true and a custom bounce flag. This prevents re-importing suppressed addresses into Salesforce as active contacts.

Mailchimp Tags migrate as Salesforce Topics. Each unique tag name generates a Topic record, and the tag-contact association becomes a TopicAssignment record linked to the Contact. We preserve all tag names and contact associations. If the customer prefers, tags can alternatively map to a multi-select picklist field on Contact for simpler filtering without the Topics relationship.

Mailchimp Segments are dynamic filter definitions that Mailchimp evaluates at send time. These do not export as static contact lists. We export the segment rules (field, operator, value) as structured JSON in the handoff document. For each segment, we either (a) generate a Salesforce Campaign with Campaign Members added as static records matching the segment criteria, or (b) document the equivalent Salesforce Report filter criteria so the customer's admin can recreate the segment as a List View or Report.

Mailchimp Groups require their parent Group Category to exist first. We export both Category and Group and map them as a Salesforce Campaign (Category) with related Campaign Members (Group membership). Group membership per contact is preserved as CampaignMember Status values named after the group.

Mailchimp sent campaign records (one record per email send) map to Salesforce Campaign records. The Mailchimp campaign subject line becomes Campaign Name, send date becomes StartDate, recipient count becomes NumberOfLeads, and open rate/click rate are stored in custom numeric fields. This preserves the email marketing history as Campaign records even though the campaign automation logic does not migrate.

Mailchimp campaign email body exports as raw HTML content files stored as Salesforce ContentDocument records linked to the Campaign. Complex Mailchimp-specific content blocks (dynamic content, time travel, product blocks) may not render correctly in Salesforce's Content Builder; we flag these in the handoff document for manual rebuild if visual fidelity matters. Plain-text campaigns migrate cleanly as Salesforce EmailTemplate records.

Mailchimp email templates export as raw HTML files. Salesforce EmailTemplate and Content Builder assets do not natively parse Mailchimp's content block syntax. We deliver the HTML files in the handoff package and note that templates with complex Mailchimp-specific blocks will require manual rebuild in Salesforce's Content Builder. Text-based and image-forward templates with minimal dynamic content typically transfer without issue.

Mailchimp merge fields (FNAME, LNAME, PHONE, and any custom merge fields the customer created) map to custom fields on the Salesforce Contact or Lead object. Field type mapping: text merge fields map to Text(255), number to Number, date to Date, phone to Phone, address to the standard Address compound field. Field display labels and order are noted for the customer's admin to configure field-level visibility in Salesforce Page Layouts.

Mailchimp open, click, bounce, and unsubscribe events migrate as Salesforce Task records linked to the Contact. Opens and clicks with URLs map as Task records with custom fields for the engagement type and URL. Bounces and unsubscribes update the corresponding HasOptedOutOfEmail flag and create a Task record with the bounce reason or unsubscribe timestamp. We export the last 90 days of activity by default; full history requires pagination across multiple Mailchimp API pages and is available at additional cost for large volumes.

Mailchimp aggregate campaign reports (open rate, click rate, bounce rate, unsubscribe rate, revenue attributed) migrate as custom numeric fields on the Salesforce Campaign record. These are summary values, not per-contact events. Visualization preferences and chart configurations do not transfer; the customer rebuilds dashboards in Salesforce Reports.

Orders synced from Shopify or WooCommerce via Mailchimp's e-commerce integration map to Salesforce Order and OrderProduct records. This requires the connected store to remain active during migration. We extract the full order history including order date, line items, quantities, and revenue before the store connection is terminated. If the connection is severed prematurely, historical order data becomes inaccessible through the Mailchimp API.

Mailchimp e-commerce products map to Salesforce Product2 records. ProductCode, title, and description migrate. Price information maps to StandardPriceBookEntry records. If the customer's Salesforce org does not have Order Management enabled, products migrate as a reference catalog without active pricing, and the customer's admin configures pricebooks post-migration.

Mailchimp automation workflows (Welcome emails, abandoned cart, birthday, post-purchase, anniversary) store trigger/delay/condition/action logic in a proprietary format that cannot be exported. We inventory every active automation with its trigger type, step count, enrollment count, and trigger conditions as a structured checklist in the handoff document. The customer's admin rebuilds each workflow in Salesforce Flow or Marketing Cloud Account Engagement (Pardot) using the inventory as a guide.