Article content and detailed guides remain in English. The selected language applies to controls and quick instructions.

Back to articles

Data Cleaning for Nonprofit Donor Databases, Fundraising CRMs, Grant Management Systems and Volunteer Management Platforms

On this page

Why Donor Data Quality Matters

Nonprofit organisations depend on accurate donor data for fundraising appeals, grant reporting, tax receipts, volunteer coordination, event management and relationship cultivation. Dirty donor data directly costs nonprofits money and damages relationships:

Problem Cause Impact
Duplicate donor records Same person entered multiple times (different name spellings, maiden/married name, nickname vs. formal name, multiple email addresses) Donor receives multiple appeals (appears unprofessional and wasteful); giving history split across records (major donor appears as multiple small donors; misses recognition thresholds); inaccurate fundraising totals; wasted printing and postage
Incorrect contact information Address, email or phone not updated after move, job change or email change Appeal never arrives; tax receipt undeliverable; event invitation not received; donor feels forgotten; lapsed donor who would have given if asked
Household vs. individual confusion Husband and wife have separate records but give jointly; family foundation has individual and entity records Giving credited to one spouse but not the other; recognition misattributed; solicitation sent to both when one is sufficient; household giving total not visible
Gift attribution errors Gift recorded under wrong fund, campaign, appeal or solicitor; matching gift not linked; pledge payment not matched to pledge Fund reports inaccurate; campaign ROI misstated; solicitor credit wrong (affects staff performance evaluation); donor's giving history incomplete
Deceased donors receiving appeals Donor passed away but record not flagged Appeal sent to deceased person (distressing to family; damages reputation); wasted resources; legal and ethical concerns
Lapsed donor misidentification Donor's recent gift is in a different record (duplicate); appears lapsed when they are active Lapsed-donor appeal sent to active donor (insulting); donor segmentation inaccurate; retention metrics misleading

Common Data Quality Problems by Platform

Platform Common problems Root cause
Bloomerang Duplicate constituents from online donation form entries that do not match existing records; incomplete merge of imported records; inconsistent interaction tracking Online forms create new records when email or name does not exactly match existing record; imported data (events, peer-to-peer campaigns) not mapped to existing constituents
DonorPerfect Duplicate records from multiple data entry points (online, events, walk-ins); gift coding inconsistencies across staff; solicitation code sprawl Multiple staff entering data without checking for existing records; no standardised gift coding guide; solicitation codes created ad hoc
Little Green Light Duplicate records from import; household relationships not linked; custom field inconsistency CSV imports from events, campaigns and third-party platforms not deduplicated before import; manual relationship linking not completed
Blackbaud Raiser's Edge NXT Constituent code inconsistency; duplicate records from data migration (RE7 to NXT); relationship linking incomplete; appeal and package code sprawl Complex data model with many optional fields leads to inconsistent data entry; migration from RE7 to NXT creates duplicates if not carefully mapped; appeal/package codes created by different staff without coordination
Salesforce NPSP Duplicate accounts and contacts; opportunity record inconsistency; campaign member tracking gaps; custom field proliferation Salesforce's flexibility means every org implements differently; NPSP data model (household accounts, organisation accounts, individual contacts) requires understanding to maintain; multiple integrations create duplicate records

Cleaning Workflow

Step 1: Export and audit

Action Details
Export all constituent records Export from your CRM: name (first, last, organisation), email, phone, address, giving history (total, last gift date, last gift amount, lifetime giving), record creation date, record source, constituent type (individual, organisation, household)
Count records Total constituent records; active records (gift in last 24 months); lapsed (no gift in 24+ months); never-given (no gift on record)
Identify data completeness Percentage of records with: email address; mailing address; phone number; giving history. Records with no contact information and no giving history are likely junk
Export email addresses for deduplication Upload your constituent email export (CSV) to Email Extractor to identify duplicate email addresses across your database; same email in multiple records = definite duplicate constituent

Step 2: Deduplicate

Deduplication method What it catches How to implement
Exact email match Same email address in multiple records Upload email column to Email Extractor; export results; match back to constituent records; merge duplicates
Exact name + address match Same person entered twice with same contact info Sort by last name + first name + ZIP code; visual scan or spreadsheet formula for exact matches
Fuzzy name matching Misspellings, nicknames, name variations (Rob/Robert, Bill/William, Liz/Elizabeth, Mike/Michael) Use CRM's built-in duplicate detection (most have fuzzy matching); or export and use record matching tools
Household matching Spouses, partners, family members at same address Sort by address; identify multiple records at same address; link as household or merge as appropriate
Organisation matching Same organisation entered under different names (acronym vs. full name, "Inc." vs. "Incorporated", "The" prefix) Sort by organisation name; visual scan for variations; standardise naming convention

Step 3: Standardise

