Migrate from Dynamics 365 Marketing to Mailchimp

Dynamics 365 Marketing Contacts (msdyncrm_contact in Dataverse) map to Mailchimp Audience subscribers. Standard fields (firstname, lastname, email, phone, address) map to Mailchimp merge fields FNAME, LNAME, EMAIL, PHONE, ADDRESS. We apply double opt-in or confirmed opt-in settings at import time based on the customer's consent requirements. The marketing contact billing flag from Dynamics is preserved in a custom field mc_original_marketing_contact__c for audit, but does not trigger Mailchimp billing because Mailchimp's tier is based on total subscriber count across all audiences.

Dynamics 365 Marketing Accounts map to Mailchimp as subscriber merge field values rather than standalone records because Mailchimp does not have an org-level parent record. We map Account.Name to a COMPANY merge field, Account.industry to an INDUSTRY merge field, and Account.website to a WEBSITE merge field on each subscriber. If the customer requires org-level reporting in Mailchimp, we recommend using Mailchimp's built-in company tags or creating an integrations table outside the migration scope.

Dynamics 365 Marketing Leads map to Mailchimp subscribers with lifecycle status preserved in a custom merge field hs_lead_status__c. We map Lead_Status from Dynamics to a human-readable label in Mailchimp (e.g., Open, Qualified, Disqualified). Leads without an email address are flagged in the reconciliation report because Mailchimp requires a valid email for every subscriber. The customer decides during scoping which Lead statuses qualify for audience import versus suppression.

Dynamics 365 Marketing Marketing Lists map to Mailchimp Tags. List membership (the contacts and leads belonging to each Marketing List) translates to individual subscriber tags applied at import time. We export list membership separately from list definition, apply tags in a post-contact pass, and flag any Marketing List without members as empty. If the customer prefers Mailchimp Groups over Tags, we configure Groups during scoping as the Groups interface allows subscriber-facing categorization.

Dynamics 365 Marketing Campaigns map to Mailchimp Campaigns, but only as named placeholders. Campaign structure (target audience, campaign type, sender profile) migrates as metadata, not functional campaign data, because Mailchimp campaign send history cannot be imported from an external source. We deliver a campaign mapping table listing each Dynamics campaign name, its associated Marketing Lists, and the recommended Mailchimp campaign type (regular, automated, or segment-based). Historical open and click rates are not portable to Mailchimp because the engagement attribution lives in Dynamics reporting.

Customer Insights - Data segment definitions are stored in a separate service from the core CRM Dataverse and require a separate export pass. Segment membership (the list of contacts satisfying each segment criteria) exports as a contact ID list, which we then use to apply Mailchimp segment filters. Segment definitions themselves (the criteria rules) do not migrate because Mailchimp uses a different segment query syntax. We deliver a segment mapping document listing each Dynamics segment name and the recommended Mailchimp equivalent (tag-based filter, merge field condition, or combined criteria).

Dynamics 365 Marketing Customer Journeys (msdyncrm_journey table) use a trigger-and-wait model with segment references, email content, and conditional branching that has no functional equivalent in Mailchimp Automation. Mailchimp Automation uses a different trigger paradigm (signup events, date-based triggers, purchase triggers) and does not support the multi-branch wait-and-evaluate logic of Dynamics Journeys. We do not migrate Journey definitions as functional code. We extract Journey metadata (name, associated segments, associated emails, trigger type, number of steps) into a written inventory document that the customer's admin uses to rebuild equivalent automations in Mailchimp.

Dynamics 365 Marketing email templates (msdyncrm_email records) store content in Dataverse but include rendering logic tied to the Customer Insights - Journeys renderer. We extract template metadata (name, subject line, sender profile, associated Journey references) into a written inventory. Full HTML template content may be extracted if the template uses standard HTML blocks, but dynamic content blocks and Copilot-assisted content cannot be ported. The customer's admin rebuilds templates in Mailchimp's drag-and-drop builder using the exported subject lines and content references as guidance.

Custom fields on any Dynamics 365 Marketing entity (Contact, Account, Lead) must be defined in the Mailchimp Audience as merge fields before we can import values into them. We extract field definitions from the managed solution schema (not UI exports, which omit relationship metadata) and create equivalent Mailchimp merge fields of the appropriate type (text, number, date, dropdown) during the schema preparation phase. Merge field values migrate during the main contact pass with the field names normalized to uppercase Mailchimp format.