Migrate from Agillic to Mailchimp

Agillic Recipients map to Mailchimp Contacts. We enumerate every custom recipient property during discovery via the Recipient API and map each to a Mailchimp merge field. If the property count exceeds 30 (standard) or 80 (Premium), we consolidate multi-value string properties into Tags, flag numeric or date fields for conversion to text merge fields, and document the dropped fields for the customer to assess. The recipient email address is the Mailchimp subscriber identifier and dedupe key.

Agillic Activity records (sends, opens, clicks, bounces, SMS deliveries) migrate as Mailchimp activity history entries against each contact. Mailchimp preserves aggregate open and click stats per contact in its interface, but does not expose event-level timestamps for every individual open/click the way Agillic's Activity Export does. We migrate what Mailchimp can represent and document the full event-level history from Agillic Activity Export as a data export for the customer's analytics team.

The Agillic Flow Execution ID cannot be natively represented in Mailchimp's activity model. We store the Flow Execution ID as a Mailchimp Tag on each affected contact record (e.g., tag format: flow_execution_[ID]) so the customer can reference which Agillic flow triggered a given communication, though Mailchimp's automation builder cannot act on these tags as triggers.

Agillic Global Data Tables are custom relational structures referenced within Flows. Mailchimp has no relational table concept. We export table schemas and row data, then map tabular fields to Mailchimp merge fields where the field maps to a contact attribute, or to Tags where the data represents segment classification. Many Global Data Table use cases (product catalogs, subscription tiers, loyalty points) cannot be represented in Mailchimp and require a separate external system or a Mailchimp-integrated app.

Agillic email, SMS, and push templates migrate as content assets with field mappings documented. HTML-based templates require content refactoring to Mailchimp's template editor or a compatible HTML import. We export template content and dynamic field bindings and deliver a mapping document showing which Agillic template fields map to which Mailchimp merge tags. Visual refactoring of the template layout is not in scope.

Agillic's Recipients Export feature generates a structured file of all recipient records and current field values. We use this as a baseline for full-contact migrations, reconcile against Recipient API data, and ingest into Mailchimp via the Mailchimp Marketing API Members endpoint with batch processing and dedupe by email address.

Agillic Flows are not exportable as portable workflow definitions. We export Flow names, associated trigger events, and step sequences as a written inventory document. The customer rebuilds equivalent automations in Mailchimp's Customer Journeys 3.0 builder, which supports email and SMS triggers, conditional branching, and time-based delays. Agillic's omnichannel Flows (push, print, paid media, POS) have no Mailchimp equivalent and are documented as requiring an alternative platform.

Agillic's real-time audience activation to Google and Meta does not have a Mailchimp equivalent. We export audience definitions and membership criteria as a written specification so the customer can recreate equivalent segments using Mailchimp's segment builder with contact properties and tag logic. The paid media activation logic requires manual rebuild within Google Ads or Meta Ads Manager using exported contact lists.