Migrate from Smarketing Cloud to Mailchimp

Smarketing Cloud Contact records with valid email addresses migrate as Mailchimp Subscribers in the designated Audience. Standard fields (first name, last name, email, phone) map to Mailchimp merge fields (FNAME, LNAME, EMAIL, PHONE). Lifecycle stage from Smarketing Cloud migrates as a tag on the subscriber (e.g., tag: lifecycle:customer) for segmentation in Mailchimp. Records without a valid email address are held in a reconciliation list for the customer to resolve before import.

Mailchimp has no native company object. Company name from Smarketing Cloud maps to a Mailchimp merge field (COMPANY) and a tag (company:acme-corp) per subscriber. If the customer requires rich company-contact linkage, we recommend establishing a Mailchimp integration with a CRM connector (e.g., HubSpot CRM sync, Salesforce Mailchimp integration) post-migration to maintain the relationship. Company address, industry, and custom fields map to additional merge fields or are documented as manual data to populate in the CRM connector.

Smarketing Cloud Campaign records are recreated in Mailchimp as Campaigns (for one-time sends) or Automation workflows (for triggered or drip sequences). Campaign membership records determine which subscribers receive which tag. Each contact enrolled in a Smarketing Cloud Campaign receives a corresponding tag in Mailchimp (e.g., campaign:spring-promo) to preserve enrollment history. Active and paused campaign status in Smarketing Cloud does not transfer; campaigns are created in Draft or active state in Mailchimp at the customer's discretion.

Smarketing Cloud records which contacts were enrolled in which campaigns and when. We export the full campaign-contact membership list, then apply tags to the corresponding Mailchimp subscribers. The enrollment date migrates as a custom merge field (e.g., ENROLLDATE_2024) or as part of the tag string (campaign:spring-promo:2024-03-15) depending on the customer's segmentation needs. A subscriber can carry multiple campaign tags, preserving the full enrollment history.

Tags applied to Smarketing Cloud Contacts and Companies migrate as Mailchimp Tags on the corresponding subscribers. We export all distinct tag strings, map them to Mailchimp tag format, and apply them in bulk during import. Tags that reference Smarketing Cloud-specific concepts (e.g., pipeline stage or owner) are preserved as tags with a prefix (e.g., owner:jane-doe, stage:qualified) and flagged for the customer to review for relevance in Mailchimp.

Smarketing Cloud Automation Workflows are documented in a written inventory we deliver to the customer, including trigger conditions, filter criteria, action sequence, and timing logic. Mailchimp Customer Journeys use a different trigger-action model and must be rebuilt manually or with Mailchimp's Journey Builder. We do not migrate workflow logic as code. The inventory document maps each Smarketing Cloud workflow to a recommended Mailchimp Journey configuration.

Smarketing Cloud Email Template HTML content exports with variable placeholders. We extract the HTML and remap placeholder syntax to Mailchimp merge field format (e.g., {{first_name}} becomes *|FNAME|*). CSS inlining and responsive template structure are preserved during remapping. Templates with complex conditional content (branching logic) are documented for manual rebuild in Mailchimp's template editor because Mailchimp's conditional merge field syntax differs from Smarketing Cloud's.

Smarketing Cloud Pipelines and Deals have no Mailchimp equivalent. Mailchimp is an email marketing platform, not a CRM, and does not include opportunity management, deal stages, or revenue tracking. We flag pipeline and deal records as not migratable and present them to the customer during scoping. If the customer requires pipeline tracking post-migration, we recommend a separate CRM migration or integration with a CRM platform alongside the Mailchimp setup.