Most nonprofits have two donor records.
One is in their CRM: Salesforce, Bloomerang, Raiser's Edge, whatever they're using for development. The other is in their email platform: Mailchimp, Constant Contact, Emma, etc.
These lists start as the same list. They diverge the moment you stop actively syncing them.
A new donor gives online. They land in the email platform but someone forgets to add them to the CRM. A donor updates their email address with you directly and it gets changed in one system but not the other. Someone unsubscribes from email and the CRM still shows them as an active contact. Three years of this and the two lists are substantially different documents with the same name.
It's a common problem that rarely gets fixed, and it shows up in the numbers in ways that are easy to misread.
What divergence actually costs
You're making retention decisions on incomplete data. If your CRM and email platform don't agree on who's in your list, your donor retention rate is calculated from a database that doesn't reflect reality. The lapsed donors you're trying to re-engage might be a different set of people than what the number suggests.
Your email open rates are misleading. Open rate is calculated against total sends. If you're sending to outdated addresses, role accounts, or people who changed jobs two years ago, your open rate denominator is inflated. Your list looks larger than it is. Your engagement looks lower than it is.
Personalization fails. Merge tags pull from email platform fields. If those fields don't match what's in your CRM, the donor who gave $5,000 last year gets an email that addresses them by the wrong name, references the wrong giving history, or skips the personal acknowledgment entirely. These failures are invisible to you and obvious to the recipient.
Compliance risk increases. If a donor unsubscribes and that preference doesn't make it back to your CRM, future communications sent outside the email platform, like direct mail or event invitations, may reach someone who has explicitly opted out. Depending on your jurisdiction, this creates legal exposure.
Where the divergence usually happens
Three moments account for most of the drift:
Online giving. When a donor gives through your online giving platform (Zeffy, Classy, Donorbox, Givebutter), they're added to your email list automatically. Whether they also land in your CRM depends on whether you have an integration, how it's configured, and whether someone is checking the exceptions. Most organizations don't have someone checking the exceptions.
Contact updates. When a donor updates their email address, whether through a form or a call to the office, that update usually happens in one place. Getting it to the other requires a process. Most organizations don't have that process written down.
Manual imports. Event attendees, board member referrals, and business card contacts from the gala get added somewhere, but not always everywhere. And they almost never get added with all the fields needed to make them useful in both systems.
What a basic email audit covers
A list hygiene review for most nonprofits covers four things:
Deduplication. How many records appear more than once? In which system? What's the rule for which record wins?
Bounce analysis. Hard bounces, meaning permanently undeliverable addresses, should be removed from your active list. Most email platforms flag them automatically. Most CRMs don't, because they're not sending email. Syncing bounce data back to the CRM prevents those addresses from being used in other outreach.
Unsubscribe reconciliation. Who has unsubscribed from email? Are those preferences reflected in the CRM? Is there a process for ensuring that future communications respect that preference?
Field matching. Does the information in your email platform match the information in your CRM for the records they share? The fields that drive personalization, like name format, address, and giving history, need to agree.
Fixing it doesn't require new software
For most organizations, a native integration between their email platform and CRM is available and under-configured, or a basic Zapier connection is sufficient to handle the most common sync scenarios.
The technical piece is usually straightforward once someone decides it matters enough to set up. The harder piece is the governance: deciding on the canonical record, writing the rule for what syncs where, and assigning someone to review exceptions on a regular schedule.
Without the governance piece, even a well-configured integration drifts over time. New scenarios emerge. Edge cases accumulate. The lists diverge again.
The goal is a maintained integration, with a named owner and a quarterly check that catches drift before it compounds.
Download the free Nonprofit Data Health Checklist
Joshua Barillas is the founder of Prismatic Consulting, a data services firm built exclusively for nonprofits. Learn more about our services or get in touch at hello@prismaticconsulting.us.