Migrate from Simplero to Mailchimp

Simplero contacts map directly to Mailchimp audience members via email address as the dedupe key. We preserve first name, last name, email, subscription date, and status (subscribed, unsubscribed, bounced, cleaned). Custom Contact Fields require pre-creation in Mailchimp as merge fields before import; we flag any Simplero custom fields that exceed Mailchimp's 255-character text merge field limit and truncate or flag for manual review. Contacts without email addresses are excluded and listed separately in the reconciliation report.

Simplero tags are flat key-value labels applied to contacts. These map directly to Mailchimp Tags, which are per-audience labels usable for segmentation and filtering. We export the full tag list from Simplero, resolve each to the corresponding Mailchimp audience tag, and apply them during contact import via the bulk import API. Tags with special characters or non-ASCII characters are normalized to ASCII slug format for Mailchimp compatibility.

Simplero segments are dynamic filter groups built from contact property conditions. We document each segment's filter logic (field, operator, value) as a written specification and recreate them as Mailchimp Segments using Mailchimp's segment query syntax. Because Mailchimp segments use different field names and operators than Simplero, we perform a logic translation during scoping. Active segment membership is preserved by exporting contacts matching each segment filter and creating Mailchimp static segments alongside the dynamic equivalents for immediate use.

Individual Simplero email broadcasts map to Mailchimp Regular Campaigns. We export subject line, from name, from email, HTML body content, and any attached images. Mailchimp's campaign type (regular, plaintext, variant) is set during scoping based on the Simplero broadcast format. Campaign stats (opens, clicks, bounces) do not transfer because they are historical metrics tied to the source send; we note this in the reconciliation report so the customer sets fresh baseline expectations in Mailchimp.

Simplero multi-step automation sequences contain content (each email step's subject and body) but not the Flow logic (triggers, delays, branching conditions). We export the content of each email step, map it to a Mailchimp Customer Journey, and document the original trigger conditions and delay rules as a written specification. The customer's admin rebuilds the Customer Journey trigger and timing in Mailchimp using our documented specification. This is manual work requiring attention to the original Flow logic.

Simplero products (courses, memberships, digital downloads, coaching programs) have no Mailchimp equivalent. Mailchimp does not have a product catalog, enrollment tracking, or access management object. We export the product list as a CSV reference table for the customer's records but do not import it. If the customer needs product data in Mailchimp, they must add products manually as audience fields or use a third-party integration like Shopify.

Simplero order records (product, price, date, payment gateway, refund status) have no native Mailchimp equivalent. Mailchimp's e-commerce integration connects only to supported platforms (Shopify, WooCommerce, Magento, BigCommerce, Stripe) and does not accept generic order data. We export orders as a CSV for record-keeping. Refund flags and partial payment statuses are lost unless the customer manually creates custom audience fields to hold them.

Simplero members are contacts with active access to a product or course. Enrollments track which member has access to which product and when. Mailchimp has no enrollment or access management object. We cannot migrate this data structurally. If the customer needs to track course access in Mailchimp, they must manually create tag-based access groups or use an external LMS integration post-migration.

Simplero Flows (triggers, delays, branching conditions, action chains) are not exposed via the public API or any export mechanism. We do not migrate Flow logic. We deliver a written inventory of every active Simplero Flow documenting its trigger event, step sequence, condition branching, and action chain so the customer's admin can rebuild it in Mailchimp Customer Journeys. This is a significant manual effort for complex nurture sequences.

Simplero Deals and pipeline stages (available on Skyrocket tier) have no Mailchimp equivalent. Mailchimp is not a sales CRM and does not have Opportunity, Pipeline, or Deal objects. We export the Deals list as a CSV reference file but do not import it. If the customer needs to track sales data post-migration, they must use a separate CRM tool.

Simplero help desk tickets (subject, status, assignee, conversation thread) have no Mailchimp equivalent. Mailchimp does not have a support ticketing feature. We export ticket records as a CSV reference file for record-keeping. The customer must evaluate dedicated help desk tools (Zendesk, HelpScout, Front) if they need to maintain support history post-migration.