Migrate from SuiteCRM to Mailchimp

SuiteCRM Contact records map to Mailchimp Audience Members within a designated Audience. We map standard fields: email (required), first_name, last_name, phone, address fields (street, city, state, zip, country). Each Contact's primary Account link is preserved as a tag account_name on the Mailchimp contact for segmentation. SuiteCRM Contacts without an email address are flagged as incomplete and excluded from migration pending customer decision on how to handle them.

SuiteCRM Leads map to the same Mailchimp Audience as Contacts. Where the customer has both a Contact and a Lead with the same email address (duplicate across modules), we merge them during deduplication, preserving Lead-specific fields (lead_source, status, rating) as Mailchimp merge tags. If the destination Mailchimp account has separate Audiences for Leads vs Customers, we distribute based on a lead_status field rule defined during scoping.

SuiteCRM Target Lists (used for campaign segmentation) map to Mailchimp Tags applied to the relevant Audience Members. We export the Target List membership junction table (Contact ID, Target List ID) and apply the Target List name as a Mailchimp tag during import. A Contact belonging to three Target Lists receives three Mailchimp tags. This preserves the segmentation logic without requiring a separate Audience per list.

SuiteCRM Studio custom fields on Contacts and Leads map to Mailchimp Merge Fields (merge tags) within the Audience. We detect field type during database scan: text fields become TEXT merge fields, date fields become DATE merge fields, dropdown fields become dropdown merge fields, and boolean fields become TEXT with Yes/No values. Mailchimp limits merge field names to 10 characters and merge field values to 255 characters, so we truncate and sanitize accordingly.

SuiteCRM Accounts have no direct Mailchimp equivalent because Mailchimp does not have an Account or Company object. We handle this as a lookup resolution: each Contact's primary Account is resolved at migration time and the Account name is applied as a Mailchimp tag on the Contact record (e.g., tag: Acme_Corp). This enables segment filtering by company within Mailchimp's segment builder. We flag Account-level fields (industry, website, annual_revenue) as informational and note that these do not migrate unless the customer has Mailchimp Plus or Premium where custom contact properties beyond merge fields may be used.

SuiteCRM Campaign records migrate as Mailchimp Campaign metadata (Campaign name, campaign type, status, start date) but not as live Mailchimp Campaigns with actual sends. Mailchimp Campaigns require a built email template and audience segment that must be created within Mailchimp's builder. We deliver a written Campaign handoff document listing each SuiteCRM Campaign record (name, target list, campaign type, description) with the recommended Mailchimp Campaign setup steps so the customer's marketing team can recreate sends with the migrated contacts as recipients.

SuiteCRM Documents are stored on the server filesystem with a database metadata record. Mailchimp does not have a document attachment capability on contact records. We do not migrate Document records. If documents are critical (e.g., signed agreements stored against a Contact), the customer should export them separately from SuiteCRM's upload directory and store them in a document management system outside Mailchimp.

SuiteCRM Opportunities, Invoices, Cases, Contracts, Products, and Quotes have no equivalent in Mailchimp's data model. Mailchimp is an email marketing platform, not a CRM. We exclude all of these objects from migration scope. We deliver a written inventory of these records with record counts so the customer's admin is aware of what will not transfer. If the customer needs CRM functionality alongside Mailchimp, we recommend evaluating HubSpot CRM Free, Salesforce Sales Cloud Starter, or Zoho CRM as a paired CRM post-migration.