Migrate from MARS to Mailchimp

MARS Contact records map to Mailchimp Member records within a target Audience. Email address is the primary dedupe key. First name and last name migrate to FNAME and LNAME merge fields. Any MARS contact with an email address that matches an existing suppressed or unsubscribed address in the Mailchimp destination is flagged for the suppression list reconciliation phase before import to avoid accidental re-activation of unsubscribed contacts.

MARS Company records denormalize into contact-level data. Company name maps to a COMPANY merge field on the Member record. If MARS Company records contain address, industry, employee count, or annual revenue fields, we create corresponding Mailchimp merge fields (COMPANY_INDUSTRY, COMPANY_SIZE, ANNUAL_REVENUE) at the Audience level before import. Companies with multiple Contacts are tagged with a company-specific tag to preserve the relationship at the Audience level without a native many-to-one link.

MARS Deals have no direct Mailchimp equivalent. Deal records with a status of Won map to a tagged segment in Mailchimp (for example, tag: Closed Won) so that these contacts retain their win context. Deal records with a status of Open or Lost do not map; we deliver a written inventory of open Deals requiring rebuild as Mailchimp Customer Journey automations post-migration. The deal value field is preserved as a merge field DEAL_VALUE on the contact record if reporting on revenue at the contact level is required.

MARS Pipeline stages map to Mailchimp Segments created within the destination Audience. Each pipeline becomes a Segment rule set filtering on the deal stage tag. This is an approximation: Mailchimp Segments filter on contact and merge field data, not deal-level pipeline state, so the segment logic requires denormalization from the Deal to the Contact first.

MARS call engagement records migrate as a Note attached to the Member (via Mailchimp's member notes field) or as a tag (for example, tag: Called-Q4) on the contact record. Call duration, disposition, and recording URL cannot be stored in Mailchimp's standard contact model; these are documented in the migration notes for the customer's admin team to handle manually or via a third-party calling integration post-migration.

MARS email engagement records are preserved as Tags on the contact record (for example, tag: Email-Opened-Q4, tag: Email-Clicked-Promo) with the campaign name and date encoded in the tag. Individual email subject lines and body content do not migrate because Mailchimp stores sent campaign content rather than inbound engagement history per contact. Opens and clicks tracked in MARS become behavioral segment conditions in Mailchimp if the customer sets up the same campaign tracking post-migration.

MARS meeting engagements migrate as Tags on the Member record (for example, tag: Meeting-Booked-Q1-2025) with the meeting title and date. Detailed attendee lists and meeting notes do not have a native Mailchimp home; we document these in the migration handoff notes.

MARS Task and Note engagement records migrate as Mailchimp Member notes. Each Note body becomes a chronological note entry on the Member, preserving author and timestamp. Tasks with status (Open, Completed) map to tags rather than notes to distinguish action items from informational notes. We limit note imports to 1,000 characters per note; longer MARS notes are truncated with a reference to the original record in the migration backup file.

MARS Ticket records have no Mailchimp equivalent. Mailchimp is an email marketing platform and does not support a Case or Ticket object at any plan tier. We deliver a written inventory of all open MARS Tickets with their owner, priority, status, and contact association for the customer's admin to migrate to a dedicated helpdesk platform (such as Zendesk, Freshdesk, or HubSpot Service Hub) as a separate project. The contact associations are preserved as tags on the Member record for reference.