Migrate from MoEngage to Mailchimp

MoEngage Users map to Mailchimp Members within the target Audience. Standard user fields (email, first name, last name, phone) map directly. Custom user attributes (up to 100 in MoEngage) map to Mailchimp Merge Fields. We apply Mailchimp's 255-character limit per merge field; any MoEngage attribute exceeding this is truncated and flagged in the mapping manifest. Push tokens and device metadata do not carry forward to Mailchimp since Mailchimp has no native push channel. Historical unsubscribe records from MoEngage are imported as suppressed contacts before active members to protect deliverability.

Each MoEngage custom user attribute becomes a Mailchimp Merge Field. We map MoEngage attribute data types to Mailchimp field types: text attributes to TEXT merge fields, date attributes to DATE merge fields, boolean attributes to TEXT (Yes/No), and number attributes to NUMBER merge fields. MoEngage allows up to 100 custom user attributes; Mailchimp allows up to 40 merge fields per audience on Standard and Premium tiers. If the source has more than 40 attributes, we prioritize attributes used in active segments and flag the remainder for a second audience or JSON auxiliary export.

MoEngage Segments define audience filters based on user attributes and event behavior. We translate MoEngage segment filter logic (attribute conditions, event conditions, recency-frequency-monetary rules) into Mailchimp's segment filter conditions. RFM-specific attributes from MoEngage are mapped to dedicated merge fields so that the customer can create equivalent RFM-based segments in Mailchimp. Segments relying on MoEngage event stream conditions that have no Mailchimp equivalent are flagged as requiring rebuild using Mailchimp's event-triggered Customer Journey conditions.

MoEngage email campaigns with published status and valid channel configuration are inventoried and documented. Campaign content (HTML, subject lines, preview text, sender name, sender email) is extracted and exported as a structured manifest. We do not push campaigns into Mailchimp directly because channel configuration, delivery schedules, and AI-powered send-time optimization (Sherpa AI best-time-to-send) require manual reconstruction in Mailchimp's campaign builder. The handoff document lists every source campaign with its content assets and a Mailchimp equivalent setup recommendation.

MoEngage email templates carry HTML content and personalization tokens. We extract template HTML and map MoEngage personalization tokens (e.g., {{UserAttribute.FirstName}}) to Mailchimp merge field syntax (e.g., *|FNAME|*). Nested object data and dynamic content blocks in MoEngage templates are exported as separate HTML sections and documented as manual rebuild recommendations in Mailchimp's template builder. Template asset mapping is included in the handoff document.

MoEngage behavioral events (purchase, session, funnel, custom) have no direct Mailchimp equivalent. Mailchimp tracks email-level engagement events (opens, clicks, unsubscribes) natively but does not ingest external behavioral event streams into a unified event log. We export the full event schema (event types, attribute names, sample payloads) as a JSON data dictionary. The customer's team can instrument Mailchimp's Event API post-migration to begin collecting events again, or use a CDP integration (e.g., Segment, Hightouch) to pipe warehouse events into Mailchimp Customer Journeys.

MoEngage Product Catalogs with custom schemas map to Mailchimp Product records if the customer enables the Mailchimp E-Commerce integration. We export catalog items in bulk JSON with all attribute definitions and map catalog item IDs to Mailchimp product IDs. If the customer does not have an active Shopify or WooCommerce integration driving the Mailchimp E-Commerce layer, catalog data is delivered as a structured CSV for manual product setup or a separate E-Commerce integration build.

MoEngage campaign tags are workspace-scoped string labels used for campaign organization. Tags migrate as Mailchimp Tags on the corresponding audience members if tag data is stored as a multi-value user attribute in MoEngage. Tags that represent internal categorization (editorial labels, content themes) rather than subscriber-level segmentation are documented separately as a content organization system to be recreated in Mailchimp using Mailchimp's Tags feature.