# Pipedrive and Mailchimp: who owns the contact status after the sync, and what a rep should see before calling

https://salesbond.app/blog/pipedrive-mailchimp-sync-lead-status-opt-out/
Published: 2026-10-24 · Updated: 2026-10-24

When Pipedrive and Mailchimp are connected, decide which tool owns the subscription status and which owns the deal. Neither of Pipedrive’s two Mailchimp integrations lists subscription status among the things it moves between the tools, so the rule has to live in the team, not in the integration. Ours: Mailchimp owns subscribed or unsubscribed, Pipedrive owns the stage and the deal owner, and a contact who unsubscribed in Mailchimp does not get a sales sequence from Pipedrive until a rep has looked at that status.

## Two tools, two truths about one contact

Take Anna. In Pipedrive she is on an open deal at Proposal sent, owner Tom, next activity a call on Thursday. In Mailchimp the same address has been Unsubscribed since last week. Both records are correct. On Wednesday Tom adds her to a three-step follow-up sequence, because Pipedrive is where he works.

Nothing stops him. Mailchimp treats each audience independently, and an unsubscribe opts the contact out of that audience’s marketing email and SMS only ( [Mailchimp: About unsubscribes](https://mailchimp.com/help/about-unsubscribes/)). Pipedrive never hears about it. The setup guides cover which fields to map; the harder question is who decides that Anna should not hear from you.

## What the Pipedrive Mailchimp integration syncs

Pipedrive’s knowledge base documents two integrations, and the answer depends on which one is installed. Both are under Tools and apps > Integrations in Pipedrive: the older one is listed as Mailchimp, and Mailchimp sync is a separate app with its own install.

The older **Mailchimp** integration is one-way: a “syncbot” sends people from a Pipedrive filter to a Mailchimp audience, with a few mapped fields such as email address, name and birthday. A person who exists in Pipedrive but not in Mailchimp is added to the audience as Subscribed, and Pipedrive’s own note asks that those contacts agreed to hear from you ( [Pipedrive: Mailchimp integration](https://support.pipedrive.com/en/article/pipedrive-integration-mailchimp)).

The newer **Mailchimp sync** works on flows. Each flow has one trigger, its own field mapping and one direction ( [Pipedrive: Mailchimp sync](https://support.pipedrive.com/en/article/pipedrive-integration-mailchimp-sync)):

- Mailchimp to Pipedrive: contacts matching selected segments or tags, or every new contact added to an audience.
- Pipedrive to Mailchimp: people matching selected Pipedrive filters, or the person on a deal when that deal enters a chosen pipeline stage.

Two limits from the same article belong in the team wiki. Change an email address on either side and the contact syncs as a new one, while the old one stops getting updates. And both Pipedrive-to-Mailchimp triggers create new Mailchimp contacts as subscribed; the setup asks you to confirm exactly that.

Now the thing that is absent. The mapping covers contact fields (some types, like Pipedrive single option fields, can’t be mapped at all), and subscription status is not mentioned anywhere in it. A Mailchimp-to-Pipedrive flow brings in people who match a segment or tag and updates the fields you mapped, and Unsubscribed is not one of them. Pipedrive’s own marketing status field belongs to Pipedrive Campaigns and lives on the email address, which is [a separate story with its own traps](https://salesbond.app/blog/pipedrive-marketing-status-unsubscribed-contacts/).

If you do want the unsubscribe written into Pipedrive, that takes a third-party connector. Pipedrive’s own article names Outfunnel, which says it records Mailchimp unsubscribes in Pipedrive as notes, activities or custom field updates ( [Outfunnel: Pipedrive Mailchimp integration](https://outfunnel.com/pipedrive-mailchimp-integration/)). Zapier lists a Mailchimp “New Unsubscriber” trigger and a Pipedrive “Update Person” action ( [Zapier: Mailchimp + Pipedrive](https://zapier.com/apps/mailchimp/integrations/pipedrive)). Under our rule, whatever lands in Pipedrive this way is still a copy.

## Who owns the unsubscribed status

Mailchimp does. The unsubscribe happened there, and the way back runs through there: a contact who wants your emails again has to resubscribe to the audience ( [Mailchimp: About unsubscribes](https://mailchimp.com/help/about-unsubscribes/)). Any flag in Pipedrive is a copy, and a copy maintained by hand goes stale the week someone forgets.

Pipedrive owns the rest: the stage, the owner, the next activity. Sales doesn’t re-add an unsubscribed address to an audience because the deal looks warm.

![Ownership table: Mailchimp owns subscription status, Pipedrive owns the deal; an opt-out field in the CRM is only a note](https://salesbond.app/wp-content/uploads/2026/10/pipedrive-mailchimp-sync-lead-status-opt-out-2.png)

If the team wants the opt-out visible inside Pipedrive without a connector, make it a note everyone knows is a note: a custom field like “Marketing opt-out seen in Mailchimp” with a date, filled by whoever looked. What breaks is treating that field as the truth and skipping the look. We wrote up [the same ownership rule for Zoho CRM and Mailchimp](https://salesbond.app/blog/zoho-crm-mailchimp-integration-opt-out-lead-status-owner/), the mechanics differ but the rule does not.

Read the status as a signal, not a verdict. Mailchimp lists ways a contact ends up unsubscribed without meaning to: a forwarded email where the second reader clicked the link, an inbox filter that clicks every link, another admin’s slip (same article). An unsubscribe is a reason to ask Anna, not to close her deal.

## What a rep checks before a sales email or call

The check is small, which is why it survives. Before adding a person with an open deal to a sequence or a template email, the rep opens the contact in Mailchimp under Audience > Manage contacts, where Pipedrive-imported contacts show up ( [Pipedrive: Mailchimp integration](https://support.pipedrive.com/en/article/pipedrive-integration-mailchimp)), and reads the status. Subscribed: go ahead. Unsubscribed: no sequence, no template.

The call still happens. So does a one-to-one email from Tom about the proposal Anna asked for. That is not marketing, and we have [argued before](https://salesbond.app/blog/pipedrive-campaigns-vs-one-to-one-email/) that a small team should keep the two apart. Say it on the call: “I saw you unsubscribed from our newsletter, so I’ll keep this to the proposal.” One sentence, and the buyer knows someone on your side is paying attention.

## The weekly manager check

Reps forget. The manager makes forgetting visible once a week with one list: people unsubscribed in Mailchimp who have an open deal in Pipedrive and a call or email planned.

1. In Mailchimp, export the audience. The export comes as a ZIP with a separate CSV per contact type, unsubscribed included; only Owners and Admins can export audiences ( [Mailchimp: View or export contacts](https://mailchimp.com/help/view-export-contacts/) ).
2. In Pipedrive, build a people filter for contacts with an open deal and an activity scheduled for the coming week, and export it.
3. Match the two lists by email address. A spreadsheet lookup is enough.
4. For each match, send the owner one line in state, reason, action form: “Anna, Unsubscribed in Mailchimp since last week. Reason: open deal at Proposal sent, call on Thursday. Action: call as planned, no sequence, mention the opt-out.”

Overlap list empty three weeks running? Move the check to monthly. If it keeps producing the same names, the problem is not the integration. Its a rep who doesn’t think the rule applies to a warm deal.

## When a one-way sync is enough

For most small teams, it is. Pipedrive to Mailchimp on a filter or a pipeline stage, plus the status check above, covers the case that actually hurts: a buyer who opted out and got a sales sequence anyway.

We’d turn on the other direction for one reason only: marketing qualifies leads in Mailchimp first, with segments or tags, and sales should only see the ones that passed. Without that intent a Mailchimp-to-Pipedrive flow drops newsletter signups into the CRM as people with no deal, no owner and no recorded source, and six months later nobody can tell [which leads came from the web form](https://salesbond.app/blog/pipedrive-lead-source-web-forms/). A sync direction is a decision about who gets to create records in your CRM.

A disclosure: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. It does not read Mailchimp, so the unsubscribed overlap stays a manual check. What it does is check the Pipedrive side of those same deals against its deal rules and explain what needs attention on each one. [Check your CRM with SalesBond](https://salesbond.app/).