Migrate from Simplicity Enterprise CRM to Mailchimp

Simplicity Contact records map directly to Mailchimp audience members using email address as the dedupe key. Standard fields (first name, last name, email, phone, postal address) map to Mailchimp merge fields (FNAME, LNAME, EMAIL, PHONE, ADDRESS). Any custom contact fields from the Simplicity instance are provisioned as Mailchimp custom merge fields before import. If a contact's company field is populated, we tag the audience member with the company name rather than storing a separate Company record, since Mailchimp has no native company object.

Simplicity Company records do not have a direct Mailchimp equivalent. We extract the company name and map it to a Mailchimp tag (COMPANY) on the contact record, using email-match resolution to link contacts with their parent company. If the customer requires company-level segmentation (e.g. B2B targeting by account), we create a custom merge field BUSINESS_NAME and store the company name per contact. Company phone, website, and address fields are stored as additional custom merge fields if they are actively used in segmentation.

Simplicity Campaign records map to Mailchimp campaigns. Campaign name, subject line, and send date migrate. Campaign-to-contact associations (who was in each campaign audience) map to Mailchimp audience tags by campaign name so that the customer can filter by historical campaign membership. We do not migrate campaign HTML content; email templates are recreated in Mailchimp's template editor. Automations such as welcome series or drip sequences are documented for rebuild in Mailchimp Automation Builder.

Simplicity's campaign response tracking (which contacts opened or clicked which campaign through which channel) has no native Mailchimp equivalent. We map each contact's response history to tagged notes on the audience member record, using a consistent label format such as 'CampaignResponse: [CampaignName] - [Open|Click|ClickLink] on [Date]'. This preserves the behavioural signal as searchable metadata without requiring a separate reporting object. For customers who need campaign-level response reporting, we recommend rebuilding campaign analytics in Mailchimp's built-in reporting after migration.

Simplicity Segments define membership rules (behavioural or demographic) that Mailchimp does not replicate as live dynamic segments. We export segment membership as Mailchimp Groups (if the segment represents a named category such as 'Industry' or 'Plan Tier') or as Tags (if the segment represents a behavioural flag such as 'Opened Last 30 Days' or 'High-Value Customer'). Dynamic segment logic does not migrate; the customer's Mailchimp admin recreates these as Mailchimp Segments using Mailchimp's own filter conditions.

Simplicity email engagements (sent, opened, clicked) do not have a native Mailchimp equivalent because Mailchimp owns the email sending and engagement tracking for its own campaigns. We preserve the historical email activity signal as tagged notes on the contact record (label format: 'EmailEngagement: [Date] - [Subject or CampaignName] - [Status]'). For emails sent outside of Simplicity campaigns (e.g. direct sales emails), we archive the record as a note. This does not create duplicate engagement records for emails sent via Mailchimp, which are already tracked by Mailchimp natively.

Simplicity call and meeting records have no Mailchimp equivalent. We archive these as tagged notes on the audience member using format 'Activity: [Type] on [Date] - [Subject or Duration or Note Summary]'. Call disposition and duration are stored as text within the note. This preserves the record as searchable contact metadata without requiring a separate CRM object. If the customer later adopts a CRM alongside Mailchimp, the archived note format can be parsed and reimported.

The Simplicity Loyalty module stores reward tiers, point balances, and program membership as distinct records linked to Contacts. Since Mailchimp has no loyalty module, we map tier name and point balance to custom merge fields (LOYALTY_TIER and POINTS_BALANCE) on the audience member. Program membership start date migrates as LOYALTY_SINCE. For customers who need a fuller loyalty history (transactions, redemptions), we archive the relational loyalty data as a structured JSON attachment or a multi-line custom field, keeping the contact record clean while preserving the data.