Choosing a Nonprofit CRM

What a nonprofit CRM actually is

CRM stands for constituent relationship management, or customer relationship management in the business world. For a nonprofit, it is the system that holds what you know about the people who support you: donors, volunteers, members, partners, funders and program contacts, along with the history of every gift, conversation and email.

Many people call it a donor database, and for fundraising that is its core job. But a good CRM does more than store names and amounts. It shows you who gave last year and has not given this year, which volunteers are also donors and which supporters asked not to be phoned.

The right system saves hours every week and helps you keep supporters for longer. The wrong one becomes an expensive spreadsheet nobody trusts.

“A CRM is only as good as the habits around it. The software is the easy part.”

Signs you have outgrown spreadsheets

• Donor information lives in several spreadsheets, inboxes and someone’s memory.
• Issuing tax receipts at year end takes days of manual work.
• Nobody can quickly say how many donors gave this year compared with last year.
• Thank-you letters go out late, or not at all, because nobody is sure who gave what.
• Volunteers, members and donors are tracked in separate places, so you cannot see the whole relationship.
• When a staff member leaves, their contacts and history leave with them.

If three or more of those sound familiar, a CRM is likely worth the investment. If only one does, a better-organized spreadsheet may carry you a little longer, and that is a perfectly reasonable choice.

What a good nonprofit CRM does

Not every organization needs every feature. A volunteer-heavy organization may care more about scheduling than major gift tracking, and a small charity may only need clean records, accurate receipts and a few reliable reports.

Canadian receipting: test it, do not assume it

If you are a registered charity, receipting is where a CRM earns or loses its place. The Canada Revenue Agency sets out what an official donation receipt must include for a cash gift, including:

• a statement that it is an official receipt for income tax purposes
• the charity’s name and address as on file with the CRA, and its registration number
• a unique serial number and the location where the receipt was issued
• the date or year the gift was received and the date the receipt was issued
• the donor’s full name, including middle initial, and address
• the amount of the gift, the amount and description of any advantage and the eligible amount
• the signature of an authorized individual, and the name and website address of the CRA

The CRA also says the information on a receipt must be readable and not easily altered. Tools built mainly for other countries may not handle these requirements out of the box. During demos, ask each vendor to produce a real Canadian receipt from test data, including a gift with an advantage, such as a gala ticket that includes dinner.

Privacy and consent

Your CRM will hold personal information, so privacy belongs in the decision from the start. The Office of the Privacy Commissioner of Canada says non-profit organizations are usually not subject to PIPEDA because they do not typically engage in commercial activities. It is also clear that selling, bartering or leasing a donor or membership list is commercial activity, and it recommends following PIPEDA’s fair information principles as a best practice either way.

Provincial privacy laws can also apply depending on where you operate and what you do, so check your province’s rules or get advice.

Email rules matter too. Under the federal anti-spam regulations, the main rules for commercial electronic messages do not apply to a message sent by or on behalf of a registered charity whose primary purpose is raising funds for the charity. Nonprofits that are not registered charities do not get that exemption, and plenty of messages are not fundraising messages at all. Choose a CRM that records consent and unsubscribe preferences clearly, whatever your status.

Start with your needs, not the features

The most common mistake is starting with vendor websites. Start with how your organization actually works.

Write the answers down in a short requirements document, one or two pages long. It keeps demos focused and stops the shiniest feature from winning the decision.

Who should be involved

A CRM touches almost every part of a small organization, so the decision should not sit with one person. Bring in:

• The executive director, who owns the budget and the final call.
• Your fundraising lead, who will live in the system every day.
• Whoever handles finance, for receipts, reconciliation and year end.
• Program or volunteer coordinators, if their contacts will be in the system.
• Someone comfortable with technology, staff, volunteer or adviser, to test integrations and data import.
• The board, at the right moment, to approve the budget and understand the risks.

Keep the working group small, three to five people, but make sure every group of daily users has a voice. People support what they help choose.

A sample requirements list

Here is a made-up example for a small registered charity with one fundraiser, a part-time bookkeeper and a few hundred donors.

Must-haves:

• Accurate CRA receipts, one at a time and in year-end batches
• Monthly and one-time gifts, linked to campaigns
• Gifts from our online donation form flowing in automatically
• A donor retention report in a few clicks
• Consent and communication preferences on every record
• Full data export at any time

Nice-to-haves:

• Event registration and ticketing
• Volunteer shifts and hours
• Grant deadlines and reporting reminders
• Peer-to-peer fundraising pages

A list this short is enough to rule out unsuitable systems quickly and to keep every demo honest.

Types of systems

There is no single best category. A five-person charity and a regional organization with a major gifts team need very different things, and that is exactly why the requirements come first.

If your organization is very small

If you have one part-time staff member and a few dozen donors, a full CRM may be more than you need today. That is fine. What matters is that your data is consistent and complete, so it can move into a proper system when you are ready.

