Migrate from Zymplify to Mailchimp

Zymplify Contact records map to Mailchimp Audience members. Standard fields (email, first_name, last_name, phone_number, job_title) migrate directly. We use the contact email as the Mailchimp subscriber_hash key for dedupe. Any contact without a valid email address is held in a reconciliation queue for the customer's admin to validate before import. Zymplify enrichment provenance (source of data, verification status) migrates as custom Merge Fields.

Mailchimp has no native Account or Company object. Zymplify Company records map as follows: Company name becomes a Merge Field (COMPANY) on the Audience Member. Company-level intent scores and Bombora signals become Mailchimp Tags with a structured naming convention (e.g., intent_high, bombora_signal, g2_intent_spike) that the customer's admin can use to create segments post-migration. Companies without linked Contacts in Zymplify are documented in a separate Company-only export.

Mailchimp has no pipeline, deal, or opportunity object. Zymplify Deals do not have a structural equivalent in Mailchimp. We export the full Deal inventory (deal name, stage, amount, close date, owner, associated contact and company) as a CSV for the customer's admin to import into a separate CRM tool or spreadsheet. The migration deliverable includes a Deal export with a mapping recommendation to whichever CRM the customer adopts alongside Mailchimp.

Zymplify Sales Cadences combine email steps, delays, and task actions into outbound sequences. Mailchimp has no sales cadence or sales engagement feature; its automation builder is marketing-focused (welcome series, abandoned cart, post-purchase). We extract the cadence structure (step order, step type, delay duration, subject, body template, task assignment) as a written sequence spec and deliver it to the customer's admin for rebuilding in Mailchimp's automation builder or migrating to a dedicated sales engagement tool.

Zymplify Marketing Workflows are automation builders with triggers, conditions, and actions across the GTM stack. Mailchimp automations support similar trigger-action models but are scoped to the Audience and cannot trigger CRM actions, cadence steps, or external system events. We document every active Zymplify workflow with its trigger, conditions, branches, and actions as a requirements spec. The admin rebuilds equivalent automations in Mailchimp's automation builder post-migration.

Zymplify health scores and churn risk indicators are calculated natively and have no Mailchimp equivalent. We extract raw health signals (engagement metrics, tenure, support ticket count) as Merge Fields on the Audience Member. The scoring algorithm itself does not migrate. We document the raw signals so the customer's admin can recreate a simplified scoring model in Mailchimp using segmentation rules based on engagement and activity data.

Zymplify's CDP Hub tracks enrichment status and deduplication decisions per contact. We carry the cleansed contact fields directly (overwriting any stale data during import). Enrichment provenance (source system, enrichment timestamp, verification confidence) migrates as Merge Fields. Duplicate status and merge decisions do not have a Mailchimp analog; we document them as a data-quality note for the admin.

Zymplify custom fields across all object types map to Mailchimp Merge Fields within each Audience. Mailchimp allows up to 40 Merge Fields per audience with type restrictions (text, number, date, phone, address, currency, URL, dropdown). We discover the full custom field inventory during the discovery phase, map each field to the appropriate Merge Field type, and flag any fields that exceed Mailchimp's type or cardinality limits for manual handling.

Zymplify user records include role and hub assignments. Mailchimp Users are account-level administrators and editors, not record owners. We map Zymplify owners who need ongoing access to Mailchimp as Mailchimp account Users. Ownership relationships (which user owns which Contact in Zymplify) cannot map to Mailchimp's permission model; we carry owner information as a Merge Field (owner_email) on each Audience Member for segmentation and assignment purposes.

Zymplify tags applied to Contacts and Companies migrate to Mailchimp Tags on the corresponding Audience Members. We preserve the full tag taxonomy and recommend a post-migration tag consolidation review, because Zymplify tag conventions may differ from Mailchimp tag best practices. Tags used for intent signal classification (e.g., intent_high, intent_medium) map to Mailchimp Tags directly and can be used to build segments for targeted campaigns.