Migrate from Mailchimp to Pipedrive

Mailchimp Audiences do not map to a single Pipedrive object. We split each Audience into Pipedrive Person records (the individual contacts) and Organization records (extracted from company_name merge fields or domain logic on email addresses). All Pipedrive Persons from the same Audience can optionally be tagged with the Audience name for segmentation clarity in Pipedrive.

Mailchimp Contact records map 1:1 to Pipedrive Person. We migrate standard fields (first_name, last_name, email_address, phone_number) plus all merge field values as custom Pipedrive Person fields. GDPR consent flags (opt_in_status,gdpr_consent) migrate to Pipedrive custom fields for compliance record-keeping. Unsubscribed and non-subscribed contacts land as inactive Persons or with a suppressed tag rather than being excluded entirely, preserving the record for audit.

Mailchimp Tags map directly to Pipedrive Labels on Person records. We export the full tag name and associate every tag with its contact record. Pipedrive Labels are a flat namespace per Person; nested Mailchimp tag categories are flattened to a single label string with the category prefix retained (e.g., Source::TradeShow).

Mailchimp Segments use Mailchimp's proprietary filter syntax against merge fields and engagement data. Pipedrive Filters replicate the same logic using field-based filter conditions on Person and Organization records. We export each segment's rules as structured data (field name, operator, value) and construct equivalent Pipedrive filter definitions during migration. Segment membership itself is not a static list in Pipedrive; it is a live query.

Mailchimp Campaign metadata (name, subject line, send date, recipient count, open rate, click rate) migrates as Pipedrive Activity records of type Note attached to each recipient Person. The campaign HTML content is exported as an attachment. Sent campaign lists do not create new Pipedrive records; the campaign history lives as Activity notes for reference during sales conversations.

Mailchimp open, click, bounce, and unsubscribe events for each contact migrate as Pipedrive Activity records. An open event becomes a Note activity with the event type and timestamp; an unsubscribe event becomes a Note noting the opt-out date. We export the last 90 days of activity by default using Mailchimp Marketing API pagination. Bounced and cleaned addresses are flagged in a custom field rather than creating a full Activity record.

Mailchimp custom merge fields map to Pipedrive Person custom fields. We preserve field names, types (text, number, date, phone, address), and all per-contact values. Field order and display labels are documented for Pipedrive admin to configure in the Person field settings. Multi-value fields (checkboxes) become Pipedrive multi-select fields.

Mailchimp email templates use Mailchimp-specific content block syntax that cannot render in Pipedrive. Pipedrive does not have an email template builder for marketing campaigns; it has email signatures and basic templates scoped to CRM activity emails. We export templates as raw HTML files and note that the customer should rebuild visually complex templates in their chosen email marketing tool. This object does not migrate as a usable Pipedrive record.

Mailchimp Automations (Welcome emails, abandoned cart, birthday, post-purchase) store logic in a proprietary format with no export mechanism. We do not migrate automations as active workflows. We deliver a written inventory of every active automation including trigger type, step count, enrollment size, and recommended Pipedrive Automation Builder equivalent. The customer's admin rebuilds each automation post-migration.

Orders, products, and customers synced from Shopify or other connected stores via Mailchimp's e-commerce integration migrate as custom fields on Pipedrive Person and Organization records (order_count, total_spent, last_order_date). We export this data first before any store connection is severed, as historical order data is only accessible while the integration is live. Pipedrive does not have a native e-commerce module; this data becomes reference fields rather than a structured order object.