Migrate from Combit CRM to Mailchimp

Combit CRM Contact records map directly to Mailchimp Members within a target Audience. The contact's email address becomes the Member email, first name and last name map to FNAME and LNAME merge fields, and phone number maps to PHONE. We resolve the Combit contact-to-address link to populate the address merge fields (ADDRESS, CITY, STATE, ZIP, COUNTRY) on the Member record. Any duplicate email addresses across Combit contacts trigger a reconciliation step with the customer before import to avoid Mailchimp's hard bounce policy triggering on re-imports.

Combit CRM Company records have no direct Mailchimp equivalent because Mailchimp does not have a native company or account hierarchy. We map company name to a custom merge field (COMPANY) on the Audience, and company industry or type to a Tag applied to each Member linked to that Company. If the customer needs to track multiple contacts per company, the company name tag approach enables audience segmentation by organization without requiring a separate company object.

Combit CRM Address records hold physical location data that maps to Mailchimp's standard address merge field set. We extract the address components (street, city, state/province, postal code, country) from the Address record linked to each Contact and populate the corresponding Mailchimp merge fields on the Member. Mailchimp's address merge field is a compound field; we split the Combit address string into its components during the transform phase.

Combit CRM user-defined fields across Contact, Company, and Project objects map to Mailchimp merge fields within the target Audience. We identify all custom field definitions during discovery, translate the German field labels to English for Mailchimp merge field names, and map Combit data types to Mailchimp-supported field types (text, number, date, phone, address, birthday, URL, dropdown). Mailchimp allows up to 40 merge fields per audience, which is sufficient for most Combit CRM custom field inventories but requires prioritization if the customer has more than 40 custom fields.

Combit CRM categorical tags on Contact records map to Mailchimp Tags on the corresponding Member. Multi-value tags from Combit (a Contact can have multiple categories) migrate as multiple Tag records in Mailchimp. We consolidate Combit's German-language category labels to English tag names during the transform phase so that Mailchimp's audience segmentation works with the customer's current naming conventions.

Combit CRM Activity records of type email do not migrate to Mailchimp as native email activity because Mailchimp tracks campaign-sent email history only. We extract the last meaningful email interaction date from Combit Activity records and populate a custom merge field (LAST_EMAIL_DATE) on the Member. The customer's marketing team decides whether to surface this in audience segments based on recency of last contact.

Combit CRM Projects span multiple contacts and activities but have no direct Mailchimp equivalent. We map project name or project status to a Tag on all Members associated with that Project via the Combit project-to-contact relationship. Alternatively, a PROJECT_NAME merge field can store the associated project identifier for each contact. The customer selects the strategy during scoping based on whether they need to segment by active project membership.

Combit CRM Deal records track pipeline stages and deal values that do not map to Mailchimp's data model. We extract the current deal stage and deal value and apply a tag (DEAL_STAGE_[stage name]) to the associated Member records. Deal value can also populate a DEAL_VALUE merge field if the customer wants to use deal size as a criterion for audience segmentation or personalization. Pipeline structure itself does not migrate; Mailchimp's automation triggers operate on audience membership and engagement events rather than deal stages.