• Keep one master list, not several, with one row per person.
• Use the same columns and formats every time: names, addresses, gift dates, amounts and receipt numbers.
• Record consent and communication preferences from the start.
• Use the donor tools in your online giving platform, if it has them, and export regularly.
• Set a trigger for moving to a CRM, such as a certain number of donors or the first time year-end receipting takes more than a day.

Clean, consistent records today will make your future migration far cheaper and far less painful.

Look at the total cost, not just the subscription

The monthly subscription is only part of the cost. Before you compare prices, list everything:

• subscription or licence fees, and how they change as your contact list grows
• setup and configuration
• data cleanup and migration
• integrations with your donation forms, email and accounting
• training for staff and volunteers
• ongoing administration time
• payment processing fees, if the CRM handles online giving

Some vendors offer nonprofit pricing or discounts, so ask, and ask how pricing changes at renewal. The cheapest system is the one your team actually uses well. A low-cost tool nobody trusts can cost more in lost donors and wasted time than a pricier one that works.

Integrations that matter

A CRM sits at the centre of your other tools. Check how it connects with:

• Online donations. Gifts should flow into the CRM automatically, without retyping.
• Email marketing. Lists and unsubscribes should stay in sync both ways.
• Accounting. Gift totals should reconcile with your books every month.
• Your website. Sign-up, volunteer and contact forms should land in the CRM.
• Your office tools. Calendars, email and documents, such as those covered in our guide to Google Workspace for nonprofits.

Ask for a live demonstration of each integration you need, not a slide saying it exists.

Volunteers, members and program participants

Many organizations want one system for everyone. That can work well for donors, volunteers and members, because the same people often play several roles and you want to see the whole relationship.

Program participant information is different. It can include sensitive personal details, and the people who need to see it are usually not the people who need donor information. Think carefully before putting it in your fundraising CRM. A separate system, or strict access permissions within one system, may be the better choice.

For members, check whether the CRM handles renewals, membership categories and voting eligibility if your bylaws depend on them. For volunteers, look at shifts, hours and screening records, and who can see each of them.

Whatever you decide, write down who can see what, and why. It is far easier to set access rules at the start than to untangle them later.

How to shortlist and choose

1. Write your requirements. Keep it to a page or two, with must-haves first.
2. Build a long list. Ask similar organizations what they use and what they would change.
3. Shortlist three vendors. Drop any that fail a must-have, such as Canadian receipting.
4. Run scripted demos. Ask each vendor to show your scenarios, using your kind of data.
5. Check references. Speak to at least two Canadian organizations of a similar size.
6. Trial if you can. Test real tasks with the people who will use the system every day.
7. Decide and document why. Record the reasons, costs and risks for your board.

Involve the people who will use the system daily at every step. A decision made by one enthusiast tends to become a system used by one enthusiast.

Scenarios to test in every demo

• Enter a new donor, record a gift and issue a receipt.
• Record a monthly donor and show the year-end receipt.
• Record a gala ticket with an advantage and show the eligible amount on the receipt.
• Merge two duplicate records without losing history.
• Pull a list of donors who gave last year but not this year.
• Record that a donor has unsubscribed from email, and show where that is respected.
• Export all your data to a spreadsheet.

If a vendor cannot show a scenario live, treat it as a gap until proven otherwise.

Ask the same scenarios of every vendor, in the same order, and score each one on a simple scale. It turns a series of polished sales presentations into a fair comparison your board can follow.

Questions to ask vendors

Data export is the question people forget. Make sure you can leave with all your records, gifts and notes if the relationship ends.

Cleaning and moving your data

Moving data is where most of the work hides. Treat it as a project of its own.

• Decide what to bring across. Gift history usually matters; old event sign-ups may not.
• Remove duplicates and fix obvious errors before migration, not after.
• Agree standard formats for names, addresses, phone numbers and gift types.
• Run a test import with a sample, check it carefully, then import everything.
• Reconcile totals: gift totals by year in the new system should match your records.

Rolling it out

A calm rollout beats a big-bang launch. A simple plan:

• Name a champion who owns the system and its data rules.
• Configure only what you need for launch, and add features later.
• Train people on their actual tasks, not every menu.
• Run the old and new systems side by side briefly, if you can, and compare results.
• Choose a go-live date away from your busiest fundraising season.

For many Canadian charities, the weeks around year end are a poor time to switch, because receipting and holiday appeals already stretch everyone. Pick a quieter period and give people time to settle in.

Getting people to use it

The best CRM fails if staff keep their own spreadsheets on the side. Adoption is a leadership job, not a software feature.

• Make the CRM the only place donor information lives.
• Keep data entry rules short and written down.
• Build the reports people actually want, so the system gives something back.
• Celebrate quick wins, such as faster thank-yous or an easier year end.
• Check in after a month and fix whatever frustrates people.

Your first year with a new CRM

A new system settles in over months, not days. A simple rhythm for the first year:

• First month. Focus on the basics: entering gifts, issuing receipts and sending thank-yous from the CRM.
• Third month. Build the handful of reports your team and board will use regularly.
• Sixth month. Review adoption and data quality, and fix whatever is frustrating people.
• Before year end. Run a test of year-end receipting well ahead of the rush.
• Twelfth month. Do a full cleanup and decide which extra features, if any, to add next.

