Two systems for one donor: what can go wrong between your CRM and your mailing tool
In December 2023, a donor asks a Belgian nonprofit to stop sending him mailings and to delete his data. The organisation confirms this several times. According to the nonprofit, he was removed from the CRM straight away. Yet six more mailings reach his inbox in 2024 and 2025.
How is that possible? His contact details were still in a file linked to Mailchimp. The CRM was correct. The system next to it was not. The Belgian Data Protection Authority published the case on 9 November 2026. There was no fine and the organisation remains anonymous. It was a small nonprofit that depends on donations. It did have to show that it had its donors' data back under control.
You do not need to be a lawyer to see what happened. The same donor was stored in two places, and only one of them was updated.
Does this sound familiar?
Many teams work with two systems: a CRM for donor management and a separate tool for email, such as Mailchimp or ActiveCampaign. Before every campaign, a selection moves from one to the other through an export, an import or a connection. At that moment, every donor exists twice.
As long as both are correct, you notice nothing. It gets tricky with small, everyday things:
- A donor unsubscribes from the newsletter, but the CRM does not know.
- A donor gives a new email address over the phone and the mailing tool keeps using the old one.
- A colleague keeps an old export on her desktop and uses it for a small campaign.
- The connection sends data in one direction and nobody realises nothing comes back.
This is not sloppiness. It follows from keeping the same data in several places. Every copy needs its own clean-up, and everyone forgets one now and then.
Why a migration is the ideal moment
When you switch to a new CRM, you are already looking at all your data. You take it out of one system, load it into another and replace the connections. Use that opportunity to count in how many places a donor is stored, and to decide whether that number can come down.
1. How many times is your donor in your systems?
Write down where donor data is stored: CRM, mailing tool, event platform, colleagues' spreadsheets, exports for the accountant. The answer is often surprising. The nonprofit in this case only found out late that the file next to the CRM had been left in place.
2. Why send donor data to a second system?
Some CRM packages can drive both your direct mail and your email campaigns. Your donor data then stays in one system and no copy leaves for an external email provider. You change an unsubscribe, an address or an objection once, and it applies to every channel. That is the biggest advantage: there is nothing left to synchronise. If that is not possible, or if you have good reasons to keep a separate tool, agree which system leads and how changes flow back in both directions.
3. An opt-out must survive the move
Choose deliberately what you need in the new system. People who opted out are usually left behind. The opt-out itself goes with you. Keep a suppression list for this, containing only what you need to avoid contacting someone again.
4. Clean up everywhere, including where you rarely look
Delete or anonymise what you no longer need, in every system where it is stored. An archive is handy for checking something later, but it gives you no reason to keep data longer than necessary.
5. Test with your trickiest donor
Create a test contact who has opted out and run it through the whole chain, from the old CRM to the new one and through every connected tool. If that contact no longer appears in any selection or mailing, your clean-up works. Also appoint one person who decides when in doubt, preferably someone from fundraising or relationship management.
Fewer places, less risk
Every place where a donor is stored is a place where something can be forgotten. A migration gives you a natural moment to count and cut. Do it beforehand, and you will not have to explain later why an email still arrived. Want to prepare a CRM switch? Get in touch with us.
Source: Belgian Data Protection Authority, decision on the merits no. 313/2026 of 9 November 2026.
Want to know where your organisation stands on data quality?
Fundflow helps nonprofits structure their Salesforce environment so every gift, every contact, and every interaction lands in the right place.






