Migrate from Zixflow Marketing Automation to Mailchimp

Zixflow Contacts migrate to Mailchimp Audience Members. Standard fields (email, first name, last name, phone) map directly. We resolve duplicate email addresses by preferring the most recently updated Contact record. Zixflow contact status (subscribed, unsubscribed, bounced) maps to Mailchimp member Status using the Mailchimp Marketing API member status values (subscribed, unsubscribed, cleaned, pending). Contact creation timestamp migrates to Mailchimp Stats Fields for campaign recency analysis.

Zixflow Collections are list-grouping objects with many-to-many contact membership. Mailchimp's model uses one primary List per Audience with Segments for internal grouping. If contacts belong to multiple Collections, we create one Mailchimp Audience per primary Collection and use Tags to track secondary Collection memberships. If the customer prefers a single Audience with Segments, we flatten multi-collection membership into Segments and tag accordingly. The customer chooses the strategy during scoping.

Zixflow WhatsApp Subscribers migrate as Mailchimp Audience Members with a WhatsApp-specific tag (e.g., SOURCE_WHATSAPP) and opt-in timestamp recorded in a merge field. The default 500 WhatsApp subscriber cap from Zixflow does not apply in Mailchimp. We flag if the contact volume exceeds the customer's Mailchimp plan limit so additional contacts can be purchased before the migration runs to avoid API rejection on import.

Zixflow custom AI-generated enrichment fields export as key-value pairs. Mailchimp merge fields are limited to 255 characters for text type. We map each Zixflow custom property to a Mailchimp merge field by name, truncating values that exceed the 255-character limit with a suffix indicator (e.g., '__TRUNCATED'). The customer decides during scoping whether truncation is acceptable or whether to exclude long-field data from migration.

Zixflow Forms capture leads and feed data into Contacts and Collections. Form definitions and field structures export as a written specification so the customer's team can rebuild equivalent forms using Mailchimp's form builder or embedded signup forms. Form submission history does not migrate as a standalone object; submissions are already represented in the contact records with field values preserved.

Zixflow Flows are visual automation definitions stored in a proprietary builder format. Automation logic cannot be exported or transferred. We export each Flow's name, trigger type, step summary, and action list as a written document. The customer's team uses this document to rebuild equivalent automations in Mailchimp's Customer Journey builder. This is a time investment that should be scoped before migration begins.

Zixflow Inbox aggregates multichannel conversation threads. Mailchimp does not have a native conversation inbox. We export inbox metadata (thread count, date range, contact association) as a written summary for the customer's records. Active conversations should be resolved or manually forwarded before migration cutover. Historical message content does not migrate.

Zixflow Wallet is a financial balance for messaging credits. This is a billing record, not customer data, and is excluded from migration scope. We flag the current wallet balance so the customer can drain or forfeit remaining credits before closing the Zixflow account. Flow automation credit history similarly does not migrate.