Mailchimp Salesforce Integration: Options, Setup and Sync Rules

What changed: the official app is now paid and built by a partner

Many guides still describe "MC4SF", the free Mailchimp for Salesforce package that Mailchimp published on AppExchange (now AgentExchange). That is out of date. Mailchimp, part of Intuit since 2021, now keeps its help article for that app only for integrations set up before May 1, 2024. Integrations set up on or after that date are supported through the Beaufort 12 listing.

• New integrations: Mailchimp for Salesforce by Beaufort 12. Mailchimp’s integrations directory lists it as a paid app starting at $25 a month per Salesforce org.
• Old installs: if Setup → Installed Packages shows a Mailchimp package from the publisher The Rocket Science Group, you have the legacy app. Beaufort 12 says there is no upgrade path: it is a separate package that you install and configure fresh.
• Running both: you can trial the new app next to the old one, but if both sync actively they can conflict. Plan a cutover, then uninstall the legacy package.

For the wider picture of how Salesforce connects to other systems, see our Salesforce integration guide.

Your options for a Mailchimp Salesforce integration

Other AppExchange connectors exist too. Compare them on the same columns, and ask how they count contacts for billing.

What the official app needs and costs

According to Beaufort 12’s setup guide and pricing page, as of October 2026:

• Salesforce: Professional, Enterprise, Performance or Unlimited Edition. On Professional Edition, list views can’t feed the Data Wizard.
• Mailchimp: any plan. Mailchimp’s own limits still apply: one audience on Free, three on Essentials, five on Standard, unlimited on Premium.
• The connecting user: someone who can install packages and has Metadata API access. Beaufort 12 notes that Salesforce Platform users can’t make the initial connection. The hourly sync runs as a Salesforce user you choose, in that user’s time zone.
• Price: $25 a month per org for 0–10,000 active audience members, then higher bands (for example $100 a month up to 50,000 and $550 up to 300,000); above 300,000 members pricing is quoted. Active members are counted across all connected audiences, so the same address in two audiences counts twice. Unsubscribed, hard-bounced and archived members don’t count. Purchase goes through Salesforce Checkout, billed monthly.
• Trial: 14 days in production. Sandbox installs get a longer test period (the setup guide says 30 days, extendable to 90), and with a paid production license you can use sandboxes for testing without a time limit.

How data moves between Mailchimp and Salesforce

Three paths, three different speeds:

1. Salesforce to Mailchimp in bulk: the Data Wizard reads a report, list view, SOQL query or Salesforce campaign and creates or updates members of one audience. It runs on a schedule or on demand. Reports are capped at 50,000 rows.
2. Salesforce to Mailchimp per record: when someone edits a mapped field on a contact or lead, the change goes to that person’s Mailchimp memberships at once. It updates existing members only, and changes to formula fields or parent records don’t trigger it.
3. Mailchimp to Salesforce: the primary sync, typically hourly, brings in audiences, members, tags, groups, campaigns and, if you turn it on, detailed email activity. It matches members to contacts and leads by email and can create leads or contacts for unmatched members.

Field and object mapping

The app stores Mailchimp data in its own custom objects (member, campaign, email activity, group and others) and links them to your records, so it doesn’t alter standard objects. Beaufort 12 warns against customizing those objects. A typical mapping:

Map only what marketing uses to segment or personalize. Account tier, industry, owner name and lifecycle stage are usually enough. Lookup and ID fields can’t map directly; use a formula field that returns the value instead.

How to set up the Mailchimp Salesforce integration, step by step

Plan for one to two weeks. Installing takes minutes; deciding who gets mailed and cleaning data takes the rest.

1. Design your audiences firstMailchimp recommends one audience organized with tags, groups or segments. Contacts in several audiences are billed several times by Mailchimp and counted several times by the app, and an unsubscribe in one audience doesn’t carry to another. Merge audiences before you connect, unless the groups truly don’t overlap.
2. Check for the legacy appIn Setup → Installed Packages, look for a Mailchimp package from The Rocket Science Group. If it’s there, write down its queries and mappings, plan a cutover date and don’t let both apps sync the same audience for long.
3. Clean SalesforceTurn on duplicate and matching rules, merge leads and contacts that share an email, and fix obviously wrong addresses. Decide whether the Email Opt Out field or the Mailchimp status is the one sales should trust.
4. Install in a sandbox with a test Mailchimp accountUse Beaufort 12’s sandbox install link and connect a separate test Mailchimp account. A sandbox connected to your live account can change real subscribers. If the sandbox was copied from a connected production org, reset the copied connection first, as the setup guide describes.
5. Connect with a dedicated userConnect from the Mailchimp Settings tab with a stable admin user, not a person who might leave, then approve the connection in Mailchimp and return to Salesforce quickly: the handoff expires after a short time.
6. Assign permissions and page componentsGive the app’s permission sets to everyone who edits mapped contacts and leads, or their edits won’t reach Mailchimp. Check that the Mailchimp components appear on contact and lead pages; for person accounts, add them to the account page yourself.
7. Configure the primary syncChoose the sync user and schedule, whether unmatched members create leads or contacts, whether to tick Email Opt Out, and whether to store detailed email activity. Leave activity storage off until you know who will report on it.
8. Map fieldsMap a few fields in each direction and give each one owner. Watch name fields: mapping a full Name field to a First Name merge field produces "Diana Prince Prince".
9. Build the Data Wizard importStart from a report or list view of people who agreed to email, exclude anyone with Email Opt Out ticked, choose tags and groups, and schedule it. Use a Last Modified Date filter on big list views or queries to keep runs small.
10. Test, then go liveUnsubscribe a test address in Mailchimp and check Salesforce after the next sync; edit a mapped field in Salesforce and check Mailchimp; run the wizard twice and confirm no duplicates. Repeat in production, compare member counts on both sides, then remove the legacy package.

