Migrate from Anthill CRM to Mailchimp

Anthill Customer records map to Mailchimp Contacts within the target Audience. We extract first_name, last_name, email, phone, and address fields and map them to Mailchimp's standard contact fields. Email address serves as the dedupe key. Any Customer without a valid email address is flagged for the customer to supply or archive. Customer status fields from Anthill map to Mailchimp Tags for segmentation in post-migration cleanup.

Anthill Company records do not have a direct Mailchimp equivalent because Mailchimp has no native company-account object. We map Company name to a merge field (COMPANY or COMPANY_NAME) applied to each Contact. If the customer requires company-level segmentation, we create Tags prefixed with the company name and apply them to all Contacts belonging to that company during the import run. This is a manual design decision made during scoping.

Anthill Enquiry records represent intake or inbound leads at the top of the workflow stream. Because Mailchimp has no pipeline or deal object, we carry Enquiry status as Tags on the corresponding Contact record. Each workflow stage name becomes a Tag value, preserving which stage the original Enquiry occupied. The customer decides during scoping whether to carry full stage history as multiple tags or retain only the most recent stage.

Anthill email and SMS activities tied to Customer records migrate as tagged metadata on the Mailchimp Contact. We extract the most recent engagement date, total engagement count, and preferred channel (email vs SMS) and write these as merge field values. Full activity timestamps and content do not migrate as records because Mailchimp's contact model does not support a native activity timeline. We document each engagement record in a CSV inventory for the customer to reference if needed.

Anthill Users assigned to Sales, Admin, and Support teams map to Mailchimp Users with appropriate access tiers (Manager, Admin, Author, Viewer). We match by email. Anthill's team-level role restrictions have no Mailchimp equivalent; team-level permission scoping is a configuration the customer sets in Mailchimp's audience permissions after migration. Users without a Mailchimp account are reconciled before production migration.

Anthill Workflows define customer interaction processes with team-level task assignments and state-based triggers. Mailchimp's Customer Journeys use a different trigger-and-delay model with no concept of team task allocation. We do not migrate Workflows as code. We audit every active Anthill Workflow, document its trigger conditions, stage sequence, and assigned actions, and deliver a written Workflow Inventory specifying which Customer Journey steps the customer's admin should configure in Mailchimp to replicate the customer communication logic.

Anthill Automations trigger personalised email and SMS sequences based on workflow state transitions. Mailchimp Customer Journeys support comparable trigger-based automation but use a different builder and action model. We do not migrate Automations as code. We document every active Anthill Automation with its trigger, conditions, sequence order, and delay rules, and deliver this as a rebuild guide for the customer's Mailchimp admin.

Anthill live role-based dashboards are configuration files stored in the platform's visualisation engine and are not accessible via API. Mailchimp does not offer a custom dashboard builder. We cannot export dashboard configurations. We document every Anthill dashboard's layout, metrics, filters, and data sources from the live system during scoping and deliver this as a rebuild specification for the customer's admin to reference when building reports in Mailchimp's analytics section or exporting to an external BI tool.