Migrate from CRM Service to Mailchimp

CRM Service Contacts migrate to Mailchimp contacts in a single Audience. Email address is the dedupe key. FirstName, LastName, Title, Phone, and Address fields map to standard Mailchimp Merge Fields (FNAME, LNAME, PHONE, ADDRESS). We preserve any CRM Service contact status as a Tag or Group membership rather than a native status field, since Mailchimp does not have a Contact Status object.

CRM Service Accounts (Companies) map to a Mailchimp Merge Field named COMPANY or a custom company field. The Account Name becomes the Merge Field value on each Contact. Mailchimp does not have a separate Account or Company object with a lookup relationship; all company data lives as a flat field on the Contact record. We recommend setting up the Merge Field before migration and mapping Account.Name to it.

CRM Service Leads have no Mailchimp equivalent. We merge all CRM Service Leads into Mailchimp contacts using email as the dedupe key. The CRM Service Lead Status value is preserved as a Tag (e.g., 'Lead: New', 'Lead: Working', 'Lead: Converted') or as a custom Merge Field named LEAD_STATUS. Any Lead Score value migrates as a numeric Merge Field. The customer chooses the tag strategy during scoping.

CRM Service Opportunities do not have a Mailchimp equivalent. Mailchimp has no pipeline, stage, amount, probability, or close date object. We do not migrate Opportunities as records. We offer a Deal documentation export as a CSV for the customer's admin to review, and we can apply a 'Has Active Deal' Tag or a Deal_Stage Merge Field to contacts with open Opportunities as a workaround. This is an explicit scope limitation that customers must acknowledge before migration.

CRM Service Campaigns track marketing initiative membership with member status and response data. Mailchimp has its own Campaign object for email sends. We do not migrate CRM Service Campaign membership as Mailchimp Campaign records because the data models are incompatible and Mailchimp Campaigns are created within Mailchimp's interface, not imported. We can export Campaign member data as a CSV and apply it as Tags to the corresponding contacts so that the customer's admin can rebuild segments within Mailchimp.

CRM Service custom objects (with __c suffix) have no Mailchimp equivalent. Mailchimp supports up to 40 Merge Fields per Audience, which constrains how many custom object fields can be preserved. We prioritize the top 40 most-used custom fields and map them to Merge Fields. Fields beyond the Merge Field limit are exported as a separate CSV and documented for manual entry or a separate data reference. The customer chooses priority during scoping.

CRM Service engagement history (calls, emails, meetings, tasks) has no native Mailchimp equivalent. Mailchimp tracks campaign engagement (opens, clicks, unsubscribes) but not CRM-level activity. We migrate the most recent engagement summary as a Contact Note or as a Tag indicating 'Has Recent Activity'. The full activity timeline is exported as a CSV for reference. This is a known limitation of the Mailchimp destination; customers expecting full history in Mailchimp should be advised that Mailchimp's contact timeline is campaign-centric, not activity-centric.

CRM Service Owners map to Mailchimp users within the same Mailchimp account, but there is no per-contact owner assignment in Mailchimp. We do not migrate Owner assignments as a contact property. If the customer needs owner-style assignment, we can apply Tags (e.g., 'Owner: John Smith') as a workaround, but Mailchimp does not enforce assignment or provide owner-based filtering.