Migrate from Zixflow to Mailchimp

Zixflow Contacts map directly to Mailchimp Members within an Audience. Standard fields — first name, last name, email address, phone number — map to Mailchimp's native Member fields without transformation. Custom field values map to Mailchimp Merge Fields, subject to the 255-character limit. We validate each field's character count during the transform step and flag any values exceeding the limit for truncation, Content Note creation, or customer decision before import.

Zixflow Collections are list-groupings of Contacts. Each Collection becomes a separate Mailchimp Audience. Members belonging to multiple Collections receive Tags in each corresponding Audience indicating their Collection membership. If the customer prefers a single Audience strategy, we apply a Collection membership Tag across all Members instead and use Tags as the segmentation signal in Mailchimp's segment builder.

Zixflow custom fields (including AI-generated custom fields on Business Stack) map to Mailchimp Merge Fields. Mailchimp enforces a 255-character limit on text Merge Fields. We inspect each custom field's data type and length distribution during the discovery phase. Long-text fields exceeding 255 characters are either truncated to 255 characters, moved to a Mailchimp Content Note attached to the Member, or excluded from the merge field mapping with a documented recommendation — the customer chooses the strategy at scoping.

Zixflow Inbox stores threaded message conversations across WhatsApp, SMS, Email, and RCS channels. Mailchimp Members do not support multi-channel conversation threading. We flatten each Inbox thread into a chronological Member Note with the channel prefix (e.g., [WhatsApp], [SMS]) prepended to each message entry, preserving sender, timestamp, and message body. Channel metadata (delivery status, read receipts) does not map to Mailchimp and is flagged as excluded in the migration inventory.

Zixflow Flows define automation logic as a node-graph with triggers, conditions, and multi-channel actions. Mailchimp Customer Journeys use a different entry-trigger and action model. We inspect each active Flow during scoping, document its trigger conditions and action sequence, and provide a structured Mailchimp Customer Journey rebuild guide so the customer's admin can reconstruct the logic. Flows do not migrate as executable code.

Zixflow Forms capture lead data with custom field structures. Form definitions and submission records require rebuild in Mailchimp. We export Form submissions as Contact field values plus a submission timestamp, which we map to the corresponding Mailchimp Member Merge Fields. The visual form builder and embed code do not transfer; we deliver a Form rebuild guide referencing Mailchimp's form builder with the field mapping documented alongside.

Zixflow User accounts represent seats. During migration we document Zixflow user roles (Admin, Member) and map them to Mailchimp account permissions. Mailchimp's permission model is account-level rather than per-audience; role mapping is informational for the customer's admin to configure post-migration. Active vs. inactive status on Zixflow Users maps to Mailchimp User active/inactive state.

Zixflow Contacts belonging to Collections receive a membership mapping that we preserve as Mailchimp Tags. Each Collection name becomes a Tag name (e.g., Newsletter_Subscribers, Trial_Users). Tags in Mailchimp are audience-scoped, so if the customer uses multiple Audiences, we apply Tags per audience based on the Collection-to-Audience mapping defined during scoping.