Migrate from Salesmate to Mailchimp

Salesmate Contact records map directly to Mailchimp Members in the selected Audience. We map email address to EMAIL, first name to FNAME, last name to LNAME, phone to PHONE, address fields to ADDRESS, and lifecycle stage to a custom merge field MC_LIFECYCLE_STAGE. Custom contact fields in Salesmate map to Mailchimp merge fields, which we create as text, number, date, or dropdown types during pre-migration setup. The migration uses Mailchimp's Members API with batch operations for contacts under 10,000 and the Bulk API for larger lists.

Salesmate Company records map to Mailchimp Accounts. Mailchimp Accounts are a CRM-level object that can be linked to Members as a company affiliation, but this linkage is optional andMailchimp does not enforce a Company-to-Contact relationship the way a full CRM does. We migrate company name as COMPANY, website as COMPANY_URL, industry as INDUSTRY, and size as COMPANY_SIZE if these fields exist in Salesmate. Any Company custom fields migrate to merge fields on the Account or as contact-level merge fields if no Company record is present for a given contact.

Salesmate Deals have no Mailchimp equivalent. Pipeline stages, deal values, and deal owners cannot be stored in a native Mailchimp object. During scoping, we ask whether the customer wants to preserve deal context as tags on the Contact record (for example, tag each contact with their associated deal stage as a string), as a custom merge field (MC_DEAL_STAGE, MC_DEAL_VALUE), or dropped entirely. The customer chooses the strategy before migration; we do not make this assumption unilaterally because deal-stage tagging inflates the contact tag count and can affect Mailchimp segmentation clarity.

Salesmate Products map to Mailchimp as tags on the related Contact record or as a text merge field (MC_PRODUCT_INTEREST) if the customer wants a single-field reference. Products do not exist as a native Mailchimp object. Full product catalog migration (name, SKU, price, description) is not feasible unless the customer sets up a Mailchimp e-commerce integration with a connected store platform, which is outside CRM migration scope.

Salesmate Tags on Contacts and Companies map directly to Mailchimp Tags on the corresponding Member. Tags are a native, first-class object in both platforms, making this a clean 1:1 mapping. We export tags as string arrays via the Salesmate API and apply them to Mailchimp Members using the Tags API endpoint. Tag naming conventions are preserved as-is; we do not rename or consolidate tags unless the customer requests it during scoping.

Salesmate custom fields on Contacts and Companies (created via the Customize > Create Form interface) map to Mailchimp merge fields. We create the merge field in Mailchimp's Audience settings before migration, matching the field type (text, number, date, phone, address, dropdown) to the Salesmate field type. Merge field names in Mailchimp are uppercase ASCII with underscores (FNAME, LNAME), so we map accordingly. Dropdown-type custom fields in Salesmate become Mailchimp dropdown merge fields with equivalent option values.

Salesmate Owner (the CRM user assigned as record owner) has no Mailchimp equivalent because Mailchimp has no owner-assignment model for Members. If the customer wants to preserve owner context, we map the Salesmate owner name or ID to a custom merge field MC_OWNER on the Contact record. This is a configuration decision made during scoping; we do not default to tagging because tags are more visible in Mailchimp's UI and may cause segmentation confusion if owner information is not actively used for routing.

Salesmate Smart Flow sequence definitions (step logic, cadence, triggers) are not accessible via the public API and cannot be migrated. We export which contacts were enrolled in which active sequences at migration time and store this as a tag (SEQUENCE_ENROLLED_[name]) or as a custom merge field MC_SEQUENCE_ENROLLED on the Mailchimp Member. The customer uses this as a seed list for rebuilding sequences in Mailchimp Customer Journeys post-migration. We explicitly do not migrate sequence step definitions, delays, or conditions.