Migrate from Pipedrive to Mailchimp

Pipedrive Persons map 1:1 to Mailchimp contacts within an Audience. The email address is the Mailchimp dedupe key. We resolve the email by lowercasing and trimming, matching against the destination Audience's existing contacts to prevent duplicates. First name, last name, phone, and address fields map directly. Custom fields on Persons are resolved by label (we read the hash-to-label mapping from Pipedrive) and written to Mailchimp as merge tags named by the original field label.

Pipedrive Organizations map to Mailchimp's Company field on contacts. Mailchimp stores companies as a field on the contact record rather than a separate object, so we embed the Organization name and any other Organization custom fields as merge tags on the corresponding contacts. Where multiple Persons belong to one Organization, all receive the same Company field value. We do not create a separate Companies collection in Mailchimp because Mailchimp's data model does not support a standalone company object.

Pipedrive Leads (separate from Persons, introduced in Pipedrive's newer UX) migrate to Mailchimp contacts in the same way as Persons. Lead-specific custom fields are resolved from their hash keys and written as merge tags. Leads without email addresses are flagged in the pre-flight report because Mailchimp requires a valid email for contact creation. Leads with no corresponding Person are imported as standalone contacts.

Pipedrive assigns each custom field a 40-character hash key unique per account. We read the hash-to-label mapping from the source account API, resolve human-readable field names, and create Mailchimp merge tags by label. Field types are preserved: text fields become text merge tags, date fields become date merge tags, dropdowns become radio or dropdown merge tags. If the destination Audience already has merge tags with the same name, we map to the existing tag. If not, we create them during migration scope setup.

Pipedrive tags on Persons, Organizations, and Deals migrate as Mailchimp Tags. Tags are applied to contacts after initial contact creation using Mailchimp's Tags API endpoint. We preserve the tag names exactly and apply all tags from the source record. Tags are not used as dedupe keys; they attach to existing contacts by email address match.

Pipedrive Deals have no equivalent in Mailchimp. Mailchimp has no pipeline, stage, deal value, probability, expected close date, or product-line-item object. We flag all active and archived Deals in the pre-flight report and advise the customer's admin to export them manually as a CSV if a historical record is required. The deal value, stage, and owner cannot be reconstructed in Mailchimp. For teams that need to preserve deal context, we recommend a separate deal-tracking system or a separate export of Pipedrive Deals into a spreadsheet.

Pipedrive Activities (calls, meetings, tasks, notes) have no equivalent object in Mailchimp. Mailchimp tracks email engagement (opens, clicks, unsubscribes, bounces) at the contact level but has no task, call log, or meeting object. We flag Activity volume in the pre-flight report and do not migrate them. The customer's admin may export Pipedrive Activities manually if historical records are required. We do not recreate Pipedrive activity timelines inside Mailchimp because no equivalent structure exists.

Pipedrive Products (standalone items with SKU, pricing, and unit information) have no equivalent in Mailchimp. Mailchimp is an email marketing platform and does not maintain a product catalog. We do not migrate Products or Deal-Product associations. If the customer needs product information attached to contacts, we can map Product names as tags or merge tag values on the associated contacts, but this is a lossy workaround and requires manual field mapping decisions during scoping.

Pipedrive Pipelines and Stages define deal progression and probability within a sales process. Mailchimp has no pipeline concept. Stage names and deal progress cannot be represented in Mailchimp. We document the pipeline structure in the written handoff inventory for the customer's admin to evaluate whether Mailchimp segments can approximate any reporting logic tied to deal stages.