Migrate from Marketing Star to Mailchimp

Marketing Star Contacts map to Mailchimp Audience members. The email address is the primary identifier and the required field for Mailchimp import. Marketing Star's mobile phone field maps to Mailchimp's PHONE field when present; SMS consent status from Marketing Star's SMS contact flag maps to Mailchimp's marketing_concent field (boolean). Records missing both email and mobile phone are flagged during profiling and excluded or handled per customer instruction since Mailchimp requires a valid email address for every member.

Marketing Star Lists map to Mailchimp Tags applied to the unified Audience. Each list name becomes a tag of type 'List: [Original List Name]' so the original audience groupings are preserved and filterable. If the customer used list-based suppression logic, we also apply 'Suppressed' tags or import those records as unsubscribed in Mailchimp. Lists exceeding the destination tier's contact cap are chunked and each sub-list becomes a separate tag group to replicate the original segmentation structure.

Marketing Star campaign names, send dates, subject lines, and high-level performance metrics (open rate, click rate, bounce rate) migrate as campaign metadata. Mailchimp Campaigns are created with names prefixed 'Archived: [Original Name]' so the customer can review historical performance. The campaign content (email HTML, templates) migrates as reference data; we export the HTML and note the original campaign configuration so the customer's admin can rebuild active campaigns in Mailchimp's campaign builder.

Marketing Star SMS contacts are distinguished by mobile phone number and an SMS opt-in flag. We preserve the mobile phone as Mailchimp's PHONE field and map the SMS opt-in status to Mailchimp's marketing_consent field. If Marketing Star records SMS consent at a per-list level, we apply that context as a Mailchimp Tag for segmentation. Note that Mailchimp SMS requires a separate paid add-on and is not included in standard email marketing plans.

Marketing Star QR codes are tied to campaigns or forms and track physical-to-digital attribution. We export QR code metadata including the encoded URL, redirect destination, and campaign association. In Mailchimp, QR codes do not have a native equivalent; we recreate the redirect configuration as a documented URL mapping so the customer's web team can set up server-side redirects or landing page redirects in their hosting environment.

Marketing Star Forms capture leads and map form fields to contact properties. Form structure and field-to-property mappings export from Marketing Star. Mailchimp provides embedded form code and a form builder but does not import Marketing Star form definitions. We deliver a written form inventory documenting each Marketing Star form's fields, required status, and property mappings so the customer's admin can rebuild equivalent Mailchimp embedded forms or use Mailchimp's form builder to recreate lead-capture flows.

Marketing Star Landing Pages are available on Ultimate tier only. We export page content as static HTML and document URL redirect configurations. Mailchimp has no native landing page builder. We deliver the exported content as a static asset package and a URL redirect map so the customer's developer can host pages externally or use a third-party landing page tool. This is explicitly a rebuild scope, not a data migration.

Marketing Star Automation Workflows are documented and not migrated as executable code. Mailchimp Automations use a Journey-style builder with trigger types (Welcome, Birthday, Abandoned Cart, API-triggered, etc.) that differ from Marketing Star's campaign-trigger model. We deliver a written automation inventory specifying each Marketing Star workflow's trigger, conditions, sequence steps, and delay logic with a recommended Mailchimp Automation equivalent. The customer's admin rebuilds automations post-migration using the inventory as a blueprint.