A nonprofit should move from a spreadsheet to a CRM when the spreadsheet starts costing more than it saves: duplicate records, no history, reports built by hand, and knowledge that leaves with a staff member. Salesforce is one good answer, but it is not the only one. If one person updates one sheet and the numbers still answer your board's questions, you probably don't need to move yet.
This post is for small and mid-size nonprofits deciding whether a nonprofit spreadsheet to CRM move is worth doing, and how to do it without losing years of history. We'll cover the signs, the non-signs, what the work involves, the mistakes we see most, and the options besides Salesforce.
Signs the spreadsheet has stopped working
One of these on its own is an annoyance. Three or four together usually mean it's time.
- Duplicates keep appearing. The same donor, family or partner shows up in three rows with slightly different spellings. Nobody is sure which row is right.
- There is no history. The sheet shows today's value, not what happened. You can't see when a donor last gave, who spoke to them, or what changed in a client's file.
- Reports are built by hand. Every board meeting or grant report starts with copying, filtering and pivoting. Two people building the same report get two different numbers.
- Staff turnover hurts. When someone leaves, their tabs, color codes and private rules leave with them.
- Data lives in several places. Donations in a payment tool, events in another sheet, email lists in a mailing tool, program notes in documents. Nobody sees the whole relationship.
- Several people edit at once. Overwritten cells, broken formulas and "which version is current?" threads.
- You can't control who sees what. A sheet is usually shared whole. If it holds sensitive information about the people you serve, that is a risk, not just an inconvenience.
Signs it has not stopped working
Plenty of nonprofits are fine on a spreadsheet, and moving too early creates its own cost.
- One or two people maintain the data, and they have written down how.
- You have a few hundred records, not thousands, and little overlap between lists.
- Your reporting needs are simple: a count, a total, a yearly list.
- Nothing you track has to be linked to anything else (for example, a donor to a grant to a program).
- You can answer a funder's question in minutes, not days.
If this is you, tidy the sheet first: one header row, one row per person or organization, consistent dropdown values, a date column, and a "last updated by" column. That alone buys another year or two and makes any later move much easier.
Why Salesforce, and when it fits
Salesforce is a flexible platform, which is its strength and its risk. It fits when you track more than gifts: relationships between people and organizations, programs, grants, volunteers, case notes or services, with reports and permissions to match.
For nonprofits, Salesforce's current nonprofit product is Agentforce Nonprofit (formerly Nonprofit Cloud). The older Nonprofit Success Pack (NPSP) is still supported, but it no longer gets new features, and Salesforce hasn't announced an end date (Salesforce Ben, checked November 2026). The same source says eligible nonprofits can request 10 donated Agentforce Nonprofit or Sales and Service Cloud licenses through Power of Us. Donated licenses are not the whole cost, so read Is Salesforce free for nonprofits? before you plan a budget.
It fits less well when you need only a donor list and receipts. For that, a lighter donor tool is often the better buy. We compare them in nonprofit CRM software compared.
What moving involves
A good move is mostly preparation. The import itself is the short part.
1. Clean up
Decide what you are keeping. Remove obvious duplicates, fix inconsistent values (one spelling per program, one format per date), and archive rows nobody has touched in years. Do this in the spreadsheet, where it is cheap.
2. Decide the structure
Work out what the CRM needs to hold and how the pieces connect. Typically that means people, organizations, gifts or grants, programs and activities. This step is where history is protected: if your sheet has one row per donation, you want those to become separate gift records linked to a person, not extra columns on one record.
3. Map the columns
Write down, column by column, where each field goes in the new system. Flag columns that don't fit anywhere and decide whether they are needed. Keep the original file, untouched, as your backup.
4. Import in stages
Start with a small test batch and check it by eye. Salesforce's standard tools are the Data Import Wizard and Data Loader. According to Salesforce Ben (checked November 2026), the Wizard handles up to 50,000 records and supports a limited set of objects (it does not support Opportunities, for example), while Data Loader covers all standard and custom objects. Both can match on a key such as email or an ID to avoid creating duplicates. Your tool may differ, so confirm current limits in Salesforce's documentation before you plan.
5. Check the results
Compare counts and totals between the old file and the new system. Does the number of donors match? Does the sum of gifts for last year match your audited figure? Spot-check a handful of records against the source.
6. Train and switch over
Run a short training on the three or four things each role does daily. Then set a date after which the spreadsheet becomes read-only. If both stay editable, you will end up with two sources of truth.
Keeping your history
The fear we hear most is "we'll lose what we have." You won't, if you plan for it.
- Keep the original file. Store a read-only copy of every sheet you import.
- Import dates, not just totals. Gift dates, contact dates and start dates are what make a timeline.
- Bring old notes in as notes or activities rather than dropping them into one long text field.
- Keep a source ID. Add a column with the spreadsheet row number or an old ID, and import it into a field. It lets you trace any record back and fix mistakes later.
- Leave out what you can't use. Importing everything "just in case" is how clutter follows you in.
Duplicates: stop them before you load them
Once data is in Salesforce, duplicate rules help prevent new duplicates. Salesforce provides standard matching rules and lets you decide whether a duplicate rule warns the user or blocks the save (Trailhead, checked November 2026). Which fields the standard rules compare, and whether they are active, depend on the org, so check the Matching Rules page in Setup. Rules do not clean data that is already messy, which is why clean-up comes first.
Common mistakes
- Migrating dirty data. A CRM makes bad data faster to spread, not better. Clean first.
- Over-building. Teams add fifty fields and ten objects on day one. Start with what you use every week and add as real needs appear.
- No owner. Someone on staff has to own the data and decide what changes. Without that, the CRM drifts back into a spreadsheet with a login.
- Skipping training. If entering a gift takes longer than the old way, people go back to the old way.
- Running both systems. Pick a cut-over date and keep to it.
- Ignoring the people question. Who will maintain this in a year, when the consultant has gone?
What a first phase can look like
Without promising a specific scope, a sensible first phase is small and finishes quickly:
- Agree the two or three questions the CRM must answer (for example, "who gave last year?" and "which program does this person belong to?").
- Set up only the records needed to answer them: people, organizations, gifts or program participation.
- Load the cleaned data and check it.
- Build the few reports and dashboards you currently make by hand.
- Train the team and cut over.
Later phases can add grants, volunteers, case notes, email, online giving and integrations, once the foundation is in daily use.
Options besides Salesforce
Salesforce is not the right move for every organization. Depending on size and needs, you might consider:
- A donor-focused nonprofit CRM. Simpler to run, built for gifts and receipts, usually less customizable.
- An all-in-one tool for your main activity, such as an event, membership or volunteer platform, if that is most of what you do.
- A better spreadsheet or lightweight database. Shared tables with validation, forms and permissions can be enough for a while.
- A general CRM from another vendor. Fine for relationship tracking, though nonprofit-specific reporting may need work.
We lay out the trade-offs in our CRM comparison above. If a lighter tool does the job, we'll tell you.
Frequently asked questions
How big does a nonprofit need to be before moving to a CRM?
There is no fixed number. Size matters less than pain: duplicates, hand-built reports and lost history. Some very small nonprofits need a CRM early because of case notes or grants, and some larger ones run well on simple tools.
Will we lose our spreadsheet history if we move to Salesforce?
Not if you plan for it. Keep the original files, import dates and notes, and carry a source ID for each record. The history you can bring is the history that exists in your sheets, so the cleaner they are, the better.
Can we import our spreadsheet directly into Salesforce?
Often yes, after clean-up and mapping. Salesforce offers the Data Import Wizard and Data Loader, with different limits and object support, as described above. Complex sheets with many tabs usually need restructuring first.
How long does a move take?
It varies with data quality, the number of sources and how much you build. Clean data and a small first phase move faster than a large, undefined project.
Is Salesforce the best CRM for a small nonprofit?
Not always. It is powerful and flexible, but that comes with setup and upkeep. Many small nonprofits are better served by a lighter tool until their needs grow.
What if we are already on NPSP?
NPSP is still supported, with no new features and no announced end date. That is a separate question from leaving a spreadsheet. If it applies to you, decide that separately.
Not sure if it's time?
Book a short call and we'll look at your spreadsheet, your goals and your team, and tell you plainly whether to move, wait or choose a lighter tool.