Migrate from Engage Messaging to Mailchimp

Engage Messaging Contacts map to Mailchimp Audience Members. The primary key mapping is phone number to email address, but Mailchimp requires an email address as the Member identifier. If the Engage Messaging Contact has an email property, we map it directly. If not, we flag the Contact for email address research or enrichment during scoping. Opt-in status from Engage Messaging (opt_in flag) maps to Marketing Permissions in Mailchimp. Custom fields on the Engage Messaging Contact migrate to Mailchimp Merge Fields with type mapping (text to text, number to number, date to date). Tags and segment memberships carry across as Tags and Groups in Mailchimp.

Engage Messaging Tags applied to Contacts migrate to Mailchimp Tags. Tags are flat-label structures in both systems, so the mapping is direct. Multiple Tags on a single Contact become multiple Tag assignments on the corresponding Mailchimp Member. We export Tag names and their association to Contact records and rebuild the Tag assignments during the Member import. Tags used for categorization rather than segmentation are preserved without transformation.

Engage Messaging Segments group Contacts by criteria (engagement history, tag membership, custom property values). Mailchimp Groups serve a similar organizational function. We export Segment definitions as criteria lists and map them to Mailchimp Group names and Group Interest values. Note that Mailchimp Groups operate at the Audience level while Engage Messaging Segments operate at the Contact level; the mapping preserves the membership outcome rather than the criteria engine. The customer rebuilds the segment criteria in Mailchimp using Audience segmentation filters if dynamic membership is required.

Engage Messaging Conversations thread messages between Contacts and agents with assignment tracking, conversation status, and shared inbox metadata. Mailchimp has no conversation model; it is a campaign broadcast platform, not a two-way messaging inbox. We do not migrate Conversation records. If conversation context is required at the destination, we recommend exporting a Conversation summary report from Engage Messaging before cutover and attaching it as a manual reference document. Agent assignment and shared inbox roles do not map to any Mailchimp construct.

Individual SMS and MMS messages in Engage Messaging are outbound or inbound units within a Conversation thread. Mailchimp sends Campaign emails to Audience Members; individual message receipts and delivery status records have no equivalent. We export message metadata (timestamp, direction, delivery status) as a reference CSV but do not create corresponding records in Mailchimp. MMS media attachments require separate file handling: we download media files from Engage Messaging and store them alongside the migration documentation for manual re-upload if needed at the destination.

Engage Messaging Automations (triggers, delays, conditional branches, message content) are platform-specific configuration that cannot be exported as executable logic. We do not migrate automations. Instead, we export a human-readable inventory of each Engage Messaging automation with its trigger conditions, sequence steps, message copy, and delay values. The customer uses this inventory to recreate the logic in Mailchimp Customer Journey Builder, which uses a different trigger-event model. The inventory document includes recommended Mailchimp trigger equivalents (signup, tag added, campaign opened, purchase) for each migrated automation.

Engage Messaging provisions dedicated and toll-free numbers that are locked to the platform and cannot be transferred. We export a list of all active numbers (with type, status, and monthly cost) as a re-provisioning checklist. If the customer intends to use Mailchimp SMS, they must submit an SMS marketing program application and agree to terms before purchasing SMS credits. We flag this step during scoping so the customer can initiate the approval process before cutover. Numbers used for WhatsApp on Engage Messaging require a separate WhatsApp Business number provisioned at Meta.

Engage Messaging delivery rates, open rates, click-through rates, and subscriber growth metrics are computed on-platform and not exposed via API. Historical analytics cannot be exported as structured data. We recommend capturing screenshots of Engage Messaging dashboards before cutover for reporting continuity. Post-migration analytics begin in Mailchimp from the date of cutover. Campaign performance history does not carry forward.