Migrate from Convertkit to Mailchimp

ConvertKit subscribers map 1:1 to Mailchimp audience contacts. Each subscriber's email address becomes the contact identifier in the target audience, ensuring unique identification across your Mailchimp account. Subscriber state values (active, bounced, cancelled) map directly to Mailchimp status flags — active becomes subscribed, bounced becomes unsubscribed, and cancelled maps to cleaned. This mapping preserves subscriber standing through the migration process so engagement history and communication permissions carry forward accurately.

ConvertKit tags migrate as Mailchimp tags — they are flat labels in both platforms, so tag-based segmentation transfers directly. If a subscriber has multiple tags in ConvertKit, each becomes a separate Mailchimp tag on the same contact. This includes tags applied manually by your team and those added by ConvertKit automations during the subscriber lifecycle. All tag metadata is preserved so segmentation rules continue functioning in Mailchimp's targeting filters.

ConvertKit segments use tag combinations and field conditions to group subscribers dynamically. Mailchimp segments use similar filter logic but with different operator names and behaviors. Because the segment rule syntax differs between platforms, we export your ConvertKit segment definitions as a structured reference document. Your Mailchimp admin then recreates each segment using Mailchimp's segment builder, applying the migrated tags and merge fields to replicate the original filtering logic.

ConvertKit forms do not transfer to Mailchimp because each platform's form embed codes, styling system, and submission handling are incompatible. ConvertKit forms are tied to ConvertKit's infrastructure and cannot be imported as functional forms into Mailchimp. We export form field names, field types, and configuration settings as a rebuild reference for your Mailchimp admin to use when recreating equivalent signup forms in Mailchimp's form builder.

ConvertKit landing pages cannot be exported or imported into Mailchimp because each platform uses a different page builder, hosting infrastructure, and URL structure. ConvertKit pages are hosted on ConvertKit's domain with their drag-and-drop editor, while Mailchimp landing pages use Mailchimp's own builder. We document your ConvertKit landing page URLs and titles so your team can recreate equivalent pages in Mailchimp's landing page tool or a third-party service.

ConvertKit sequences (automated email series) do not migrate automatically because ConvertKit's sequence logic uses trigger conditions, delay timers, and action steps that are not compatible with Mailchimp's Customer Journey builder architecture. We export each sequence's complete definition — every email subject line, HTML content, send delay interval, and trigger condition — as a structured text document. Your Mailchimp admin uses this export to manually recreate each Customer Journey in Mailchimp's visual journey builder.

ConvertKit visual automations with branching logic, conditional paths, goal tracking, and action triggers cannot be exported or converted to Mailchimp Customer Journeys due to fundamental differences in how each platform stores and executes automation workflows. We document each automation's complete structure — all trigger events, condition branches, delay actions, and goal milestones — in a structured reference format. Your Mailchimp admin uses this documentation to manually rebuild each workflow in Mailchimp's Customer Journey builder.

ConvertKit broadcasts (one-off email campaigns) have sent history that migrates as campaign records in Mailchimp — including subject line, send date, and open/click statistics. The email HTML content from each broadcast can be exported and reused when creating new Mailchimp campaigns. This migration of broadcast history ensures your Mailchimp reporting timeline includes historical engagement data from ConvertKit, providing a complete picture of subscriber interaction across both platforms.

ConvertKit custom fields map to Mailchimp merge fields through type-based mapping — text custom fields become text merge fields, number fields become number merge fields, date fields become date merge fields, and phone fields become phone merge fields. Address custom fields from ConvertKit map to Mailchimp's compound ADDRESS merge field. Merge fields in Mailchimp are audience-specific, meaning each Mailchimp audience maintains its own set of merge fields independent of other audiences.

ConvertKit pulls product data from Gumroad, Teachable, and Stripe via native integrations — this product information and purchase links are stored as ConvertKit-specific records that do not have a direct equivalent in Mailchimp. To preserve product data in Mailchimp, you must set up Mailchimp's native e-commerce integration with the same platform (Shopify, WooCommerce, BigCommerce, or Magento) so products and orders sync directly. We export ConvertKit product data as a CSV reference file.

Purchase history linked to ConvertKit subscribers requires a Mailchimp e-commerce integration to sync order data into Mailchimp's e-commerce tracking system. Mailchimp supports native e-commerce integrations with Shopify, WooCommerce, BigCommerce, and Magento — if your store uses one of these platforms, connecting the integration will pull order history directly. Without a supported platform integration, ConvertKit purchase records must be mapped manually or exported as a CSV file for Mailchimp's bulk order upload feature.

ConvertKit's subscriber created_at timestamp migrates as a custom merge field in Mailchimp (Signup_Date__c) so your reporting reflects the original subscription date rather than the migration import date. This preserves subscriber tenure data important for engagement segmentation and churn analysis. The timestamp appears in Mailchimp merge field reports and segmentation filters, allowing you to filter contacts based on when they originally subscribed in ConvertKit.