Migrate from Optimove to Mailchimp

Optimove Customer records map to Mailchimp Members within a destination Audience. Email address serves as the primary dedupe key. Standard fields (first name, last name, phone) map to Mailchimp merge fields FNAME, LNAME, PHONE. Custom attributes map to additional merge fields with the understanding that Mailchimp text merge fields are capped at 255 characters; long-text Optimove attributes require truncation or splitting into multiple fields during the transform.

Optimove Lifecycle Stages (e.g., New, Active, At-Risk, Lapsed, Evangelist) translate to Mailchimp Tags applied to each Member at migration time. This preserves the segmentation logic that Optimove uses for behavioral modeling without requiring manual recreation in Mailchimp. Tags are additive and do not overwrite existing Mailchimp tag structures, allowing teams to add new tags post-migration without conflict.

Optimove custom attributes map to Mailchimp merge fields. Mailchimp supports up to 40 merge field slots per audience. If the Optimove customer has fewer than 40 custom attributes, we map them directly. If there are more than 40, we prioritize attributes used in active Target Groups and campaign personalization, flagging the remainder for post-migration manual field creation. All Optimove text attributes exceeding 255 characters are truncated at migration; the original full values are preserved in a supplementary CSV deliverable for the customer's admin to handle separately.

Optimove Target Groups are dynamic customer segments built from attribute rules. We export the customer membership lists and recreate the segment logic as Mailchimp Segments using Mailchimp's filter-based segmentation builder. Complex nested rules with multiple conditions and OR logic may require simplification in Mailchimp's segmentation model; we document each source rule and its recommended Mailchimp equivalent in the migration inventory.

Optimove campaign metadata (campaign name, type, channel, schedule, audience size) migrates as a documented record in the migration inventory. Mailchimp campaign settings (From name, From email, Subject line) are recreated manually because Optimove campaign content is stored in the connected ESP layer, not in Optimove itself. We export Optimove campaign send history to populate the customer-facing performance reference document.

Optimove historical campaign performance data including sends, opens, clicks, conversions, and control group metrics migrates as a structured dataset linked to the original customer email addresses. We preserve open and click event timestamps with CustomerID for downstream attribution in Mailchimp. This historical data is stored as a contact-level custom dataset in Mailchimp rather than as native Mailchimp reporting, which resets at cutover.

Optimove Control Group membership assignments migrate as a Tag (e.g., Control_Group) applied to the relevant Members. This preserves the ability to calculate campaign ROI post-migration by comparing engagement rates between tagged and untagged Members. Control group sizing data is documented in the migration inventory for the customer to reference when setting up A/B tests in Mailchimp.

Optimove user accounts and roles cannot migrate programmatically because Optimove's permission model is platform-specific and Mailchimp does not expose a comparable API-based user provisioning system. We extract the user list from Optimove and deliver it as a roster for the customer's admin to manually configure as Mailchimp Account Users and Audience Contributors with appropriate permission levels.