Migrate from cMercury to Mailchimp

cMercury Subscribers map to Mailchimp Audience members via email address as the dedupe key. Each subscriber's subscription status (active, unsubscribed, bounced) maps to Mailchimp's Member Status. We apply any unsubscribes or hard bounces from cMercury as a suppression import before the main audience import to prevent Mailchimp from automatically re-engaging suppressed contacts.

cMercury's per-subscriber engagement score has no native Mailchimp equivalent. We create a custom merge field (ENGAGEMENTSCORE or similar) on the Mailchimp Audience and populate it with the numeric value from cMercury. Mailchimp does not use this field for segmentation or automation triggers natively, but it is available for export, reporting, and triggering through Mailchimp's API-based integrations.

cMercury Verify badges (valid, invalid, risky, catch-all) per subscriber transfer as a custom text merge field (VERIFICATION_STATUS) on each Mailchimp contact record. Mailchimp does not enforce or act on this status, but it is preserved for the customer's data hygiene records and can be used to filter sends via Mailchimp segment conditions or API-based routing.

cMercury Segments defined by filter rules translate into Mailchimp Segments with equivalent condition logic. Simple single-condition segments map cleanly. Nested AND/OR conditions in cMercury may require multiple Mailchimp segments or a static segment approach since Mailchimp's segment builder uses a flat condition list rather than nested groups. We document each cMercury segment and its Mailchimp equivalent during scoping.

cMercury tags on subscribers map directly to Mailchimp Tags on the corresponding Audience member. Tags are preserved as flat string labels and can be used in Mailchimp for segmentation, reporting, and automation triggering via Customer Journeys. Tag names with special characters are normalized to Mailchimp's tag format during export.

cMercury campaign records include subject line, send date, recipient count, and aggregate performance stats (opens, clicks, bounces, unsubscribes). We export this as a CSV companion file alongside the audience import. Mailchimp campaign history is separate from contact records; the customer can reference the companion file for historical performance comparison after migration. We do not recreate campaigns in Mailchimp because subject lines, content, and timing are campaign-specific and require editorial decisions post-migration.

cMercury templates use a proprietary block structure for the drag-and-drop editor. We extract template HTML and inline images, download hosted image assets, and re-upload them to Mailchimp's Content Studio. We then recreate the template structure using Mailchimp's block-based editor, noting that complex nested layouts with conditional content may require manual reconstruction. Template names and folder organization are preserved where Mailchimp supports them.

cMercury custom profile fields on subscribers (text, number, date, dropdown) map to Mailchimp Merge Fields with equivalent data types. Text fields map to text merge fields, numeric fields to number merge fields, dates to date merge fields, and dropdowns to radio or dropdown merge fields depending on the cMercury field configuration. We preserve the field labels and populate values during the audience import.

cMercury sending domains with DKIM, SPF, and DMARC records cannot be transferred to Mailchimp because DNS records are platform-specific. We document each cMercury's sending domain configuration during discovery and provide a DNS checklist for the customer to set up SPF, DKIM, and custom tracking domains in Mailchimp before the first send. This step is required before Mailchimp allows sending from the customer's branded domain.

Images and files stored in cMercury's Asset Library are downloaded and uploaded to Mailchimp's Content Studio. File names and folder organization are preserved where Mailchimp's folder structure supports it. We flag any image that exceeds Mailchimp's file size limits and note any HTML files or non-image assets that cannot be imported to Content Studio.