# Salesforce Mailchimp integration: opt-outs, lead status and who owns the sync

https://salesbond.app/blog/salesforce-mailchimp-integration-opt-out-lead-status-owner-check/
Published: 2026-10-27 · Updated: 2026-11-14

The Salesforce Mailchimp integration runs through the Mailchimp for Salesforce app, a third-party connector, or Zapier, and only the current version of that app, with its Email Opt Out option switched on, decides which system owns the unsubscribe. Pick one source of truth for opt-outs, then check weekly for contacts who unsubscribed in Mailchimp but are still active leads in Salesforce.

The setup itself is short. Install Mailchimp for Salesforce from AppExchange, connect your Mailchimp account, and the app tries to add its components to your Contact and Lead page layouts on its own (if your pages aren’t activated, you finish that part by hand). That’s the developer’s whole three-step guide, and the sync starts running in the background as soon as the connection is made ( [Beaufort 12: Setup guide](https://www.beaufort12.com/mailchimp/support/setup-guide)). Everything after that is a decision about data.

## Three ways to set up the Salesforce Mailchimp integration, and the one we’d pick

When people say “the Salesforce Mailchimp integration” they usually mean Salesforce Integration by Beaufort 12, the app Mailchimp lists on its own integrations page. It is paid, starting at $25 USD per month per Salesforce org (checked November 2026), and the listing describes a bi-directional sync with email activity history inside Salesforce ( [Mailchimp: Salesforce Integration by Beaufort 12](https://mailchimp.com/integrations/salesforce/)). Installing in production starts a free 14-day trial. It works with Professional, Enterprise, Performance and Unlimited editions, in Classic and Lightning ( [Beaufort 12: Setup guide](https://www.beaufort12.com/mailchimp/support/setup-guide)). If your org was connected before May 1, 2024, you are on Mailchimp’s older application; Mailchimp’s help article covers that one and sends anyone set up on or after that date to Beaufort 12 for support ( [Mailchimp: About Mailchimp for Salesforce](https://mailchimp.com/help/about-mailchimp-for-salesforce/)).

The second route is another AppExchange connector or something a consultant built. Plenty of orgs run a custom pipe someone set up two admins ago.

The third is Zapier, where the Salesforce templates are marked Premium. On the Mailchimp side there’s a New Unsubscriber trigger and an Unsubscribe or Delete Contact action ( [Zapier: Mailchimp + Salesforce](https://zapier.com/apps/mailchimp/integrations/salesforce)).

We’d take the app for a team that lives in Salesforce, because the opt-out logic is already written and documented. Zapier is fine for one job, like pushing a Mailchimp unsubscribe into a Salesforce field. As the whole integration it’s a bad idea: every mapping you add is a Zap nobody remembers.

## What syncs, and what does not

Audiences and members come into Salesforce on the primary sync, typically within an hour. A change made from the Salesforce side reaches Mailchimp right away. Each member record has a status such as subscribed, pending, unsubscribed, non-subscribed or cleaned ( [Beaufort 12: Audiences](https://www.beaufort12.com/mailchimp/support/audiences)). Email activity shows up on the Salesforce record, and that’s the part reps actually notice. Field Mappings can also create a Lead from a Mailchimp member ( [Beaufort 12: Setup guide](https://www.beaufort12.com/mailchimp/support/setup-guide)), handy until you ask who owns them.

What doesn’t sync is the stuff a sales manager cares about. Lead Status, Lead Owner and the next task never leave Salesforce, and Mailchimp has no idea what a lead is. So a campaign click can look like a hot signal while the lead sits with no owner and the status it was created with. We made the same point about opens and clicks for [Zoho CRM and Mailchimp](https://salesbond.app/blog/zoho-crm-mailchimp-integration-opt-out-lead-status-owner/): the campaign tool reports on the campaign, the CRM reports on the conversation.

One more thing before you map fields. On the older Mailchimp application, Salesforce data always took priority: an edit in Salesforce overwrote Mailchimp on the next sync, never the other way round ( [Mailchimp: About Mailchimp for Salesforce](https://mailchimp.com/help/about-mailchimp-for-salesforce/)). That rule is harmless for a phone number and risky for consent.

## Opt-outs: Mailchimp wins, and the current app enforces it

On the current Beaufort 12 app, with the Email Opt Out option switched on, an unsubscribe in Mailchimp checks the standard Email Opt Out field in Salesforce, and only in that direction. Which app you are on, and whether that option is on, decides how much checking you have to do.

Our rule for any CRM: the opt-out lives where the person clicked it, and the CRM copies it into a real field, here the standard Email Opt Out checkbox on Contact, Lead and Person Account. A Mailchimp unsubscribe comes back on the primary sync and shows on the membership component. If you’ve enabled the option and the person’s related members are Unsubscribed, Email Opt Out gets checked; if any member goes back to Subscribed, it’s unchecked on the next run. If a rep unchecks the box by hand, the next primary sync checks it again while the person is still unsubscribed in Mailchimp ( [Beaufort 12: Email Opt Out](https://www.beaufort12.com/mailchimp/support/email-opt-out)). The same page warns that the field isn’t exclusive to the integration, so users, processes and other apps can change it too.

![Flow: Mailchimp Unsubscribed sets Email Opt Out in Salesforce; a rep unchecks it and the next primary sync checks it again](https://salesbond.app/wp-content/uploads/2026/10/salesforce-mailchimp-integration-opt-out-lead-status-owner-c-2.png)

Switch the option on. Then tell the team the honest version: unchecking the box only makes the record wrong until the next sync. An unsubscribed person isn’t made active again automatically; the developer documents two deliberate ways back, moving the member to Subscribed in the membership component or a Resubscribe Member invocable action ( [Beaufort 12: Audiences](https://www.beaufort12.com/mailchimp/support/audiences)). Decide who is allowed to use them.

Two traps remain. The Data Wizard doesn’t check Email Opt Out before it creates new subscribers, so your import source has to leave opted-out people out; it won’t resubscribe someone already unsubscribed, but it can add an opted-out lead who was never in that audience. And Mailchimp treats each audience separately, with no global unsubscribe, so a person can leave one audience and still be subscribed to another ( [Beaufort 12: Email Opt Out](https://www.beaufort12.com/mailchimp/support/email-opt-out)). On the older Mailchimp application, an unsubscribe in Mailchimp left the Email Opt Out field as it was, and an opt-out set in Salesforce left the person subscribed in Mailchimp ( [Mailchimp: About Mailchimp for Salesforce](https://mailchimp.com/help/about-mailchimp-for-salesforce/)). If that describes your org the weekly check below is doing the job the sync should.

## The Monday report: unsubscribed but active, and campaign leads nobody owns

Build two Salesforce reports once and run them every Monday. Ten minutes.

1. Unsubscribed but still being worked: a Leads report and a Contacts report filtered on Email Opt Out equals True, with an open Task or an open Opportunity on the record. Every row is a person who told Mailchimp to stop while a rep plans to call or write. The rep may still call; what matters is that no sales email sequence goes out.
2. Campaign leads with no owner. Filter Leads on the Lead Source your campaign import uses, Lead Owner equal to a queue or the integration user, and Lead Status still at the default for new leads. Add a column for next activity. A row here is a lead your marketing paid for that no human has touched.

Send each row to the owner, or whoever will become the owner, as state, reason, action: “Dana Lee, Email Opt Out true since the sync on the 14th. Reason: open task, call on Wednesday. Action: call as planned, no sequence, mention the opt-out.”

If the first report is empty three Mondays running, the sync is doing its job and you can go monthly. If the second one keeps filling up, the problem is your assignment rules. We walked through the ownership half of this for [Salesforce Account Engagement handoffs](https://salesbond.app/blog/salesforce-account-engagement-lead-handoff-sales-manager-check/), and the same rule holds there, so every campaign lead gets a named owner before anyone counts it as pipeline.

## Who owns the sync user

The integration runs as a Salesforce user, and someone has to be responsible for that user. In most orgs we see, teh connection was made with an admin’s login, the admin left, and the sync kept running under that account until something broke. Beaufort 12 doesn’t recommend using a Platform license user as the sync user at all ( [Beaufort 12: Setup guide](https://www.beaufort12.com/mailchimp/support/setup-guide)). Make it a named decision: which user the app is connected as, who hears about it when the sync fails, and who may touch the field mappings and the Email Opt Out option.

One person owns the integration. The sales manager owns the reports. Put the two Monday reports on the the manager’s dashboard and the integration user’s name in the team wiki, and that’s the whole governance.

For a Pipedrive team the same split looks different in the tooling; we covered it in [Pipedrive and Mailchimp: who owns unsubscribes](https://salesbond.app/blog/pipedrive-mailchimp-sync-lead-status-opt-out/). We build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. It analyses deal and customer data, finds risks and explains what needs attention, so a manager isn’t the one building every report; if you want to see what it finds, [check your CRM with SalesBond](https://salesbond.app/). The opt-out rule is still yours to set.