Write the dates into your calendar on launch day, so the reviews actually happen.

Keeping your data clean

Data decays. People move, change email addresses and pass away. A few habits keep your CRM trustworthy:

• Set required fields and standard formats.
• Assign clear permissions, so people only see and change what they need.
• Review duplicates and bounced emails every month.
• Record how and when consent was given.
• Do a deeper cleanup once a year, before your biggest appeal.

Write these habits into a one-page data policy and review it when you onboard new staff or volunteers.

Reports worth building

A CRM should answer your most important questions in minutes. Start with:

• donor retention: how many of last year’s donors gave again this year
• new, lapsed and reactivated donors
• revenue by campaign, appeal and channel
• monthly donors and how long they stay
• average gift and number of gifts per donor

These numbers drive real decisions. Our guides to donor retention and building a monthly giving program show what to do with them, and a clear case for support helps you act on what the reports reveal.

Supporting relationship fundraising

If your fundraising includes major donors, foundations or corporate partners, your CRM should help you manage relationships, not just record transactions.

• Notes from meetings and calls, visible to the people who need them
• Tasks and reminders for follow-ups, so nothing slips
• Stages for each relationship, from first conversation to ask to thank-you
• Links between people and organizations, such as a donor who sits on a foundation board

These features matter more as your fundraising grows. Our guide to building a fund development strategy explains how relationship fundraising fits into the bigger plan.

Security basics

• Turn on two-factor authentication for every user.
• Give each person their own login. Never share accounts.
• Remove access the day someone leaves.
• Export a backup of your data on a regular schedule.
• Limit who can export full donor lists.

Your donors trust you with their information. Protecting it is part of earning that trust.

Review who has access every few months, especially volunteers and former contractors.

How to tell if the CRM is working

Six months after launch, check whether the system is doing what you bought it for. Useful signs:

• Year-end receipting takes noticeably less time than before.
• Thank-you messages go out faster after each gift.
• You can answer basic questions, such as donor retention, in minutes.
• Staff have stopped keeping side spreadsheets.
• Duplicate records and bounced emails are falling, not rising.

If the answers are disappointing, the cause is usually training, data rules or configuration, not the software itself. Fix those before you consider switching again.

Making the case to your board

A CRM is an investment, and boards rightly want to know what it will deliver. Keep the case short and concrete:

• The problem. Where donor information lives today and what that costs in time, errors and missed gifts.
• The options. Two or three systems that meet your must-haves, with total costs.
• The benefits. Faster receipting, better retention reporting, less risk when staff change.
• The plan. Timeline, owner, training and data cleanup.
• The risks. What could go wrong and how you will manage it.

Boards respond well to plain numbers, such as the hours spent on year-end receipts today. Measure a few before you start, so you can show the difference later.

Common mistakes

• Choosing on price alone.
• Letting one enthusiast pick the system without input from daily users.
• Migrating messy data and hoping to clean it later.
• Skipping receipting tests before year end.
• Over-customizing on day one.
• No owner for data quality after launch.

Each of these is avoidable with a written plan, a named owner and honest testing before you sign.

Getting help

Choosing and implementing a CRM is a significant project for a small team. For Good Consultants provides technology support for nonprofits, including CRMs and donor databases, online donations, websites and email, and can help you define requirements, compare options and plan the move.

Whatever you choose, start with your needs, test with real scenarios and plan for the people side. The software really is the easy part.

Frequently asked questions

What is a nonprofit CRM?

A system that holds information about your donors, volunteers, members and other supporters, with their gifts and interactions, so you can manage relationships, receipts and reporting in one place.

What is the difference between a CRM and a donor database?

A donor database focuses on donors and gifts. A CRM usually covers more relationships, such as volunteers, members and partners. Many nonprofit systems do both.

Does a Canadian charity need special receipting features?

Yes. The CRA sets out what an official donation receipt must include, from the registration number to the eligible amount. Test that any CRM can produce compliant Canadian receipts.

Does PIPEDA apply to nonprofits?

The Office of the Privacy Commissioner says non-profits are usually not subject to PIPEDA because they do not typically engage in commercial activities, but selling, bartering or leasing donor lists is commercial activity. It recommends following fair information principles anyway.

Do charities need consent to send fundraising emails?

The federal anti-spam regulations exempt messages sent by or for a registered charity whose primary purpose is raising funds for the charity from the main rules. Other messages and other organizations may not be covered, so get advice for your situation.

How much does a nonprofit CRM cost?

It varies widely. Look beyond the subscription to setup, data migration, integrations, training and staff time, and ask how pricing changes at renewal.

How long does it take to implement a CRM?

It depends on your data and needs. Clean data and few integrations make it faster; messy data and many connections take longer. Avoid going live in your busiest fundraising season.

Can we switch CRMs later?

Yes, if you can export your data. Before signing, confirm you can export all records, gifts and notes in standard formats at any time.