Migrate from Synerise to Mailchimp

Synerise Profiles map to Mailchimp Members within a target Audience. We export Profiles via the Profile Management API (email, firstName, lastName, phone, address, and all custom attributes) and import via Mailchimp's Members API. Email address is the dedupe key. We flag any Profiles missing an email address during scoping because Mailchimp requires an email for every Member. Synerise's 10M record cap per export job means large workspaces require chunked export jobs segmented by segment membership or creation date range.

Synerise segment membership flags export as true/false per Profile. We transform these into Mailchimp Tags applied per Member. A Profile belonging to five Synerise segments receives five Mailchimp Tags. We recommend a Tag naming convention that prefixes with the segment category (e.g., VIP_segment, churn_risk_segment) to avoid namespace collisions in Mailchimp's flat tag model. Complex segment rule logic does not replicate; only the resulting membership state transfers.

Synerise custom profile attributes map to Mailchimp Merge Fields. We audit all custom attribute names during scoping and flag any that conflict with Mailchimp's reserved field names (EMAIL, FNAME, LNAME, etc.) or exceed Mailchimp's 255-character text limit. Note that Synerise's immutable attribute name constraint means if the original name was poorly chosen, it cannot be renamed on Synerise before export; we document naming mismatches and the customer decides whether to accept the Mailchimp-side name or create a new attribute on Synerise for a reconciliation run.

Synerise Tags (free-form string labels attached to Profiles) map directly to Mailchimp Tags. We preserve the full tag set per Profile and import as Tags on the Member record. Tag count and tag names transfer without transformation. If a Synerise Profile has more than 50 tags, we batch the import to avoid Mailchimp API timeouts on individual member updates.

Synerise Campaign definitions (email, SMS, push, WhatsApp) export from the Campaigns API (100 endpoints). We export campaign configurations including templates, audience rules, and scheduling. Email campaign subject lines and body content transfer as Mailchimp template content. We do not migrate SMS, push, or WhatsApp campaigns because Mailchimp supports email and transactional SMS only; these are flagged as out-of-scope for rebuild planning.

Synerise behavioral events (product.view, transaction, page.visit) do not have a native equivalent in Mailchimp. We offer two strategies during scoping. Strategy one preserves aggregate results (total transactions, total spend, last purchase date, most-viewed category) as Mailchimp Merge Fields with number or date types. Strategy two tags Members with behavioral flags (has_abandoned_cart, has_purchased) for use in Mailchimp segment conditions. Raw event history (individual product.view records) does not migrate because Mailchimp has no event log object. We document the chosen strategy in the migration manifest.

Transaction records export from Synerise's Data Management API and contain line items, totals, and timestamps. Mailchimp has no transaction object, so we compute aggregate purchase metrics (lifetime spend, order count, last order date, average order value) and import these as Merge Fields. We flag the customer at scoping if these aggregates are not pre-computed in Synerise because real-time aggregate computation during export is outside standard migration scope and requires a compute step in the staging environment.

Synerise Catalogs (product/item feeds) used by AI recommendation models have no equivalent in Mailchimp. Mailchimp has no native product catalog, product feed, or recommendation engine. We document all active Catalog configurations (item feed references, recommendation thresholds, display rules) in the migration manifest so the customer's team can evaluate Mailchimp's basic product block capabilities or a third-party product recommendation app from the Mailchimp marketplace as replacements. The catalog product data itself is not migrated.

Synerise Companies are linked to Profiles via profile.assigned-to-company but exist as attributes or schema records rather than a standalone object. Mailchimp has no native company or account object. We export company-related profile attributes (company_name, industry, employee_count if present as custom attributes) and import them as Merge Fields on the Member. No standalone company record is created in Mailchimp. If the customer requires company-level segmentation, we document the attribute-based approach during scoping.

Synerise Automation Workflows export as JSON (node graphs, trigger conditions, action configurations) for documentation purposes only. Mailchimp Customer Journeys are a different automation model with different trigger types, action nodes, and delay logic. We do not migrate workflows as code. We deliver a written inventory of every active Synerise workflow with its trigger, conditions, and actions mapped to a recommended Mailchimp Customer Journey equivalent, and the customer's team rebuilds them post-migration. Any time-sensitive workflows will have gaps during the rebuild window.