From Spreadsheet to Fundraising System: A Practical Migration Guide
Last updated: July 2026
Spreadsheets are often the first donor database. They are familiar, flexible, and easy to start. The trouble appears when different people maintain different versions, conversations live in inboxes, and nobody is sure which follow-up is current.
A careful move to FUNDesk does not require a complicated data project. It does require clear decisions about what each row and column means.
1. Gather the source files
Collect the files that contain donors, contacts, gifts, potential gifts, grant applications, tasks, and notes. Name an owner for each source and identify which file should win when values conflict.
Keep an untouched copy of every source file before cleaning begins.
2. Separate people, organizations, and gifts
A common spreadsheet mixes several kinds of information into one row. Split it into clear groups:
- Donors & Contacts: people, households, companies, and foundations.
- Potential Gifts: a request or possible contribution being discussed.
- Grant Applications: a request submitted to a grantmaker.
- Gifts: money already received.
- Tasks and Notes: follow-ups and relationship history.
Do not treat a committed gift as money received. Keeping those events separate makes reports and follow-ups more reliable.
3. Clean the important fields
Before import:
- use one column for each value;
- standardize dates and email addresses;
- remove obvious duplicate rows;
- keep source IDs when they can help with matching;
- decide how households and organizations relate to people;
- preserve useful notes instead of squeezing them into a status field.
Do not delete uncertain data simply to make the sheet look tidy. Mark it for review.
4. Map progress to five stages
Older files often contain many status names. Map each active potential gift to the closest plain stage:
| Meaning | FUNDesk stage |
|---|---|
| Recently identified or not yet contacted | New |
| Relationship-building is underway | In Conversation |
| A specific request has been made | Asked |
| The donor has agreed | Committed |
| The money has arrived | Gift Received |
Keep declined or closed items as outcomes. Keep acknowledgments, stewardship, and renewal work as tasks and dates.
5. Import a small sample first
Start with enough records to reveal problems, but not the entire database. Check:
- names and contact details;
- donor-to-contact relationships;
- gift amounts and dates;
- potential-gift stages;
- grant deadlines;
- notes and record ownership.
Fix the mapping, then import the full set.
6. Reconcile totals and review the work
Compare record counts and gift totals between the source files and FUNDesk. Review a sample of long-standing donors with the staff members who know them. Document anything intentionally excluded.
7. Give the team a simple first week
Do not begin with every report and setting. Teach the daily loop:
- Open Home.
- Review priorities and overdue follow-ups.
- Update the donor or potential gift after a conversation.
- Record a gift only when it is received.
- Use Ask FUNDesk when context needs to be gathered quickly.
A successful migration is not just a clean import. It is a system the team can keep current without thinking like database administrators.
Visit FUNDesk when you are ready to bring the work together.