Migrate from Marketing Optimizer to Mailchimp

Marketing Optimizer Contact records with name, email, phone, and company linkage map directly to Mailchimp subscribers in a single Audience. We use email address as the dedupe key. First name and last name map to FNAME and LNAME merge fields. Phone number maps to PHONE. Company name maps to COMPANY. Subscribed/unsubscribed status is determined by the contact's current Marketing Optimizer opt-in flag.

Marketing Optimizer Lead records do not have a direct Mailchimp equivalent because Mailchimp does not have a separate Lead object. We migrate Leads as subscribers with the original lifecycle stage (e.g., new_lead, contacted, qualified, sold, rejected) preserved as a Mailchimp tag mo_original_lifecycle_stage. Lead assignment status and buyer/seller routing data migrate as custom merge fields mo_assignment_status and mo_seller_id. The customer's admin decides whether to segment by lifecycle stage tag post-migration.

Marketing Optimizer Campaign records (name, type, associated contacts) map to Mailchimp Campaign records. Associated contacts are re-linked via tag application at migration time. Mailchimp campaign content (templates, copy, subject lines) does not migrate automatically; we extract campaign metadata and recommend the admin use Mailchimp's template library or recreate from scratch. Campaign performance history (open rates, click rates) does not transfer to Mailchimp because those metrics are platform-specific.

Marketing Optimizer custom fields on Contact and Lead require field-level mapping to Mailchimp merge fields. We document all custom field names, types, and sample values during scoping. Text fields map to Mailchimp text merge fields, number fields to number merge fields, date fields to date merge fields, and dropdown fields to radio or dropdown merge fields. Mailchimp allows merge fields up to 255 characters; longer text values are truncated with a flag for customer review.

Marketing Optimizer tracks pages visited and time on site per contact. This data migrates as a Mailchimp tag mo_web_tracked and optionally as a text merge field capturing the last-visited URL and session timestamp. Mailchimp does not have native web tracking in the same way as Marketing Optimizer; post-migration, the customer should implement Mailchimp's website tracking pixel or connect via a CMS integration for continued behavioral data collection.

Marketing Optimizer Lead Assignment records map a lead to a specific buyer or internal user. We migrate these as a text merge field mo_seller_id on the subscriber record. Mailchimp does not have a native assignment model; if the customer needs lead routing post-migration, they should implement Mailchimp's Customer Journey Builder with conditional splits based on the mo_seller_id tag or use a third-party integration like Zapier or a sales engagement tool.

Marketing Optimizer automated workflows define lead routing, scoring, and action triggers. Workflow logic is platform-specific and does not migrate as code to Mailchimp Customer Journey Builder. We document every active workflow with its trigger conditions, branching logic, and action sequence as a migration artifact. The customer's admin rebuilds these in Customer Journey Builder using Mailchimp's visual builder and the documented trigger matrix. Pre-built Mailchimp journey templates (welcome series, abandoned cart, birthday) accelerate common rebuild scenarios.

Files attached to Marketing Optimizer contact or lead records are not accessible via the documented API. We flag all attachments during scoping and recommend the customer exports them manually as a separate step before the migration window closes. Failure to do this results in permanent data loss for attachment-dependent records. Mailchimp does not support file attachments on subscriber records; files associated with email campaigns are stored separately in the campaign content builder.