Migrate from Rule to Mailchimp

Rule contact profiles map directly to Mailchimp subscribers. Standard fields (email, first name, last name, phone) map to Mailchimp merge fields (EMAIL, FNAME, LNAME, PHONE). Behavioral attributes and channel preferences from Rule store as custom merge fields in Mailchimp. We use email as the dedupe key across all imports to prevent duplicate subscriber records.

Rule dynamic segments export as filter logic rather than static snapshots. We reconstruct equivalent Mailchimp segment filters using the same field names and operator logic (equals, contains, greater than, less than, date range). Where Rule segments reference behavioral attributes (opens in last 30 days, tag equals X), we translate these to Mailchimp segment conditions. Note that Mailchimp Standard and Premium offer more sophisticated real-time segmenting than Essentials.

Rule company records contain organization-level data (name, domain, industry, employee count) that Mailchimp does not store as a native Account object. We map company name to a merge field (COMPANY), domain to a merge field (DOMAIN), and attach the remaining fields as structured notes on the subscriber profile for reference.

Contact tags migrate directly to Mailchimp subscriber tags. Rule's multi-tag model maps 1:1; there is no tag limit in Mailchimp for Standard and Premium plans. Tags used for audience segmentation in Rule become tag-based conditions in Mailchimp segment filters.

Rule custom fields on contacts (dropdown, date, numeric, text) map to Mailchimp merge fields with equivalent data types. Dropdown fields become radio or dropdown merge field types in Mailchimp; multi-select fields become checkbox merge fields. We preserve the original field labels and option lists; merge field API names derive from Rule field names with alphanumeric normalization.

Rule automation workflows with trigger conditions, time delays, and channel actions do not migrate as executable code to Mailchimp. The trigger types (event-based, date-based, tag-based) and action sequences differ fundamentally from Mailchimp Customer Journey logic. We deliver a written inventory of every active Rule automation documenting its trigger, conditions, delays, actions, and recommended Mailchimp Customer Journey equivalent for the customer's team to rebuild.

Rule campaign metadata (name, status, linked contacts, send date) migrates as campaign reference data. Campaign performance metrics (open rate, click rate, bounce rate) are time-bound historical records that do not replay in Mailchimp; we export them as a structured report for the customer's analytics team to reference outside the platform.

Rule email engagement events (opens, clicks, bounces, unsubscribes) export as per-subscriber activity records. We map these into Mailchimp's activity feed for each subscriber, preserving the event type, timestamp, and campaign name. Mailchimp surfaces these events in the subscriber profile activity timeline. Historical engagement rates do not carry forward into Mailchimp's aggregate campaign reports.

Rule SMS engagement events (sends, deliveries, replies, opt-outs) have no native Mailchimp equivalent because Mailchimp SMS operates through a separate SMS add-on with its own subscriber data model. We export SMS engagement history as a structured JSON activity log and attach it to the subscriber record as a note for the customer to reference. If the customer activates Mailchimp SMS, SMS engagement data begins fresh from the activation date.

Rule RCS and Social Media engagement events have no Mailchimp equivalent. Mailchimp does not support RCS or Social Media channel tracking. We export these channel histories as structured JSON activity logs for the customer to retain independently; they do not appear in Mailchimp's reporting or subscriber timeline.

Rule email templates (body text, subject lines, image references) export as Mailchimp email templates. We map template body content and preserve dynamic variable syntax where it aligns with Mailchimp merge field syntax. Complex custom variable syntax or proprietary token formats from Rule may require reformatting; we flag these during the template audit for the customer's team to adjust before sending.

Rule suppression lists (unsubscribed, bounced, blocked contacts) export as a distinct suppression dataset before active contacts are imported. We create Mailchimp suppression lists (one per audience or a global suppression list) and import the suppressed email addresses before active contacts to prevent re-engagement of unsubscribed or hard-bounced addresses. Post-import, suppressed contacts carry an unsubscribed status that blocks future sends.