Migrate from XMPie to Mailchimp

On Mailchimp Premium ($350/month and above), each XMPie Audience maps to a separate Mailchimp Audience. On Essentials and Standard tiers, the Mailchimp account is limited to one Audience, so XMPie's multiple Audiences collapse into one Mailchimp Audience with each original Audience represented as a Tag. We pick the pattern based on the customer's tier and the operational cost of unsubscribe handling: separate Audiences mean separate unsubscribe lists, while Tag-scoping shares the unsubscribe pool.

Each XMPie Segment defined by parameter rules becomes a Mailchimp Segment (the saved-query type) within the parent Audience. Segment definitions translate into Mailchimp's segment-builder filters with five condition types: subscriber data, signup source, campaign activity, e-commerce data, and tag membership. Where a Segment is small and static, we apply a Tag instead so subscriber lookup is faster. XMPie's higher-segments-take-priority precedence rule is preserved by writing Segment filter order top-down.

Circle Campaign records map to Mailchimp Campaigns. Campaign name, send date, owner, and audience filter transfer. Mailchimp Campaigns have a single channel each (Regular Email, Automation, Postcard, SMS via add-on), so multi-channel XMPie Campaigns split into multiple Mailchimp Campaigns grouped under a shared name prefix and a custom Campaign tag for reporting. Campaign reports preserve via Mailchimp's report API as a one-time snapshot.

Email Touchpoints inside a Circle Campaign become Mailchimp Regular Email Campaigns. We migrate the rendered email content as Mailchimp HTML templates and load send, open, click, bounce, and unsubscribe events from the Circle execution log against the matching subscribers using the Marketing API's POST /lists/{list_id}/activity endpoint. The original send timestamp is preserved on each event so the subscriber timeline reads correctly.

Mailchimp's Postcard channel exists but is limited to standard postcard formats and a Mailchimp-managed print partner; it does not match XMPie uProduce's variable-data print production. We migrate print Touchpoint history as a Tag (for example, received_print_q4_2025) and a custom merge field (last_print_drop_date) so subscriber filtering and segmentation still work. Print rendering itself does not migrate; the customer keeps XMPie running for print production or accepts that print is out of scope.

SMS Touchpoints migrate to Mailchimp SMS, which is a US-only add-on launched in 2024. Each SMS-eligible subscriber needs an explicit SMS opt-in flag because Mailchimp's SMS compliance model is separate from its email subscription model. If the destination Mailchimp account does not have the SMS add-on, we deliver SMS Touchpoint history as Tags (sms_opt_in, last_sms_date) and a CSV inventory rather than as Mailchimp SMS events.

XMPie web Touchpoints render personalized pages driven by uCreate Print Variables. Mailchimp's Landing Pages support personalization via merge tags but do not match XMPie's depth of conditional content. We translate the simplest Variable-driven blocks into merge tags on Mailchimp Landing Pages and deliver the more complex conditional logic as a written specification. Customers who need rich web personalization typically pair Mailchimp with a separate CMS or web personalization tool rather than rebuilding inside Mailchimp.

Each XMPie recipient row becomes a Mailchimp subscriber. Email address is the dedupe key. Subscriber status maps from XMPie's opt-in flag to Mailchimp's subscribed, unsubscribed, cleaned, or pending status. We preserve the original XMPie recipient ID as a custom merge field XMPIE_ID for round-trip reference. First name, last name, address, and phone map to Mailchimp's reserved merge fields FNAME, LNAME, ADDRESS, and PHONE.

Variables in uCreate Print become Mailchimp merge fields, but Mailchimp caps each Audience at 30 merge fields and each text merge field at 255 characters. Customers with more than 30 Variables face a triage decision: which Variables become merge fields, which become Tags, and which are dropped. Long-text Variables that exceed 255 characters are split into multiple merge fields or stored as Tags concatenated with separator characters. We deliver the triage decision matrix as part of discovery.

Content Object rules drive conditional visibility, conditional formatting, and image swaps in XMPie. Mailchimp supports conditional blocks via merge tag conditional syntax (the *|IF:VAR=value|* ... *|END:IF|* construct) inside the Email Builder. We translate each rule to a Mailchimp conditional merge tag block where the logic is straightforward. InDesign-only typography rules (character styles, paragraph styles, multi-page PDF Table layout) do not translate; they are documented as out-of-scope for the email rebuild.

XMPie Data Sources feeding recipient data become flat CSV files for Mailchimp's bulk import endpoint. Excel 95 format files (which PersonalEffect itself does not support) convert to XLSX or CSV first. Multi-source Audiences are deduped by email address; conflicts are surfaced for customer review rather than auto-resolved. Imports run via POST /lists/{list_id} with batch operations to stay inside the 10-simultaneous-connections rate limit per API key.

Per-Touchpoint send, open, click, and unsubscribe timestamps migrate to Mailchimp via the Marketing API's events endpoint, which accepts custom timestamps unlike the standard Mailchimp-to-Mailchimp connector path (which Klaviyo and other tools cap at 90 days). We process events in chronological order so the subscriber Activity feed reads correctly, and we checkpoint progress in a local state file so any 429 response from the rate limiter can resume from the last successful batch.