Data field Standardisation rule Example
Name prefix (salutation) Standardise to: Mr., Mrs., Ms., Dr., Rev., Hon., etc.; remove informal salutations from formal field "mr" becomes "Mr."; "Doctor" becomes "Dr."
First name Use formal first name in first-name field; store nickname/preferred name in separate field First name: "Robert"; Preferred name: "Bob"
Organisation name Standardise abbreviations; remove "The" from sort name; consistent capitalisation "the american red cross" becomes "American Red Cross" (sort as "American Red Cross")
Address USPS standardised format; verify deliverability through NCOA (National Change of Address) processing "123 Main Street, Apartment 4B" standardised to "123 MAIN ST APT 4B"
Phone Consistent format: (555) 555-5555 or 555-555-5555; remove extensions to separate field; identify mobile vs. landline "5551234567" becomes "(555) 123-4567"
Email Lowercase; trim whitespace; verify format " John@Example.COM " becomes "john@example.com"
Gift codes (fund, campaign, appeal) Publish a gift coding guide; standardise existing codes; merge duplicates; retire unused codes Fund: "GEN" (General Operating); "GALA23" (Gala 2023); "ENDOW" (Endowment). Merge "General", "Gen Fund", "Operating" into "GEN"

Step 4: Verify and update

Action Method Frequency
Email verification Run email list through verification service; remove hard bounces; update records with corrections Before every major email campaign; at minimum annually
Address verification (NCOA) Run mailing list through NCOA processing (USPS National Change of Address database) Before every direct mail campaign; at minimum annually; required for nonprofit bulk mail rates
Deceased identification Subscribe to deceased identification service (commercial providers match against death records) Annually; before year-end appeal
Phone number verification Call or text to verify; remove disconnected numbers When preparing for phonathon or peer-to-peer texting campaign
Employer/occupation update For donors who give $200+ (federal reporting threshold for some nonprofits); verify employer through public records or donor surveys Annually; at gift acceptance for reportable gifts

Household Giving and Recognition

Scenario Data approach Recognition approach
Married couple, both give separately Link as household; track individual giving and household total Recognise household total for donor wall, annual report, giving level; send individual tax receipts
One spouse gives, other does not Link as household; primary donor is the giver; spouse is linked constituent Solicitation to giver; correspondence addressed to both (if preference allows); recognition includes both names
Family foundation makes gift Organisation record for foundation; linked to individual records for family members Tax receipt to foundation; recognition may credit foundation name and/or family name (per donor preference)
Donor gives through workplace (matching gift, workplace campaign) Individual gift linked to matching gift; employer record linked to matching gift programme Recognise individual giving including matched amount; credit matching gift company in corporate partnerships
Donor advised fund (DAF) gift Gift recorded from DAF sponsor (Fidelity Charitable, Schwab Charitable, etc.); linked to individual donor who recommended the gift Tax receipt to DAF sponsor (not to individual); recognition credits the individual donor (their recommendation); stewardship directed to individual
Anonymous gift Gift recorded with designation "anonymous"; donor name in restricted access field (development officers only) No public recognition; private acknowledgement to donor per their preference; not included in public donor lists

Metrics

Metric Problem threshold Healthy threshold How to measure
Duplicate rate Over 10% of records are duplicates Under 3% Run deduplication analysis; count identified duplicates / total records
Email deliverability rate Under 90% Over 97% Hard bounces / emails sent in last campaign
Direct mail return rate Over 5% Under 2% Returned mail pieces / total mailed (run NCOA before mailing)
Record completeness (email) Under 50% of active donors have email Over 75% of active donors have email Donors with email / active donors (gift in last 24 months)
Record completeness (address) Under 70% of active donors have mailing address Over 90% of active donors have mailing address Donors with address / active donors
Gift coding accuracy Gifts regularly miscoded (fund, campaign, appeal); staff report reconciliation issues Under 1% of gifts require recoding after entry Gifts recoded in last 12 months / total gifts
Lapsed donor accuracy Donors flagged as lapsed who are actually active (duplicate record issue) Under 1% false lapsed (verified through deduplication) After deduplication: count donors whose merged record changes status from lapsed to active

Annual Cleaning Calendar

Month Action Purpose
January Year-end giving reconciliation; verify all December gifts correctly recorded; run deduplication Clean start for new fiscal year (if calendar year); accurate year-end totals for annual report
March-April NCOA processing before spring appeal; email verification Clean contact data for spring campaign
June Mid-year data audit; gift coding review; duplicate scan Catch issues before they accumulate; mid-year budget check
August-September Pre-year-end appeal preparation; NCOA; email verification; deceased suppression; lapsed donor identification and reactivation list Clean data for the most important fundraising season
October Verify employer/occupation for donors above reporting threshold; update matching gift records Compliance preparation for year-end reporting
November-December Monitor bounce rates during year-end appeal; flag new duplicates from online giving surge Real-time data quality during highest-volume giving period

Extract emails

Explore tools

Verify emails

Check address validity before using your list.

ZeroBounce

Email Verification

Verifies email lists and provides tools for monitoring deliverability.

Useful when list cleaning and sender health belong in one workflow.

Explore ZeroBounce (opens in a new tab)