Migrate from Convert Wire to Mailchimp

ConvertWire subscribers map directly to Mailchimp subscribers within a single target audience. FlitStack creates the Mailchimp audience first using the account's primary domain, then upserts subscribers via the batch subscribe endpoint keyed on email address. Duplicate subscribers (same email in ConvertWire across multiple lists) collapse to one subscriber record in Mailchimp's audience.

ConvertWire tags migrate as native Mailchimp tags via the Tags API. Each subscriber's tag assignments transfer as individual tag-add operations against the target audience. Tags with identical names are deduplicated during migration so Mailchimp's tag list stays clean. If a tag appears on multiple subscribers, FlitStack executes batch tag-add calls to speed up processing while preserving the original tag name and assignment timestamp.

ConvertWire custom fields map to Mailchimp merge fields within the audience. FlitStack reads each custom field's type in ConvertWire and creates the corresponding Mailchimp field type — text fields become type 'text', number fields become type 'number', date fields become type 'date'. Fields with incompatible types (e.g., ConvertWire stores a JSON object in a text field) are flagged for type-conversion review before migration runs.

ConvertWire forms and landing pages are content objects with embed codes, styling, and submission-handler logic that cannot be exported as structured data. They do not migrate. FlitStack delivers a form-field inventory (field names, types, and conditional logic notes) as a rebuild checklist for Mailchimp's form builder.

ConvertWire automation sequences store trigger conditions and action steps in a proprietary format with no exportable API representation. These do not migrate. FlitStack exports each sequence's trigger type (form submission, tag applied, date-based), enrolled subscriber count, and step summary as a plaintext rebuild reference for Mailchimp's Customer Journey builder.

ConvertWire open and click events per subscriber transfer as Mailchimp 'activity' metadata — FlitStack writes a tagged note to each subscriber's profile with the last open date, last click date, and total click count. Mailchimp does not store per-link click URLs in the same way, so click URLs are consolidated into a single 'has clicked' flag plus last-click timestamp per subscriber.

If ConvertWire stores purchase events or revenue data, these map to Mailchimp's order model for e-commerce-connected accounts. For non-e-commerce accounts, purchase data migrates as a custom merge field (Last_Purchase_Amount__c) and a Last_Purchase_Date__c merge field. Mailchimp's native order sync requires an e-commerce platform integration (Shopify, WooCommerce, etc.) which must be reconnected separately.

ConvertWire broadcast campaign content (email subject, body HTML, send date, and recipient count) is not exported as structured data. Only the fact that a campaign was sent, to how many recipients, on which date, migrates as campaign metadata on each subscriber's profile. The HTML content and templates remain in ConvertWire.

ConvertWire segments (dynamic lists based on subscriber property conditions) are evaluated at migration time. FlitStack exports the segment definition as a list of conditions, then applies the same filter to the Mailchimp audience after migration to recreate equivalent segments. Static segments (manually curated lists) are delivered as tag-based groups in Mailchimp.

Mailchimp does not expose a subscriber create date in the standard contact record that can be used for reporting. FlitStack preserves the original ConvertWire subscriber creation date as a custom merge field (Original_Create_Date__c) in the Mailchimp audience for historical continuity in segmentation and reporting.