Built by Gilzor

Results we’ve shipped

70+products launched

98%delivered on time

85%clients come back

Aviation33%faster baggage weigh-inWeb and Mobile application for Airlines→Healthcare+30%lab test ordersMedical Lab Web and Native Mobile Applications→Retail · Startup700+stores aggregatedMobile application for Grocery shops→

Talk to the people who build it. Tell us about your project and get a free estimate of scope, timeline and cost.

See how we’d approach yours →

Consent and unsubscribes: get this right first

Mailchimp is where people subscribe and unsubscribe, so treat it as the system of record for email consent. Salesforce should show that status, not override it.

• Unsubscribes stay unsubscribed. The Data Wizard never reactivates someone who unsubscribed in Mailchimp, and Salesforce can only update subscribed members. Don’t work around this with the API.
• The wizard doesn’t check Email Opt Out. Filter opted-out contacts out of every source report or query, or they will be added as new subscribers to audiences where they never existed.
• Double opt-in helps. If the audience uses double opt-in, new emails from Salesforce arrive as pending and get a confirmation email instead of being subscribed outright.
• Salesforce-side opt-outs need a rule. If people opt out by phone or with a rep, unsubscribe them through the app’s member component or, on Enterprise Edition and above, an invocable action in a Flow, so the change reaches Mailchimp.

Under the US CAN-SPAM Act, the FTC says you must honor an opt-out within 10 business days, and hiring another company to send doesn’t move that responsibility off you. An hourly sync is well inside that window; a broken sync nobody watches is not.

Common pitfalls and how to fix them

Other email tools: Constant Contact and Salesforce

Constant Contact’s built-in Salesforce integration is simpler and one-way. According to its knowledge base (updated July 2026), it imports contacts and leads from Salesforce into Constant Contact on a schedule you choose, from contact lists, lead lists or Salesforce campaigns. Unsubscribes and email activity are not sent back to Salesforce. It works with Professional (with Web Services API access), Enterprise and Unlimited editions.

That means sales can’t see in Salesforce who opted out. If that matters, add a flow that writes unsubscribes back, through Zapier, an iPaaS or a small custom service, or pick a tool with a two-way sync. The same applies to most email platforms: check which direction unsubscribes travel before anything else.

When a custom integration makes sense

Look past the app when Mailchimp data has to pass through other systems, when you run several Salesforce orgs with different rules, or when you need logs and alerts a compliance team will accept. A custom integration usually has these parts:

• Mailchimp webhooks for subscribes, unsubscribes, profile updates, cleaned addresses and email changes. According to Mailchimp, webhooks need a Standard or Premium plan.
• Salesforce change events (platform events or change data capture) to push updates the other way.
• Batch operations for bulk work. Mailchimp’s Marketing API allows 10 simultaneous connections per user and times out calls after 120 seconds, so large syncs go through its batch endpoint.
• A queue, retries and a log for every record that fails, plus a nightly comparison of counts.

Our API integration cost guide explains where the hours go, and the cost of data integration covers projects that combine several systems. If Mailchimp signups start on your own site, the Salesforce website integration guide covers capturing them cleanly.

When to move to Account Engagement, Marketing Cloud or HubSpot

Mailchimp is a strong email tool. It isn’t built to score leads for a sales team or alert reps when a prospect returns. Consider a CRM-native marketing platform when:

• Marketing qualifies leads for sales and you need scoring, grading and handoff rules tied to Salesforce records. That is Account Engagement (formerly Pardot). Salesforce’s pricing page lists its editions from $1,250 per org per month, billed annually (US list price, October 2026); usage-based features of Marketing Cloud Next need extra credits.
• You send high-volume B2C journeys across email, SMS and other channels: that is Marketing Cloud territory, with a project to match.
• You want marketing and sales tools from one vendor outside Salesforce: HubSpot’s connector is covered in our HubSpot Salesforce integration guide, and Marketo in the Marketo Salesforce integration guide.

Moving is a migration, not an integration: templates, automations, consent records and reporting all have to be rebuilt. If Mailchimp does the sending job well, the app plus clean rules is often the cheaper answer.

Go-live checklist

Tick what is true for your setup.

FAQ

Where Gilzor fits

For most teams the Beaufort 12 app plus clear consent and field rules is the right start. When Mailchimp data has to meet billing, product or several Salesforce orgs, Gilzor’s engineers in Poland and Cyprus can map the data flow, build the integration and support it after launch. See Gilzor’s Salesforce integration services.