Migrate from Xtremepush to Mailchimp

Xtremepush user profiles map directly to Mailchimp Contacts within an Audience. The profile's email address becomes the Contact email (required for import), and the profile UUID becomes a custom merge field XP_ProfileID for cross-reference. First name, last name, phone, and date fields map to Mailchimp's standard FNAME, LNAME, PHONE, and date merge fields. Any profile without a valid email address is excluded from the Mailchimp import and held in a separate reconciliation file.

Xtremepush attributes (custom key-value pairs stored on user profiles) map to Mailchimp Merge Fields. We read the attribute schema during discovery, create the corresponding Mailchimp merge field (with the correct type: text, number, date, phone, address, or dropdown) before import, and map values during data load. Attributes with multi-value semantics (comma-separated lists) become Mailchimp TEXT merge fields; attributes that represent yes/no states become dropdowns with Yes/No options. Mailchimp allows up to 40 merge fields per Audience on Standard and lower tiers.

Xtremepush tags (flat string labels assigned to profiles) map directly to Mailchimp Tags on the same Contact record. Tags migrate as string values, not as a structured taxonomy. We export the tag list from Xtremepush, create the corresponding tag names in Mailchimp during pre-migration setup, and assign tags to each Contact during import. Tags with special characters or spaces are normalized to alphanumeric-and-hyphen format.

Xtremepush consent records (preference type, subscription status, last-updated timestamp, consent source) map to Mailchimp's opt-in tracking model. Active consent becomes a subscribed Contact with a CUSTOM_CONTACT consent tag; unsubscribed records are imported as unsubscribed in Mailchimp (which suppresses them from future sends). We flag the consent source field (manual, SDK, import) as a custom merge field XP_ConsentSource because it is relevant for GDPR compliance audits. High-compliance industries (iGaming, financial services) should re-collect consent through a double opt-in campaign rather than relying on the Xtremepush import-source consent record alone.

Xtremepush campaign records (name, schedule, trigger conditions, channel, content) do not migrate as executable campaigns in Mailchimp because Xtremepush's campaign canvas and Mailchimp's automation builder are structurally different. We deliver a written campaign inventory: every Xtremepush campaign with its name, channel, trigger conditions, and content summary. The customer's team uses this inventory to rebuild equivalent automations in Mailchimp's Automation builder or Customer Journey tool.

Xtremepush audience segments (defined by attribute, event, and tag rules) are documented as segment membership counts and rule definitions. We translate Xtremepush's segment rule syntax into Mailchimp segment conditions using the migrated merge fields and tags. The actual membership is computed in Mailchimp post-import because Xtremepush's event-based segment triggers (real-time behavior) cannot be replicated without the underlying event data pipeline. We deliver a segment mapping table with the rule translation and the expected Mailchimp contact count at migration time.

Xtremepush push tokens (APNS and Firebase GCM) have no equivalent object in Mailchimp because Mailchimp does not support push notifications. These are documented as excluded from migration scope. If the customer requires continued push capability, a separate push provider (Firebase Cloud Messaging, OneSignal, or Airship) must be provisioned and configured post-migration, and the mobile app SDK must be updated to point to the new provider. We provide a device token export as a CSV for use with the new push provider if needed.

Xtremepush loyalty mechanics (points balances, tier assignments, earned badges, gamification achievements) are stored as attributes on user profiles. We export the current state snapshot and map these to Mailchimp merge fields: XP_PointsBalance (number), XP_LoyaltyTier (dropdown), XP_Badges (text list). The gamification rule engine (triggers, reward conditions, threshold logic) is not exposed via export and has no Mailchimp equivalent. We deliver a gamification mechanics inventory listing every rule, trigger, and threshold observed in the account during discovery for the customer's team to evaluate for manual rebuild or a dedicated loyalty platform.