Salesforce is a widely used CRM in the nonprofit sector. It's also one of the most frequently underused, misconfigured, and quietly resented.
Not because it's a bad product. Because nonprofits often get into Salesforce without enough support, then spend years working around problems that were baked in at the start.
Here are the mistakes that come up most often, and what to do about them.
Mistake 1: Importing dirty data at setup
The most costly Salesforce mistake happens before the system is even live. When nonprofits migrate to Salesforce, they often import their existing data without cleaning it first.
That means every duplicate contact from the old system becomes two records in Salesforce. Inconsistently formatted addresses, misspelled names, blank fields that should have data: all of it comes along for the ride.
Salesforce's deduplication tools can help after the fact, but they're not a substitute for clean source data. The cost of cleaning data before import is a fraction of the cost of cleaning it after, when it's spread across thousands of records with relationships, activity logs, and donation histories attached.
Before any migration, run a full audit of your existing data. Deduplicate contacts, standardize name and address formatting, and fill in critical missing fields. Then import.
Mistake 2: Too many custom fields, too soon
Salesforce lets you create custom fields for almost anything. Nonprofits often take this as an invitation to recreate every column from every spreadsheet they've ever maintained.
The result is a contact record with 40 fields, most of which nobody fills in, and staff who feel overwhelmed every time they open the system.
Custom fields should earn their place. Before creating one, ask: who will fill this in, when, and what decision will it inform? If you can't answer all three, don't create the field yet.
Start with the minimum set of fields you actually need for your most important workflows: gift processing, program enrollment, grant reporting. Add more as specific needs emerge, not in anticipation of hypothetical future needs.
Mistake 3: No data entry standards
Salesforce is only as consistent as the people entering data into it. If your team doesn't have written standards for how to enter names, addresses, gift types, and program codes, everyone will do it slightly differently, and your reports will reflect that inconsistency.
Common symptoms: running a report by state and getting separate rows for "FL," "Florida," and "fl." Searching for a donor and finding them listed as three separate contacts because different staff entered them at different times. Gift amounts that don't match your accounting software because staff are recording the gross amount in one place and the net in another.
The fix is simple but requires discipline: write down your entry standards, make them available to every staff member who touches Salesforce, and enforce them during onboarding.
Mistake 4: Letting the record owner field go stale
Salesforce assigns every contact and opportunity a record owner. In small nonprofits, this is often set during import and never updated. Staff turn over, roles change, and three years later half your major donor records are owned by someone who left the organization.
This matters for reports, for task assignment, and for anything that uses ownership as a filter. Set a reminder to review record ownership quarterly, especially when staff transition.
Mistake 5: Ignoring the Activity log
Salesforce's activity tracking (calls, emails, meetings, tasks) is one of the most valuable things it does for relationship management. It's also one of the most consistently ignored features in small nonprofits.
When staff don't log interactions, the system has no memory of the relationship. A new development director who joins can't see that a major donor had a difficult conversation two years ago, or that a prospect was contacted six times with no response. That institutional knowledge lives in someone's head or not at all.
Logging doesn't have to be exhaustive. Even a brief note on significant interactions is enormously valuable over time. Build it into your workflow standards and hold the team to it.
Mistake 6: Not using reports and dashboards
The point of having a CRM is to use it for decisions. If your team only opens Salesforce to look up a contact or log a gift, you're using it as an expensive address book.
Salesforce's native reporting tools are powerful. You can build a lapsed donor report in an afternoon. You can track gift revenue by campaign, by fund, by month. You can see which program participants have donated and which haven't. You can pull the grant report data you need without manually compiling a spreadsheet.
If nobody on your team knows how to build a Salesforce report, that's the highest-value skill to develop or hire for.
The common thread
Most Salesforce problems in small nonprofits trace back to the same root cause: the system was set up quickly, without much planning, and nobody was ever formally responsible for maintaining it.
The good news is that these mistakes are fixable. It takes time, but it's systematic work. A data audit, a cleanup project, a set of entry standards, and a named data owner can turn a system people work around into one they trust.
If you're not sure where your Salesforce data stands, our free Nonprofit Data Health Checklist is a practical starting point.
If you work through it and want to talk through what you find, I'm happy to do a free 30-minute discovery call.
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.