Migrate from erxes to Mailchimp

erxes Contact records map 1:1 to Mailchimp Audience members. The email address is the dedupe key. Standard fields (firstName, lastName, phone) map to Mailchimp FNAME, LNAME, and PHONE merge fields. Any erxes custom fields on Contact migrate as Mailchimp merge fields, which we create in the destination Audience before import. erxes ownerId does not map to a Mailchimp field; we flag this in the handoff documentation for teams that need rep attribution.

erxes Company records do not have a direct Mailchimp equivalent because Mailchimp has no Account object. We split company data: the company name becomes a COMPANY merge field on each Contact that links to it, and additional company properties (industry, size, website, address) become merge fields (COMPANYINDUSTRY, COMPANYSIZE, COMPANYWEBSITE) that we populate per linked Contact. The customer decides during scoping whether to use one Audience for all contacts or segment by company domain.

erxes email campaign history does not map to Mailchimp campaign records (Mailchimp campaigns are not created by API import; they are built inside the Mailchimp UI). Instead, we tag each Contact in Mailchimp with tags reflecting their erxes engagement history (e.g., 'Received Welcome Email', 'Opened Campaign Q4 Newsletter'). This preserves a lightweight signal of past email interaction without recreating the full campaign audit trail.

erxes contacts with an unsubscribed email status must import into Mailchimp as suppressed contacts before any sendable records land. We export the erxes unsubscribes list, format it for Mailchimp's suppression import API, and push it first. This step is mandatory for deliverability protection: importing sendable records before suppression lists can trigger Mailchimp's spam filter audit and temporarily suspend the new account's sending reputation.

erxes Users (team members) do not map to Mailchimp objects because Mailchimp uses account-level user access rather than contact-level owner assignments. We document the erxes user list and their assigned contacts in the handoff spreadsheet. If the customer needs rep attribution on Mailchimp contacts (e.g., for accountability or territory management), we add a REPASSIGNMENT merge field and populate it from erxes ownerId during contact import.

erxes multi-channel Conversation history (email, SMS, chat, WhatsApp messages) has no Mailchimp equivalent. We tag contacts who appear in Conversations with metadata tags (e.g., 'Has SMS History', 'Has Chat History') to signal conversation touchpoints, but the full message body, thread ordering, and channel metadata do not migrate. This is a conscious data reduction decision because Mailchimp is an email marketing platform, not a helpdesk.

erxes custom fields defined on Contacts migrate to Mailchimp merge fields with type mapping: text fields become TEXT merge fields, date fields become DATE merge fields, dropdown selects become dropdown merge fields. We create the merge fields in Mailchimp before contact import using the Mailchimp Marketing API. erxes custom fields on other objects (Deals, Tasks, Companies) do not migrate because the parent objects have no Mailchimp equivalent.

erxes Automation Workflows (trigger-action sequences defined in the Marketing plugin) do not migrate to Mailchimp Customer Journeys because the automation logic, triggers, and conditions are platform-specific and not exportable from erxes. We extract the automation names, active/inactive status, and trigger types and deliver them as a written inventory with Mailchimp Customer Journeys equivalents. The customer rebuilds them in Mailchimp's automation builder post-migration.