Mailchimp integration one list instead of five exports
Mailchimp sends campaigns well and keeps templates well. It does not know who bought from you in March, which stage the deal sits at in the CRM or whether a rep has already called. We connect it to the CRM, the shop and the warehouse through Marketing API v3 and webhooks: one recipient list, an unsubscribe in the CRM within the minute, segments built from system data instead of a spreadsheet.
- 14 daysfrom the workshop to the first automation running on your own Mailchimp list, on real data
- 2 to 6 weeksfrom the workshop to a connected Mailchimp, depending on the number of lists, the state of the database and whether the shop is in scope
- 5 eventshow many webhook events Mailchimp sends at list level: subscribe, unsubscribe, profile, upemail and campaign
The problem
Why does the recipient list drift away from the CRM?
A Mailchimp account rarely holds one list. One is left over from a webinar, one from a trade show, and someone uploaded a third from a spreadsheet the week before Black Friday. The same address sits in two of them, in one with a typo in the company name, and in the CRM the same person shows up as a customer who bought in March. Before every send, somebody sits down to export files and glue them together.
The second problem is quieter and costs more. An unsubscribe in Mailchimp works at list level, so a person who opted out of the newsletter still receives a campaign from the second list. The CRM hears nothing about it, because nobody copies that fact across. A rep calls someone who withdrew their marketing consent a week earlier.
That is no longer a question of tidiness. Consent is one of the lawful bases for processing under Regulation 2016/679, Article 6(1)(a), and Article 7(3) of the same regulation gives the right to withdraw consent at any time and requires withdrawal to be as easy as giving it. Marketing email carries a second rule on top: Directive 2002/58/EC, Article 13 makes prior consent the condition for sending it at all. If an opt-out stays inside Mailchimp and never reaches the CRM, the company has nothing to show for who withdrew consent and when.
- Before every send somebody glues a list together out of two exports and a spreadsheet
- A person who unsubscribed from one list still gets a campaign from the second
- A rep calls a contact who has withdrawn their marketing consent
- The same address in two lists is billed twice on your plan
- Opens and clicks stay in Mailchimp while revenue stays in the CRM
Why now
What changed, so that connecting Mailchimp takes weeks rather than a quarter?
Mailchimp exposes Marketing API v3 with Lists, Members, Campaigns, Automations and Reports, and authentication runs on an API key in the Authorization header. Webhooks are registered per list through POST /lists/{id}/webhooks and deliver five events: subscribe, unsubscribe, profile, upemail and campaign. An unsubscribe can therefore reach the CRM in the same minute somebody clicked it. The resources and the limits behind them are set out in the Mailchimp developer documentation.
The second change is about the division of labour. Customer Journeys handle a simple path well: sign-up, welcome, a reminder a week later. Once a condition depends on the deal stage in the CRM, on order value over the last quarter and on whether a rep has already called, the path grows into a dozen or more branches maintained by hand. So we move the decision to n8n, Make or a custom API integration, and Mailchimp stays what it is good at: sending and templating.
The third change is the AI agent. A rule will sync the list, but it will not answer the question of how many people in the customer segment unsubscribed this month. BOND, our company AI agent, answers that in a plain sentence in 5 to 10 seconds, with no Mailchimp login and no report to build.
What changes
What does the marketing team get?
One list instead of five exports
We settle which system is the system of record for the address, the consent and the company name, and that system overwrites the rest. An address from a form, from the CRM and from the shop lands on one Mailchimp list, reduced to a single record.
Matching on email address and company domain instead of a name everyone spells differently
Unsubscribes and consent written back to the CRM
The unsubscribe webhook records the date and the channel of the opt-out against the contact in the CRM. A rep sees it on the record before making the call, and the company has a consent history it can show.
Sign-up date, opt-out date and consent source in one place, on the CRM contact
Campaigns built from system data
A segment is built from what you actually know: the deal stage in the CRM, the category of the last order, basket value, renewal date. Instead of uploading a file, you pick a segment that keeps itself current.
PATCH /lists/{id}/members/{hash} sets the tag and the segment field when the CRM stage changes
Send stats next to the rest of your data
Opens, clicks and unsubscribes from the Reports API land in BigQuery once a day, next to CRM and order data. You can see whether the campaign delivered revenue, not only whether it delivered clicks.
A daily batch into BigQuery, the same tables as order and deal data
Personalisation without editing messages by hand
Merge Tags are filled from CRM fields: first name, company name, date of last activity, account owner. The content changes at field level in the template, so nobody edits a campaign by hand for each group.
CRM fields injected into the template, one campaign instead of four variants
Questions about the list in a plain sentence
How many contacts are in the customer segment, who unsubscribed after the last campaign, how many people on the list bought this quarter. The AI agent answers from Mailchimp and the CRM at once.
An answer in 5 to 10 seconds, with no report and no logging into two systems
And in your company
What if our Mailchimp is simple and does the job?
Mailchimp is usually the first email tool a company buys and it often stays for years. Four sentences come up most often, and this is how we answer them. If the question next to this one is about the sequences themselves, they have their own page on automatic email sequences, and the layer above the tools, meaning one definition of a lead and one way of measuring a campaign, sits on marketing automation.
We have one list and we send a newsletter once a month.
Then an integration solves a problem you do not have yet, and we will say so at the consultation. It makes more sense to fix the form and the consent capture on your website first. We come back to this when there is more than one list, or when sales starts asking who unsubscribed from the newsletter.
We keep the list in a spreadsheet and upload a file before every send.
That is the most common starting point and the first thing the workshop changes: the spreadsheet stops being a quiet second CRM and the data goes back to the system that answers for it. Uploading a file stays as a fallback route, not as the process.
Mailchimp has its own automations, why add anything?
For a simple path, native Customer Journeys are enough and we will tell you that. An external orchestrator earns its place when the condition depends on the CRM stage, the order history and the rep's work at the same time, because that is when the native path grows into a dozen or more branches somebody has to patch by hand.
We want to leave Mailchimp, we pay for contacts we never touch.
First we check how many of those contacts are duplicates across lists, because the same address in two lists is billed twice. If the problem survives the cleanup, the workshop compares two routes: Mailchimp as pure sending with the logic outside it, or a tool with a deeper link to the CRM.
- Email marketing
- Mailchimp: Marketing API v3, Lists and Members, Segments, Automations, Reports, E-commerce API
- CRM
- HubSpot, Pipedrive, Salesforce, Zoho CRM
- Sales and shop
- Shopify, WooCommerce, PrestaShop, BaseLinker, Magento
- Data and reporting
- BigQuery, Google Sheets, Google Analytics, SQL databases
- Team tools
- Google Workspace, Microsoft 365, Slack, Notion
- Automation layer
- n8n, Make, Zapier, custom API integrations
What reaches Mailchimp, where from, and what comes back out
The exchange we build most often. The direction of each row is settled at the workshop, because until it is clear which system is the system of record for the address and the consent, syncing only spreads the mess faster.
| Data | Direction | Endpoint or event |
|---|---|---|
| New sign-up from a form | Mailchimp to CRM | subscribe webhook, with the campaign tag and the sign-up source |
| Opt-out and withdrawn consent | Mailchimp to CRM | unsubscribe webhook, date and channel stored on the contact |
| Email address change | Mailchimp to CRM | upemail webhook, so the CRM does not create a second contact |
| Deal stage and closed-won | CRM to Mailchimp | PATCH /lists/{id}/members/{hash}, tag and segment field |
| Order from the shop | Shop to Mailchimp | Purchase Event through the E-commerce API, triggers the post-purchase sequence |
| Opens, clicks, unsubscribes | Mailchimp to warehouse | Reports API, a daily batch into BigQuery |
| First name, company, last activity | CRM to Mailchimp | Merge Tags filled from CRM fields |
Marketing API v3 allows 10 simultaneous connections per key, so bulk changes to a list run as batch operations rather than a loop over contacts. The member identifier is a hash of the lower-cased address, which means an address change is an identifier change and needs handling of its own.
How we work
Five steps from several lists to one, connected to the CRM
Each step ends with something you can judge before you decide on the next one.
Workshop
We write down every list in the account, where it came from and who sits on two of them at once. We check where you collect consent, what happens to it after sign-up and how long preparing one send takes today.
Data exchange design
We settle the system of record for the address, the consent, the company name and the sales stage, the direction of every sync and the rule for resolving conflicts. We pick the tool: native Customer Journeys, n8n, Make or a custom API integration. We also write down which data goes into Mailchimp and which stays in the CRM.
Rollout in parallel
The sync runs on a copy of the list, alongside the current process, with the exports still in place. We test duplicate merging, unsubscribes, address changes and contacts with no consent. Only then do we send the first campaign from a segment built out of system data.
Switchover and training
Once it checks out we move to production with monitoring on sync errors. Marketing learns to create a segment, add a field to a template and read the report in the warehouse without raising a ticket with us.
Measurement at 30 and 90 days
We look at how many contacts the merge removed, how many unsubscribes reached the CRM and whether segments built from sales data outperform the uploaded file. If that window shows the company is outgrowing Mailchimp, we say so plainly.
Before and after
How preparing one send changes
Before
- A CRM export, a shop export and a spreadsheet glued together by hand before the campaign
- Only marketing sees the unsubscribe, sales finds out during the call
- The segment comes from a file, so it is current on the day it was uploaded
- The campaign result stops at opens and clicks
After
- There is one list and it is current, the send starts by picking a segment
- The opt-out sits on the CRM contact in the same minute
- The segment updates itself when the stage or the order changes
- Opens and clicks sit in the warehouse next to revenue from the same period
The first campaign from a CRM-linked segment usually goes out in the second week after the workshop. List quality and the effect of segments on revenue are judged at 30 and 90 days.
For the person signing this off
What the marketing director gets out of it
You stop answering the question of whether the list is current, because currency follows from the sync rather than from somebody's memory. Instead you have one contact count, one source of consent and an opt-out history you can put in front of a regulator or a client audit.
The second thing carries more weight in a board conversation. Once send data sits in the warehouse next to orders, you talk about a campaign in revenue for the period rather than in open rate. That is an argument in a budget conversation that is usually missing from the table today.
- One list and one system of record for marketing consent
- Opt-out and consent date visible in the CRM, not only in Mailchimp
- The sync run in parallel, so the exports keep working until testing ends
- Segments and template fields changed by marketing, with no ticket to us
What it costs
The workshop has a fixed price, the integration is quoted after it
The process workshop costs EUR 3,500 net per week and runs from one to seven weeks depending on scope. For Mailchimp one week is usually enough, because the process is narrow: from sign-up to send. The integration is quoted after the workshop, once we know how many lists there are, how many of them can be merged and whether the shop and the warehouse are in scope.
You pay Mailchimp for the plan directly, and the automation tool goes to its own vendor, or costs nothing at all when n8n runs on your infrastructure. Where an AI agent is in scope, the model provider charges EUR 0.005 to 0.07 per query. No commission on top from us.
Process workshop
EUR 3,500 net
per week, usually one week for Mailchimp
A self-contained piece of work. It ends with a map of lists, consents and data exchange, plus a plan you can execute without us.
- An inventory of every list, the duplicates between them and where the addresses came from
- The system of record for the address, the consent and the sales stage, agreed in writing
- A tool recommendation: Customer Journeys, n8n, Make or a custom API integration
- The measures to judge it by at 30 and 90 days
- Most popular
Workshop and Mailchimp integration
Quoted after the workshop
scope follows from the number of lists, systems and the state of the database
The option most companies choose. Mailchimp connected to the CRM and the shop 2 to 6 weeks after the workshop, tested on a copy of your list.
- Everything in the workshop
- Lists merged and cross-list duplicates removed
- subscribe, unsubscribe, profile and upemail webhooks wired into the CRM
- Segments from CRM and order data, Merge Tags filled from the CRM
- Parallel rollout, switchover and monitoring on sync errors
- Training so marketing works on segments on its own
Integration and an AI agent for marketing
Quoted after the workshop
for teams that ask about the list and the results several times a week
Everything in the integration plus BOND, which answers questions about the list, the opt-outs and campaign results in a plain sentence.
- Everything in the Mailchimp integration
- Reports API batched into BigQuery, next to sales data
- An AI agent wired into Mailchimp and the CRM, an answer in 5 to 10 seconds
- Alerts on a spike in unsubscribes and on a campaign that did not deliver revenue
The workshop ends with a document that stands on its own without us: a map of lists, consents and data exchange. If it turns out that merging two lists and setting up a native path in Mailchimp is all you need, we say so and show you how, instead of selling you an integration you do not need.
Frequently asked questions
What does a Mailchimp integration with a CRM give you?
Three things: one recipient list instead of several exports, opt-outs and consent visible in the CRM within the same minute, and segments built from system data, meaning the deal stage or the order history. Mailchimp keeps doing what it is good at, which is sending and templating.
How long does a Mailchimp integration take?
One week of workshop and 2 to 6 weeks of work. The first automation usually runs on your list 14 days after the workshop. The upper end applies when several lists have to be merged, the shop has to be connected and the data has to reach the warehouse. The longest item is often the list cleanup rather than the integration itself.
Will an unsubscribe in Mailchimp reach our CRM?
Yes, that is what the unsubscribe webhook registered at list level does. We store the date and the channel of the opt-out on the contact in the CRM, so a rep sees it before picking up the phone. Worth knowing: an opt-out in Mailchimp applies to one list, so with several lists you have to decide separately what unsubscribing means for the company as a whole.
Is Mailchimp enough, or do we need n8n or Make?
For a simple path, such as a welcome after sign-up and a reminder a week later, native Customer Journeys are enough and we will tell you so. An external orchestrator earns its place when the condition depends on the CRM stage, order value and the rep's work at once, because that is when the native path grows into a dozen or more branches maintained by hand.
How do you build a segment from order data?
An order from the shop reaches Mailchimp as a Purchase Event through the E-commerce API, while the deal stage and tags are set with a PATCH on the list member. That way a segment such as bought in the last quarter or deal at proposal stage keeps itself current, with no file to upload before every send.
Can send stats be joined with sales data?
Yes. Opens, clicks and unsubscribes from the Reports API go into BigQuery as a daily batch, next to CRM and order data. Then a campaign can be discussed in revenue for the period rather than in open rate alone. We set the measurement up so the numbers can be compared with the same period a year earlier.
When does a company outgrow Mailchimp?
Usually when campaign logic depends on the sales stage rather than on email behaviour alone, when the plan is billing contacts nobody writes to, or when you need several brands and markets in one tool. Before we suggest changing tools, we check how much of that a list cleanup solves on its own. We settle it at the workshop, with numbers from your account.
What happens to marketing consent in a sync like this?
We send Mailchimp only the fields a send and a segment need, while the consent and its withdrawal stay in the system that is their system of record. Regulation 2016/679 requires withdrawal to be as easy as giving consent in Article 7(3), so a one-click opt-out in an email has to reach the CRM without anyone retyping it. At the workshop we also set how long you keep contacts that never opened a single campaign.
Let us count your lists and see how many can be merged
The free consultation takes 30 minutes. You tell us how many lists you have in Mailchimp, where they came from and how you prepare a send today. We show you what can be merged and connected to the CRM straight away, and what needs the consent side sorted out first. You do not have to share access to any system at this stage.
We run at most two rollouts at a time, so that someone is actually sitting on each of them.
Book a free consultationPS. If your last send was preceded by gluing two exports and a spreadsheet together, that is exactly this problem. With Mailchimp connected to the CRM, a send starts by picking a segment, and sales sees the opt-out too. It starts with a map of lists and consents, which is the workshop.