Migrate from Mailchimp to Zoho CRM

Mailchimp Audiences are top-level containers holding contacts, segments, tags, and group memberships. Zoho CRM does not have an Audience equivalent — contacts live in the Leads or Contacts module. We map each Mailchimp Audience to a named Contacts view or a Zoho Campaigns List. If the customer has multiple Audiences representing distinct business units, we recommend creating separate Zoho CRM modules (e.g., Contacts and a custom module) with a custom field marking the original Audience source. Audience-level settings like opt-in workflow and GDPR compliance flag are noted for Zoho configuration post-migration.

Mailchimp Contacts with subscribed or non-subscribed status map to Zoho CRM Contacts. Contacts with unsubscribed or cleaned status map to Zoho Leads with the Email Opt Out flag set to true. We compute the split at migration time using the status field, and preserve the original Mailchimp status enum value in a custom field mailchimp_status__c for audit. Standard fields (email, first name, last name, phone, address) map to their Zoho CRM equivalents. Merge field values populate corresponding custom fields on the Zoho record.

Mailchimp status is an enum (subscribed, unsubscribed, non-subscribed, cleaned) that changes how the platform treats a contact for billing and sending. Zoho CRM uses boolean flags (Email Opt Out, Do Not Call) that prevent sends and calls. We translate Mailchimp status to Zoho flags: subscribed maps to Email Opt Out = false; unsubscribed and cleaned map to Email Opt Out = true; non-subscribed maps to Email Opt Out = false (billable but not opted in to marketing). We preserve the original enum value in mailchimp_status__c so the customer can reconstruct subscriber segments in Zoho Campaigns if needed.

Mailchimp Tags are freeform labels applied to individual contacts. They map directly to Zoho CRM Tags, which are multi-purpose labels visible across all modules. Tag names and their contact associations migrate 1:1. Tags from Mailchimp that represent audience segments (e.g., VIP, churned, engaged) are flagged for the customer to review — Zoho CRM Filters or Zoho Campaigns Segments may be a better long-term representation for filterable audience logic.

Mailchimp Segments are dynamic filter rules applied to an Audience, with conditions based on merge field values, tag presence, engagement history, and other criteria. The underlying rule syntax is Mailchimp-specific and cannot be exported in executable form. We export the complete segment rule definition (field names, operators, values, and logic) as structured JSON and document each segment with its estimated member count. The customer's admin rebuilds these as Zoho CRM Filters (for internal segmentation) or Zoho Campaigns Segments (for email marketing targeting). Active segment count and complexity are factored into the migration timeline.

Mailchimp Groups are opt-in category memberships (e.g., 'Product Interest: Widget A, Widget B, Widget C') stored within a Group Category. Groups require their parent Category to exist. We export both and map them to Zoho CRM — if the group set is small and static, we map Group Category to a custom picklist field and Group to its values. If groups are numerous or frequently updated, we recommend mapping to Tags with a naming convention like 'Group:Category Name > Group Value'. The customer chooses the strategy during scoping.

Mailchimp Campaign records (sent emails, automations, ads) migrate to Zoho CRM Campaigns with metadata preserved: campaign name, subject line, send date, recipient count, open rate, click rate, and unsubscribe count. Email body content exports as HTML. Zoho Campaigns stores detailed send and engagement data natively, but the aggregate metrics from Mailchimp become reference fields on the Zoho Campaign record. Mailchimp automation workflows associated with a campaign do not migrate as code — the campaign record notes which automations were attached for the rebuild inventory.

Mailchimp Merge Fields are custom contact properties beyond the standard fields. They map directly to Zoho CRM custom fields on the Lead or Contact module. We preserve the merge field name, data type (text, number, date, phone, email, address), and all per-contact values. Field display labels and order are noted in the mapping document so the customer's Zoho admin can replicate the label structure. Required field configuration in Zoho is set to false at migration time and can be adjusted post-migration if data completeness warrants.

Mailchimp email engagement events (opens, clicks, bounces, unsubscribes) from the last 90 days migrate as Zoho CRM Tasks linked to the corresponding Contact record. Open and click events populate a custom multi-line field or activity log for reference. Bounce and unsubscribe events are captured as Activity records with the appropriate disposition type. Full engagement history may require pagination across multiple Mailchimp API pages; we default to 90 days to balance completeness with API rate limit budget and import volume.

Mailchimp email templates are exported as raw HTML files. The block-based Mailchimp template syntax (mailchimp-specific div structures and content block markers) does not render natively in Zoho Campaigns. We export templates with their names, descriptions, and categories for the customer to reference during manual rebuild in Zoho's email designer. Templates with complex nested layouts, Mailchimp-specific dynamic content blocks, or embedded CSS may require a complete redesign. The template HTML export is provided as-is; visual rendering in Zoho is not guaranteed.

Mailchimp automation workflows (Welcome emails, Abandoned Cart, Birthday, Post-Purchase, Custom Journeys) cannot be exported. We inventory all active automations with their trigger type (order placed, date trigger, tag added, etc.), step count, enrollment count, and condition logic. This inventory is delivered as a structured checklist with recommended Zoho Workflow Rule equivalents and, if the customer licenses Zoho Campaigns, Zoho Campaigns multi-step journey equivalents. Rebuilding automations is the customer's post-migration responsibility.

Products, customers, and orders synced from Shopify or other stores via Mailchimp's e-commerce integration migrate to a Zoho custom module (if the customer's Zoho edition supports it) or are provided as structured CSV for import into Zoho Inventory or Zoho Books. E-commerce data is only accessible while the Mailchimp store connection is live. We coordinate the export timing with the store connection and prioritize pulling order history before any account changes are made. Product SKUs and prices migrate as Zoho Products or Inventory items depending on the customer's Zoho setup.