Migrate from Agencyzoom to Mailchimp

AgencyZoom contacts and leads migrate as Mailchimp Subscribers within a target Audience. Email address serves as the unique key for deduplication across the import. Unsubscribed contacts in AgencyZoom are imported as unsubscribed in Mailchimp to preserve suppression status and protect deliverability reputation. The subscription status mapping ensures GDPR compliance and prevents accidentally re-activating suppressed contacts during the migration process.

AgencyZoom lifecycle stages map to Mailchimp Tags applied at import time. A 'Lead' stage contact gets the tag 'Stage: Lead'. Tags are additive so a contact can carry multiple stage transition tags from AgencyZoom's history, enabling Mailchimp segments to reconstruct lifecycle-aware logic.

AgencyZoom's lead source categories (Referral, Website, Carrier Website, etc.) migrate as Tags on the Subscriber record — e.g., 'Source: Carrier Website'. These tags enable Mailchimp segments to replicate AgencyZoom's lead source segmentation logic, allowing targeted campaigns that reach contacts based on how they originally entered the insurance agency's pipeline. The tagging preserves attribution data that would otherwise be lost in a platform switch.

AgencyZoom pipelines have no direct Mailchimp equivalent. We capture each pipeline assignment as a Tag (e.g., 'Pipeline: Sales', 'Pipeline: Service') and build a corresponding Mailchimp Segment filter using tag membership, so the original pipeline context drives campaign targeting in Mailchimp.

Policy fields merge into Mailchimp Merge Fields (POLICYNO, CARRIER, EFFDATE, XDATE) stored on the Subscriber record. This preserves policy context on each contact in Mailchimp for renewal drip campaigns, carrier-specific messaging, and lapse-warning segments — without requiring a full CRM.

AgencyZoom's custom fields (retrieved via GET /v1/api/custom-fields) map to Mailchimp Merge Fields created before import. Merge field type is inferred from AgencyZoom's data type: text fields become text Merge Fields, date fields become date Merge Fields, and pick-list fields become radio or dropdown Merge Fields with mapped values.

AgencyZoom notes attached to contacts migrate as Mailchimp Notes on the Subscriber profile with timestamp and author preserved. Call and email activity records are summarized as a Note entry (e.g., '3 calls logged, last call: 2024-11-15') to preserve activity history without creating separate CRM-style activity objects.

AgencyZoom Service Tickets track customer service interactions. Mailchimp has no service ticket object — we apply a 'Has Service Ticket' tag to contacts with open tickets and add a note summarizing ticket status. Open service ticket details must be tracked outside Mailchimp or migrated to a dedicated service tool post-switch.

AgencyZoom owner/producer assignment migrates to a Mailchimp Merge Field (OWNERAGT) storing the owner's name or email. Mailchimp does not have a native user-assignment model per contact — the field is informational only, enabling agents to filter and segment their own contact lists using this attribute for targeted outreach management.

AgencyZoom's internal tag system migrates 1:1 as Mailchimp Tags on the Subscriber. If a contact has tags 'Renewal', 'High Priority', and 'Commercial Auto' in AgencyZoom, those exact tags are applied in Mailchimp, preserving any tagging taxonomy the agency built over time.

AgencyZoom Lifecycle Automations (email drip sequences, task creation, SMS triggers tied to pipeline stages) have no Mailchimp equivalent. Mailchimp Customer Journeys can replicate basic email drip logic but cannot mirror complex multi-branch automation trees. FlitStack exports the automation definition JSON as a rebuild reference document.

AgencyZoom's carrier API connections for quoting workflows, commission data feeds, and policy update syncing do not exist within Mailchimp's ecosystem. These carrier credential configurations and integration logic must be disconnected from AgencyZoom separately and re-established in a dedicated insurance CRM platform or directly through carrier portals as needed following the migration, as Mailchimp lacks any carrier connection infrastructure.