Connecting Mailchimp to Salesforce sounds simple. Install a connector, map a few fields, and your sales and marketing data finally live in one place.
One thing many teams don’t realize at first: the official Mailchimp for Salesforce package is no longer free. It’s now run by Beaufort 12 as a paid subscription billed every month. For a big marketing team that uses every feature, that can make sense. But many organizations only need the basics: keep contacts in sync, respect unsubscribes, and pass a few tags back and forth. For a simple use case like that, you end up paying a recurring fee year after year for something you set up once.
If that sounds like you, a one-time-fee option is worth a look. SyncMailChimp by Tenetizer gives you two-way sync of contacts, subscription status and tags inside Salesforce, with no monthly subscription.
Whichever tool you pick, most integration problems come from a few setup decisions made in a hurry. Here are the seven mistakes we see most often, and how to avoid them.
1. Not deciding which system is the source of truth
Before you sync anything, decide which system owns which data. Without that decision, the two platforms keep overwriting each other.
A setup that works for most teams:
- Salesforce owns names, company details, owner, lifecycle stage and anything sales updates.
- Mailchimp owns email engagement: opens, clicks, bounces and campaign activity.
- Subscription status needs its own rule, which we cover next.
Write this down before you configure field mappings. It takes an hour and saves weeks of cleanup.
2. Letting unsubscribes get lost
This is the most serious mistake, because it has legal consequences under CAN-SPAM, GDPR and similar laws.
Here’s how it goes wrong. Someone unsubscribes in Mailchimp. The sync doesn’t write that back to Salesforce. Later, a rep adds the person to a new Salesforce campaign, the record syncs to Mailchimp again, and they’re back on your list.
To prevent it:
- Map Mailchimp’s unsubscribe status to Salesforce’s Email Opt Out field, or to a custom field if you track consent in more detail.
- Make sure opt-outs sync both ways, and quickly.
- Never let a sync resubscribe someone Mailchimp has marked as unsubscribed or cleaned.
If your connector only syncs one way, look closely at how it handles opt-outs.
3. Syncing Leads and Contacts without a duplicate plan
Salesforce stores people as both Leads and Contacts. Mailchimp stores them as one audience member per email address. When the same email exists as a Lead and a Contact, or on two Contacts, the connector has to guess which record to update.
Before you connect:
- Run duplicate rules and clean up existing duplicates in Salesforce.
- Decide what happens when a new Mailchimp subscriber matches an existing Contact. Update the Contact, don’t create a new Lead.
- Check how your connector handles converted Leads. Engagement history should follow the person onto the Contact.
4. Creating a separate Mailchimp audience for everything
Many teams build one Mailchimp audience per segment: newsletter, customers, event attendees and so on. Mailchimp charges by contact count, and someone in three audiences can be counted three times. It also makes the Salesforce sync much harder to manage.
A better approach is one main audience, segmented with tags, groups or merge fields driven by Salesforce data. Salesforce campaigns or field values decide who gets which tag, and Mailchimp segments do the rest.
5. Treating tags as one-way
Tags are where most of the segmentation value comes from, and they’re often the weakest part of an integration.
Ask two questions about your setup:
- If a Salesforce field changes, for example a customer moves from “Trial” to “Paid”, does the Mailchimp tag update automatically?
- If marketing adds a tag in Mailchimp, does it show up anywhere in Salesforce so sales can see it?
If the answer to either is no, your segments will go stale and your team will end up exporting CSVs again.
6. Ignoring API limits
Every Salesforce org has a daily API request limit based on its edition and licenses. Many third-party sync tools use your inbound API calls every time they check for changes. If you also run other integrations, such as payment tools, forms or ERP connectors, a busy sync can use up your allowance and break other systems for the rest of the day.
Also note that Salesforce Professional Edition doesn’t include API access by default. You may need to ask Salesforce to enable it before any connector will work.
Check with your integration provider how often they sync and roughly how many API calls a typical day uses. Then compare that with your org’s limit under Setup → Company Information.
7. Syncing everything “just in case”
It’s tempting to map every field and every record type. The result is a slower sync, more API usage, more storage and more things that can break.
Start small:
- Sync only the records you actually email.
- Map only the fields you’ll use for personalization or segmentation.
- Bring back only the engagement data sales will act on, such as recent opens, clicks and campaign membership, rather than every email event ever recorded.
You can always add more later. Removing clutter after the fact is much harder.
Choosing the right integration method
There are four common ways to connect the two platforms:
- The official Mailchimp for Salesforce app on AppExchange. It’s well established, but it’s a paid monthly subscription, which adds up over time for simple sync needs.
- No-code tools like Zapier or Outfunnel. They’re quick to set up but can get expensive at volume and add another system to manage.
- A custom API integration. It’s fully flexible but needs developers to build and maintain.
- A Salesforce-native sync app with a one-time fee. It runs inside your org, avoids ongoing subscription costs, and can reduce the external API traffic described above.
The right choice depends on your data volume, your budget, and whether you need true two-way sync for tags and subscription status. For a side-by-side comparison of these options, see this Mailchimp Salesforce integration guide.
Final checklist before you go live
- Source of truth decided and documented for each field
- Unsubscribes and cleaned emails sync back to Salesforce
- Duplicates cleaned and a matching rule agreed
- One main Mailchimp audience, segmented with tags
- Tags update automatically when Salesforce data changes
- API usage checked against your org’s daily limit
- Only needed fields and records mapped
- Tested in a sandbox with real sample data before going live
Get these right and the integration becomes something your team relies on every day instead of something they work around.
Frequently asked questions
Is Mailchimp for Salesforce free?
No. The official Mailchimp for Salesforce app is now a paid monthly subscription provided by Beaufort 12. Some alternatives charge a one-time fee instead.
Can Mailchimp and Salesforce sync both ways?
Yes, but not every tool does it fully. Check that contacts, subscription status and tags all sync in both directions, not just contacts from Salesforce to Mailchimp.
Does syncing Mailchimp use Salesforce API calls?
Most external connectors do, each time they check for changes. Salesforce-native apps that run inside your org can reduce this.
Should I sync Leads, Contacts, or both?
Sync whichever records you actually email. If you sync both, set clear duplicate and matching rules first so the same person isn’t created twice.