Migrate from RedEye to Mailchimp

RedEye Contacts migrate as Mailchimp subscribers within an Audience. Email address is the dedupe key. Standard contact properties (first name, last name, phone, address fields) map to Mailchimp merge fields (FNAME, LNAME, PHONE, ADDRESS). We flag any contact without an email address as a skipped record and surface the count before import so the customer can decide whether to suppress or re-verify those addresses. Subscription status migrates as a Subscriber Status value; contacts with an unsubscribe timestamp become unsubscribed in Mailchimp via suppression list import rather than per-record import.

RedEye's B2C model stores company linkage as a light-weight contact property rather than a primary record. We extract company association and map it to a Mailchimp text merge field (COMPANY or similar) on the subscriber record. If the customer requires richer company-level reporting in Mailchimp, we recommend creating a separate Audience per company segment or using Mailchimp's Company tag strategy documented during scoping.

RedEye campaigns migrate as Mailchimp campaigns with channel assignments preserved. Campaign name, subject line, from name, and from email transfer directly. We map the RedEye campaign type (regular, triggered, automated) to the closest Mailchimp campaign type (Regular, A/B Test, or Automation). Note that RedEye multi-channel assignments (SMS, push, social) beyond email require separate channel configuration in Mailchimp; we flag unsupported channel assignments for manual setup post-migration.

RedEye visual journey definitions do not export as a portable schema. We extract each journey's trigger conditions, branch logic, and lifecycle stage criteria as a structured rule document. This document describes the journey in Mailchimp Automation terms (trigger block, filter conditions, delay actions, email sends) so the customer's marketing team or a Mailchimp partner can rebuild it manually. We do not configure the Automation inside the migration scope; the rebuild is a separate planning step agreed during scoping.

RedEye behavioural events (website actions, email opens, purchase triggers, custom events) migrate as a flat event log with contact email, event name, and timestamp. We import this as a custom contact activity note or store it in an external event log the customer configures in Mailchimp. Note that Mailchimp does not natively replay imported historical events as automation triggers; the event log serves as a reference record for reporting and customer profile enrichment rather than live journey firing.

RedEye segments are dynamic contact groups built from behavioural rules and demographic criteria. We export each segment definition as a rule set and rebuild it in Mailchimp using equivalent filter conditions. Simple segments (single-field demographic filters) convert directly to Mailchimp Segments. Complex multi-condition behavioural segments may require a tag-based reconstruction strategy or a combination of Segments and Tags; we document the recommended approach per segment during scoping and deliver the full segment map as part of the migration package.

RedEye product catalogue records (SKU, name, pricing, category) migrate to Mailchimp Product entries if the destination uses Mailchimp's e-commerce connected store feature. Product records without an active Mailchimp store connection migrate as a structured CSV reference table the customer can import into any product management tool. Unlimited product records are included on both RedEye tiers, so we flag any product count ceiling in Mailchimp's current tier before migration.

RedEye contact and campaign tags migrate as flat tag arrays attached to the corresponding Mailchimp subscribers and campaigns. Tag names transfer exactly. We flag any tag containing characters unsupported by Mailchimp's tag schema (certain Unicode characters, quotes, or slashes) and normalise them to an accepted format during the transform step to prevent silent tag failure on import.