Migrate from Mautic to Mailchimp

Mautic Contact records map directly to Mailchimp Audience members. All standard fields (email, firstname, lastname, phone, title, city, state, country, company) map to their Mailchimp merge field equivalents. Custom contact fields map to Mailchimp merge fields with type conversion: text fields to text merge fields, date fields to date merge fields, number fields to number merge fields. The primary key is the contact email address. We resolve any duplicate email addresses during import by matching on email and updating existing Audience members rather than creating duplicates.

Mautic Company records have no direct Mailchimp equivalent because Mailchimp has no native company or account object. We flatten company data into the contact record: company name becomes the COMPANY merge field, and company address fields (street, city, state, zip, country) are stored in a structured merge field block or appended as text fields on the contact. One-to-many contact-to-company relationships in Mautic (a contact can belong to multiple companies) cannot be preserved in Mailchimp; we attach the primary company record only and note the limitation for the customer's CRM integration plan.

Mautic Tags are flat string labels applied to contacts. They map directly to Mailchimp Tags, which are applied identically to Audience members. All tag names and memberships transfer without transformation. Tag-based segmentation in Mautic does not carry over as active segment definitions; the customer rebuilds segment logic in Mailchimp Segments using the same tag conditions.

Mautic Segments are dynamic contact lists defined by filter rules (field values, tags, behaviors, campaign membership). We export the segment name, description, and full filter definition logic in a written specification document. Mailchimp Segments must be rebuilt manually using Mailchimp's segment builder because the filter condition syntax differs between platforms. The segment membership itself is recalculated at migration time after contacts are in Mailchimp, using the exported filter rules as the rebuild guide.

Mautic Campaigns (automation workflows) and Email Campaigns (single sends) have different structures in Mailchimp. We export campaign metadata: campaign name, send date, subject line, from name, open rate, click rate, bounce rate, and unsubscribe count. This metadata is delivered as a CSV inventory for the customer's reporting records. The campaign automation logic (triggers, conditions, delays, actions) does not transfer to Mailchimp Customer Journeys because the workflow architectures are incompatible. We document each Mautic campaign's automation steps in a written rebuild guide for Mailchimp Customer Journeys.

Mautic Forms collect contact data and trigger actions on submission. We export form definitions including field configurations, field types, and submission logic. Mailchimp's embedded signup forms provide a comparable field builder but with different validation rules and styling constraints. We deliver a form field mapping document that pairs each Mautic form field with its Mailchimp equivalent. Form submission actions (adding to a segment, updating a field, triggering a campaign) do not migrate; the customer rebuilds these actions in Mailchimp's form settings or automation triggers.

Mautic Assets are downloadable files managed within the platform (PDFs, guides, media). Mailchimp does not have a native file asset management system. Asset metadata (file name, URL, description, download count) is exported as a CSV inventory. The files themselves must be migrated separately to a CMS, file hosting service, or Mailchimp's content studio if the customer uses Mailchimp's paid tiers with content storage. We provide the asset inventory and URL mapping during migration but do not migrate binary files as standard scope.

Mautic Custom Objects extend the data model beyond standard contacts and companies, supporting relationships between object types. Mailchimp has no custom object or relationship model; the platform supports only standard subscriber profiles with merge fields. Any Mautic Custom Object records, relationship definitions, and junction table data cannot be migrated to Mailchimp. We export the custom object schema, field definitions, and a sample of records as a CSV deliverable. The customer's admin decides how to handle this data post-migration: it may be stored in an external database, a CRM, or a custom Mailchimp integration.