Why your team is still using spreadsheets after moving to Salesforce
You made the leap and invested in Salesforce. That’s a big step.
Then a few months in, you notice you’re back where you started. The development team still tracks grants in a spreadsheet. Communications keeps its own list of event RSVPs. Your donor data is in Salesforce, but volunteer hours are still in a Google Sheet.
I call this the spreadsheet graveyard. It’s where important data goes to die, cut off from the system you paid for.
It usually happens for understandable reasons. The spreadsheet was there first, people know how to use it, and nobody built a home for that information when Salesforce went in. Every list that lives outside your main system still costs you something, though.
What you lose when data lives outside Salesforce
When your data is split across spreadsheets, you can’t:
- See the full picture of a supporter’s engagement, from their first volunteer shift to their latest major gift.
- Automate your follow-ups, because someone has to copy data between systems by hand first.
- Pull together reports that show the real impact of your work.
Here’s what that looks like in practice. Say a donor sends a generous gift. You send a thank-you note and add them to your mailing list. Simple enough. Now imagine you didn’t know that same person has also volunteered more than 100 hours with your organization.
That was the situation at a human services organization I worked with recently. Their donor information was in Salesforce and their volunteer data was in separate spreadsheets, so they were working in two different worlds. We merged the two into one place in Salesforce.
Once fundraisers could see both the money and the time a supporter had given, they could:
- Offer stewardship that recognized every kind of gift.
- Spot passionate supporters who were ready to get more involved.
- Build stronger relationships that pay off over the long run.
You end up seeing your supporters as whole people, with their full history in front of you.
What connected data makes possible
Once everything lives in one place, the tools built into Salesforce get a lot more useful, including the new AI features.
Picture your major gifts officer with a donor meeting in an hour. They need the whole history: every donation, every event and every conversation. Digging through records could take hours they don’t have.
With AI in Salesforce, they can click a button on the donor’s record and get a short summary of the relationship. The AI reads the full record, including past gifts, volunteer activity, event attendance and notes. In seconds it writes something like: “This donor has given every year for seven years, with gifts growing each year and a major gift in Q3 last year. Their main interest is youth programs, and they recently attended the annual gala.” It can also suggest next steps, like a first draft of a follow-up on their latest gift or an invitation to a private tour.
That summary is only as good as the record behind it. If the volunteer hours are still in a Google Sheet, the AI won’t know about them, and neither will your gift officer.
How to bring your spreadsheets into Salesforce
- Find every spreadsheet. Ask each team what they track outside Salesforce. Grants, event RSVPs and volunteer hours are the usual ones, and there are often a few surprises.
- Ask why it lives there. Usually Salesforce didn’t have a place for that information, or the process in Salesforce was clunkier than the sheet. That tells you what to build or fix.
- Start with the one that hurts most. Pick the list that causes the most double entry or the most missed connections. If your donors and volunteers are split, that’s a good place to start.
- Match records before you import. Check the names in the spreadsheet against your existing contacts so you don’t create duplicates. A clean import is worth the extra day.
- Retire the spreadsheet. Once the data is in Salesforce, archive the sheet or make it read-only, so nobody keeps updating both.
- Show people what they get. Build one view or report that uses the new data, like a supporter’s full history on their record, so the team sees why the move was worth it.
For leaders: ask what’s still living outside Salesforce
You’ve already made the investment. The return comes when your team works from one system instead of a handful of spreadsheets. A few questions to bring to your next staff meeting:
- Which spreadsheets do we still update every week, and who owns them?
- Can a fundraiser see a supporter’s volunteer history before a donor call?
- How long does it take us to pull a report on our impact, and how many files does it touch?
If the answers make you wince, start with one spreadsheet and bring that data home. Each one you retire makes the next report and the next donor conversation a bit easier.