Migrate from Zoho Marketing Plus to Mailchimp

Discovery and data audit

We audit the source Zoho Marketing Plus portal: contact volume and status distribution, mailing list and segment structure, custom contact field definitions and data types, active Journey count and complexity, campaign history volume, and any event, survey, or landing page assets. We confirm the customer's Mailchimp plan tier based on subscriber count and feature requirements (Essentials, Standard, Premium, or Max). The discovery output is a written migration scope document with record counts, segment mapping plan, and a Mailchimp plan recommendation if the customer has not yet provisioned their destination account.

Merge tag audit and template normalization

We scan all Zoho email campaign content for merge tag usage and map each Zoho merge field to its Mailchimp merge field equivalent. Hard-coded merge tags in custom HTML templates are flagged for manual replacement. We run a pre-export template audit to identify any non-standard HTML that may render inconsistently in Mailchimp, and we document recommendations for the customer's admin to review and clean templates before migration or to rebuild from Mailchimp's template library.

Contact export with deduplication and status normalization

We export contacts from Zoho Marketing Plus via the Marketing Automation API in batches of 100 records per request, using request queuing with exponential backoff to respect the 100-call-per-5-minute limit. Each contact record includes all standard fields, custom fields, subscriber status, source attribution, and any lead scoring values. We run email address deduplication against the full export set before Mailchimp import to prevent duplicate subscribers. Subscriber statuses (subscribed, unsubscribed, bounced, cleaned) normalize to Mailchimp's member status model.

Segment and tag migration

We migrate Zoho mailing lists as Mailchimp Audiences. Zoho Segments with static member lists migrate as Mailchimp Segments. Zoho Segments with dynamic behavioral criteria (engagement-based, date-based) migrate as documentation for the customer's admin to rebuild as Mailchimp Segment conditions. We map Zoho's behavioral and demographic segment criteria to Mailchimp's segment condition builder and deliver a segment translation matrix. Brand metadata from Zoho's multi-brand structure migrates as Mailchimp Tags on each contact.

Campaign content migration and Journey inventory

We export Zoho campaign metadata (name, subject, send date, recipient count, open rate, click rate, bounce count) and campaign content (HTML and text bodies) as structured records. We map Zoho merge tags to Mailchimp merge field tokens in the content. Active campaigns are paused in Zoho before migration begins to prevent mid-migration sends. For each Zoho Journey, we produce a written inventory document describing the trigger, all conditions and filters, step sequence, delays, and recommended Mailchimp Customer Journey equivalent. This document is delivered separately from the data migration and is the customer's rebuild reference.

Mailchimp import and validation

We import contacts into Mailchimp via the Mailchimp API using batch operations with chunking. The import uses email address as the dedupe key and applies subscriber status for each record. Segment membership is applied after contact import using Mailchimp's segment update API. We validate by reconciling contact counts between Zoho export and Mailchimp import, spot-checking 25-50 records for field-level accuracy, and running a campaign send test to the internal team before any production campaign deployment.

Cutover and handoff documentation

We freeze Zoho Marketing Plus writes during the final cutover window, run a delta export of any records modified during migration, and update Mailchimp with the final record set. We deliver the complete migration package: contact export CSV, campaign content files, segment translation matrix, and Journey inventory document. We support a three-day post-migration validation window where we resolve any record reconciliation issues. Journey rebuild, landing page reconstruction, and survey setup are outside standard migration scope and are the customer's admin responsibility using the handoff documentation.