What belongs in your donor database

A donor database should hold four things for every donor: who they are, how to reach them, every gift and pledge they have made, and a record of what was said to them along the way. Most spreadsheets only manage the first two. A donor database for a political campaign or a nonprofit is the record that keeps donors, pledges, donations, and follow-ups in one place instead of split across a spreadsheet, an inbox, and a volunteer’s notebook.

This post covers what belongs in that record, where a campaign’s fields differ from a nonprofit’s, and how to keep the database accurate once your list outgrows a spreadsheet.

Key Takeaways
– Every donor record needs four parts: identity and contact info, giving history, open pledges with dates, and a log of conversations.
– A pledge without a follow-up date is a maybe, not a commitment, so the date belongs in the record as much as the amount.
– Campaigns should capture occupation and employer for donors whose cumulative gifts may require itemized reporting; confirm the threshold with the FEC or your state’s campaign finance office.
– Nonprofits need to track which gifts have been acknowledged, since written acknowledgment is required for larger contributions under IRS rules.
– Smart Groups can surface missing fields, outstanding pledges, and unacknowledged gifts automatically, instead of relying on someone to notice.

What a donor database actually holds

A donor database is a record of every donor, their giving history, and every conversation connected to it, built so a finance director or development director can act on it without reconstructing the story from memory. It is different from a mailing list, which only needs a name and an address, and different from a spreadsheet of gifts, which rarely tracks what happened between gifts. The database’s job is to answer one question fast: where does this relationship stand right now?

The core record: identity, contact info, and giving history

Every donor needs a profile with their name, mailing address, email, and phone number, plus how they prefer to be reached. Next to that sits their giving history: every donation and its date, amount, and method, whether it came through a donation page, a check, or a call. FundHero’s Donor Profiles hold this record, with Automatic Donation Tracking adding the donor account and the gift record the moment money comes in, so nobody has to type it in twice.

Two fields get skipped more often than they should: how the donor first gave or got involved, and which of your donation pages or appeals brought them in. Activity Tags record that source on each gift, so months later you can still tell a board member or a candidate which appeal, event, or volunteer brought that donor in.

Pledges: the field a spreadsheet always loses

A pledge is a promise to give a specific amount by a specific date, and it belongs in the database with both of those details, not just a note that someone “said they’d give.” Without a date, a pledge turns into a line nobody follows up on. Donor Profiles holds the pledge with the amount and the date side by side, and a Smart Group can list every pledge that has passed its date unpaid, so the follow-up is a list to work through rather than something a volunteer has to remember.

Campaign donor databases: fields the FEC cares about

A political campaign’s database needs one more layer: the information federal and state reporting rules require once a donor’s contributions pass a certain threshold, typically the donor’s occupation and employer alongside the standard contact fields. Those thresholds and the exact reporting rules differ by office and by state, so do not treat any number here as settled; confirm the current recordkeeping requirements with the FEC or your state’s campaign finance office before you file.

What a database can do regardless of the exact threshold is make the habit automatic: capture occupation and employer at the time of the gift, not months later when a treasurer is reconstructing a filing. FundHero’s premade reports pull the contributions for a filing period so that work is a report, not a research project.

Nonprofit donor databases: fields for stewardship and tax receipts

A nonprofit’s database carries a different extra layer: whether each gift has been acknowledged, since the IRS requires a written acknowledgment for the donor to claim a tax deduction on larger contributions. That acknowledgment status belongs in the record next to the gift itself, not in a separate thank-you tracking sheet. A Smart Group built on Activity Tags and Contact History can list every gift still missing one, so a development director works it as a weekly list instead of trusting that someone remembered.

Nonprofits also benefit from recency and frequency fields: when a donor last gave, how often, and whether they have lapsed. That is the same data a database already holds; the only extra step is grouping by it, which is what Contact Groups and Smart Groups are for.

Contact history: the conversations around the gift

A donation is one moment. The calls, emails, and text messages around it are what turn a one-time donor into a repeat one, and they belong in the same record as the gift, not scattered across a volunteer’s phone and someone’s inbox. Contact History saves every call, email, text message, pledge, and contribution to the donor’s timeline, so a finance director can see the whole relationship, not just the deposits.

This matters most at call time. A caller working from a list that shows the last conversation, the last gift, and any open pledge can pick up where the relationship left off instead of starting cold.

Keeping the database clean as it grows

A donor database degrades the same way every spreadsheet does: duplicate entries from imports, donors with no email, pledges nobody closed out. Three habits keep it usable. Import contact lists and past contributions in one pass rather than copying rows by hand, so duplicates get caught once instead of repeated. Give every team member their own login, under Teams, so you can see which conversations happened and which still need to. And let a Smart Group flag the gaps, such as donors missing a phone number or pledges open past their date, instead of auditing the whole list by hand.

Frequently asked questions

What is a donor database?
A donor database is a record of every donor’s contact information, giving history, pledges, and the conversations connected to each gift, kept in one place so a campaign or nonprofit can act on it without searching a spreadsheet, an inbox, and a notebook separately.

What is the difference between a donor database and a spreadsheet?
A spreadsheet can hold names and gift amounts, but it rarely tracks pledge dates, acknowledgment status, or the history of calls and emails tied to each donor. A donor database connects all of that to one profile, and tools like Smart Groups can act on it automatically.

Do I need a donor database for a small campaign or a small nonprofit?
Yes, even with twenty donors. The habits that keep a database clean, logging pledges with dates and acknowledging gifts on time, matter more when a volunteer team is small, because there is no one else to catch what slips through.

What donor information do campaigns need for FEC reporting?
Campaigns typically need a donor’s name, address, occupation, and employer once their cumulative contributions reach a reporting threshold. The exact threshold and requirements differ by office and change over time, so confirm them with the FEC or your state’s campaign finance office before you file.

How fast should a nonprofit acknowledge a donation?
Quickly, and within the timeframe the IRS requires for the donor to claim a deduction on larger gifts. Track acknowledgment status in the same record as the gift so a Smart Group can flag any that are still open.

How do I move from a spreadsheet to a donor database?
Import your existing contacts and past contributions in one pass, confirm the pledge dates and acknowledgment status carried over correctly, then start logging new calls and emails directly in the donor’s profile instead of a separate notebook.

The record you can act on

A donor database earns its place when it answers four questions for any donor on command: who they are, what they have given, what they have pledged, and what was last said to them. Build the habit of logging pledge dates and acknowledgment status as part of the gift, not as a separate task, and the database does the reminding instead of a person. If your current donor database is three spreadsheet tabs and a notebook, start a free trial and import your list; no payment information is required to see what belongs where.