Migrate from Mailchimp to Microsoft Dynamics 365 Sales

Mailchimp Audiences have no direct single-object equivalent in Microsoft Dynamics 365 Sales . We create a top-level Account record named for the Audience (using Audience name as the Account name), then create Dynamics Marketing List members linked to that Account, preserving the Audience's opt-in workflow settings. For organizations with multiple distinct Audiences representing different business lines, each Audience maps to a separate Account and Marketing List pair.

Mailchimp Contacts with a confirmed company affiliation and a buyer-role email address (procurement, executive, sales-rep domains) map to a Dynamics Contact tied to the Account derived from their Audience. Contacts with personal or unqualified email domains with no company affiliation map to a Dynamics Lead for sales follow-up. The original Mailchimp status (subscribed, unsubscribed, non-subscribed, cleaned) is preserved in a custom field mc_original_status__c on both Lead and Contact.

If Contacts carry a company name via a Mailchimp merge field (typically named COMPANY or COMPANY_NAME), we resolve each unique company name to a Dynamics Account record. Account is created before Contact import so that the Contact-to-Account Lookup is satisfied at insert time. Company names that are blank or non-specific in Mailchimp create placeholder Accounts that the customer's admin reconciles post-migration.

Mailchimp tags migrate as custom fields on the Dynamics Lead or Contact object. If fewer than 150 distinct tag values exist across the contact base, we use a multi-select picklist field named mc_tags__c. For tag volumes exceeding picklist limits, we create a related custom entity mc_contact_tag__c with a Lookup to Contact/Lead and a Tag Name field, allowing an N:N relationship without picklist constraints.

Mailchimp segments are dynamic filter sets (based on merge field values, tag presence, engagement history, or signup date) that do not export in a form compatible with Dynamics 365. We export segment rules as structured JSON describing the filter conditions and flag count, then create equivalent Dynamics Marketing List membership criteria or Power Automate flows that replicate the segment logic. Complex behavioral segments (based on opens, clicks, purchase recency) require a rebuild in Dynamics Customer Insights or a connector like Marketing4Dynamics.

Mailchimp campaign metadata (campaign name, subject line, send date, recipient count, open rate, click rate, bounce rate, unsubscribe count) migrates as a Dynamics 365 Campaign record with metrics stored in custom fields. Individual contact engagement with each campaign (opened, clicked, bounced, unsubscribed) migrates as CampaignMember records with corresponding statuses. We import the last 90 days of campaign history by default; full history requires pagination across multiple Mailchimp API pages.

Individual email open, click, bounce, and unsubscribe events from Mailchimp's activity log migrate as Task records on the corresponding Dynamics Lead or Contact. Opens and clicks become Task records with a custom mc_engagement_type__c field (open, click, bounce, unsubscribe). We set ActivityDate to the original Mailchimp event timestamp to preserve the engagement timeline. The full 90-day activity log migrates by default; historical events beyond 90 days are included if the Mailchimp API pagination completes within the migration window.

Mailchimp email templates use Mailchimp-specific content block syntax that does not export in a form that renders natively in Dynamics 365 or Outlook. We export template HTML as raw files for the customer's reference, but Dynamics email templates must be rebuilt using Dynamics' built-in template editor or Marketing Cloud Content Builder. We flag each template with a rebuild recommendation during the automation inventory phase.

Every Mailchimp merge field (custom contact properties beyond email, name, phone, address) migrates to a corresponding custom field on the Dynamics Lead or Contact object. Field type mapping: text merge fields become Dynamics Text fields, date fields become Date fields, number fields become Number fields, and checkbox fields become Checkbox fields. We preserve field labels and ordering in a separate mapping reference document for the customer's admin to assign to Dynamics field-level security profiles.

Orders, products, and customers synced via Mailchimp's e-commerce integration migrate to a custom Order entity in Microsoft Dynamics 365 Sales if the destination org has no ERP integration. Product data becomes Product2 records; Order data becomes a custom sales order entity with line items. The connected store must remain linked during migration; if the connection is severed before export completes, historical order data may be inaccessible. We recommend running the e-commerce export phase first and separately from the contact migration.