Migrate from Zoho CRM to Mailchimp

Zoho Contacts map to Mailchimp Audience Members via email address as the unique identifier. Standard fields including First Name, Last Name, Phone, and any custom Contact fields migrate to Mailchimp Merge Fields (FNAME, LNAME, PHONE, and any custom merge field names). We create the merge field in Mailchimp before import and resolve it by name at migration time. If a Contact in Zoho has no email address, we flag it for the customer admin to supply or exclude before import, because Mailchimp requires a valid email for every subscriber.

Zoho Leads map to Mailchimp Audience Members separately from Contacts. We run both modules through the same import pipeline using email address as the dedupe key. If a Lead email matches an existing Contact email, we update the existing member rather than create a duplicate. The Lead Status and Lead Source from Zoho become custom merge fields (LEAD_STATUS, LEAD_SOURCE) on the Mailchimp member so that the customer's admin can use them in segmentation after migration.

Zoho Account data (Company Name, Industry, Annual Revenue, Website, Billing Address) does not have a direct Mailchimp object equivalent. We flatten Account fields into merge fields on each related Contact or Lead, prepending ACCOUNT_ to the field name to distinguish them from Contact-level fields. For example, Account.Industry becomes ACCOUNT_INDUSTRY on the Mailchimp member. Customers who want Account-level reporting in Mailchimp use Tags to label members by company affiliation.

Zoho Tags attached to Contacts and Leads map directly to Mailchimp Tags on the corresponding Audience Member. Tags are preserved as-is and import in the same POST to the Mailchimp Members Tags endpoint. Multi-word tags (e.g., High Priority Customer) import as single Mailchimp tags. If the same tag exists across multiple Zoho modules, we apply it to every matching member in Mailchimp.

Zoho Owner (User) assignments on Contact and Lead records can be preserved in Mailchimp as a custom merge field (OWNER_EMAIL or OWNER_NAME) or as a tag per owner. The customer's admin chooses the strategy during scoping. This field is informational and does not grant Mailchimp access to any user.

Zoho Products attached to Deals do not map to a standard Mailchimp object. If the customer wants to track product affinity in Mailchimp, we create one Mailchimp tag per Product (using Product_Code or Product_Name) and apply it to all Contacts or Leads that are associated with that Product via the Deal. This is a best-effort link resolution because Zoho's deal-to-contact relationship is many-to-many.

Zoho Contact custom fields (fields added beyond the standard schema) migrate to Mailchimp as Merge Fields. We introspect the Zoho field metadata (type, picklist values, required flag) during discovery and create matching merge fields in Mailchimp before import. Picklist fields become Mailchimp text or dropdown merge fields with valid values enumerated. Number and currency fields become number-type merge fields.

If the source includes Zoho Campaigns data (email campaign names, send dates, open rates, click rates), we migrate the campaign metadata as informational records to a separate Mailchimp Tag or note rather than as native Campaign objects, because Mailchimp Campaign objects are created and managed within Mailchimp's UI and have no bulk import endpoint. The customer's admin uses campaign history as a reference for recreating segments in Mailchimp.