The Nonprofit landscape
Decision rights in a nonprofit are spread wider than the org chart suggests. The executive director or CEO signs, but the board, and often its finance or audit committee, approves anything that looks like a multi-year commitment. The development director feels the pain most because gift processing, acknowledgments and donor reports land on that team. Finance controls the chart of accounts and the audit. Program leaders own the data funders ask for. Map all five groups before you write a proposal, and ask who on the board has opinions about technology, because someone always does.
- 01
Many prospects already run Salesforce through the Nonprofit Success Pack, the managed package that powered nonprofit Salesforce orgs for years.
Salesforce says NPSP will continue to be supported, and it recommends Nonprofit Cloud for new customers. The two use different data models: Nonprofit Cloud represents individuals as person accounts, groups them into households through party relationship groups, and records giving on gift commitment and gift transaction objects. Salesforce's help documentation also says person accounts are not supported with NPSP and cannot be switched off once enabled. Treat an NPSP customer's move as a fresh implementation with a data migration, never as a package upgrade.
- 02
Nonprofit Cloud now brings fundraising, programs, volunteer management and outcomes into one product, with Grantmaking for organizations that award funds.
You will still see help articles and Trailhead modules that use the name Agentforce Nonprofit, which the product carried briefly; the product is Nonprofit Cloud, and the AI layer is Agentforce for Nonprofit. Salesforce lists prebuilt agents for prospect research, donor engagement, donor self-service, volunteer shift coverage and program participant support.
- 03
Pricing comes up early, because most prospects have heard Salesforce gives software to charities.
Through the Power of Us program, Salesforce's pricing page says eligible nonprofits receive 10 Nonprofit Cloud Core licenses at no cost, with discounts on additional licenses. The Power of Us page asks US applicants for a 501(c)(3) or 501(c)(4) IRS determination letter. Free licenses do not make an implementation free. Say that plainly in the first meeting, and the budget conversation later is much easier.
Who buys, and how to open with them (5)
Executive Director or CEO
Cares about: Mission impact they can show the board, a stable donor base, staff who are not burned out by manual reporting, and not becoming the organization whose expensive system nobody uses.
“When the board asks how last year's programs changed outcomes for the people you serve, how long does it take your team to pull that answer together?”
- Which decisions would you make differently if you could see giving, program and volunteer data side by side?
- Who on the board will review this investment, and what did they say about the last technology project?
- If this went well, what would be different for your staff a year from now?
Chief Development Officer or Director of Development
Cares about: Donor retention, major gift pipeline, accurate gift processing and acknowledgments, and the ability to segment appeals without exporting everything to a spreadsheet first.
“Walk me through what happens between a check arriving in the mail and the donor getting a thank-you letter. Who touches it, and where does it wait?”
- How do your major gift officers manage their portfolios today, and how do you review their moves with them?
- Which tools hold online giving, events and peer-to-peer fundraising, and how do those gifts reach your donor database?
- How do you track pledges and recurring gifts that are promised but not yet paid?
- When a donor is also a volunteer or a board member's spouse, does your team see that before they call?
Director of Programs or Chief Program Officer
Cares about: Serving participants well, keeping caseworkers out of duplicate data entry, and reporting outcomes to funders in the form each funder requires.
“How many different funder reports do your program managers build each year, and how much of that is copying numbers between systems?”
- How do participants get referred, enrolled and tracked from intake to exit today?
- Which outcomes do funders ask you to measure, and where do the baseline and follow-up data live?
- Do caseworkers record sensitive notes, and who should be allowed to see them?
CFO, Finance Director or Controller
Cares about: Reconciling development's revenue numbers to the general ledger, tracking donor restrictions correctly, a clean audit and total cost of the system over several years.
“At month-end, how far apart are the development team's gift totals and your ledger, and how long does it take to close the gap?”
- How do restricted gifts and their designations get from the gift record to your accounting system?
- Which accounting system are you on, and who owns the integration or export today?
- What does the auditor ask for that is hardest to produce?
Database Manager, Operations Director or IT Lead
Cares about: Data quality, a system they can maintain with a small team, integrations that do not break every time a vendor changes something, and sensible access controls.
“If you were out for two weeks, which parts of the database would stop working or start drifting?”
- Are you on NPSP, another donor database or something homegrown, and how much custom code or how many packages have been added over the years?
- How many duplicate constituent records do you think exist right now, and how are they merged?
- Who supports the system today: staff, a volunteer, a partner or nobody?
The problems worth solving (6)
Development and finance never agree on what was raised
Gifts are entered in the donor database, then rekeyed or exported into accounting. Designations, refunds, soft credits and in-kind gifts are handled differently in each place. Every month someone reconciles the two by hand, and the year-end audit turns into a hunt for supporting detail. Ask finance how many hours that reconciliation takes and who does it.
Where Salesforce fits: Nonprofit Cloud fundraising records gift commitments, transactions and designations against a designation hierarchy. Accounting Subledger, which the pricing page lists in the Core edition, maps those records through accounting sets and produces debit and credit records formatted for export to the accounting system.
Gift processing and acknowledgments run behind
Checks, online gifts, event revenue and matching gifts arrive through different channels. Staff enter them one at a time, batch totals do not tie out, and thank-you letters go out late or with the wrong amount. The IRS requires a written acknowledgment before a donor can deduct a gift of $250 or more, so mistakes here create donor service problems quickly.
Where Salesforce fits: Gift Entry handles single gifts and gift batches built from templates, including batches imported from CSV files. Nonprofit Cloud generates acknowledgments and tax receipts from document templates, so letter content follows the gift record.
Major gift officers work from memory and spreadsheets
Relationship notes live in personal files and inboxes. Leadership cannot see which prospects are moving, which are stalled and which have not been contacted in months. When a gift officer leaves, their portfolio knowledge goes with them, and donors notice the silence.
Where Salesforce fits: Fundraising portfolios and the Donor Profile give each officer one view of assigned donors, a relationship timeline, wealth and giving information, and alerts. The Prospect Research and Donor Engagement agents can summarize capacity and prepare outreach context for a human to review.
Program outcomes are hard to prove
Program teams collect intake forms, attendance and assessments on paper, in spreadsheets or in a separate case management tool. Funders want outcome indicators, and each one wants a slightly different cut. Program staff spend reporting season rebuilding numbers instead of serving people.
Where Salesforce fits: Program Management tracks programs, benefits and disbursements, with Case Referral Intake, care plans and assessments available for case-managed services. Outcome Management links indicators, targets and results to the programs and benefits that drive them.
Volunteers are invisible to fundraisers
Volunteer coordinators schedule shifts in a separate tool or on a shared calendar. Development never sees that a mid-level donor has given forty hours this year, and the volunteer never hears from the organization about anything except the next shift. Coverage gaps get filled with last-minute phone calls.
Where Salesforce fits: Volunteer Management in Nonprofit Cloud sets up activities, roles, shifts and locations, records check-in and check-out, and keeps hours on the volunteer profile. An Experience Cloud portal lets volunteers find and register for shifts, and the Volunteer Capacity and Coverage Agent looks for unfilled shifts.
Grantmakers juggle applications by email
Foundations and nonprofits that award money often take applications through forms, email attachments and spreadsheets. Reviewers score in different places, and tracking budgets, disbursements and grantee reports takes a lot of manual follow-up.
Where Salesforce fits: Grantmaking in Nonprofit Cloud covers publishing funding opportunities, reviewing and awarding grants, and managing budgets and disbursements, with an Experience Cloud template for grantee portals. Salesforce sells it separately and includes it in the Max editions.
The numbers leaders run on (7)
Donor retention rate
Keeping a donor costs less than finding a new one, and boards watch this number closely. Gift transaction history by person account and household shows who gave last year and has not given this year.
Gift processing time (receipt to acknowledgment)
Late or wrong thank-you letters damage relationships and create work. Gift entry and acknowledgment dates in Nonprofit Cloud show where the queue backs up.
Major gift pipeline and portfolio coverage
Development leaders need to know how many qualified prospects each officer manages and how recently each was contacted. Portfolio assignments and activity history provide both.
Recurring giving revenue and lapse rate
Monthly donors are a predictable base, but failed payments and quiet cancellations erode it. Gift commitments and their unpaid or closed transactions show the trend.
Revenue reconciliation variance
The gap between development's totals and the ledger is a direct measure of how much manual work finance absorbs. Accounting Subledger output reconciled to the general ledger makes it visible each period.
Program outcome indicators against target
Funders and boards judge programs on outcomes, not activity. Outcome Management indicators with targets and results show progress by program and period.
Volunteer hours and shift fill rate
Volunteer capacity drives program delivery, and hours are often reported to funders or used as in-kind evidence. Shift records and check-in times provide the data.
Product fit (8)
Cross-sell sequence (5)
- NPSP Nonprofit Cloud"Our org has years of customizations nobody understands," or they want program, outcome or volunteer features that NPSP never had natively.
- Nonprofit Cloud fundraising Accounting SubledgerFinance rekeys gifts into the ledger, or month-end reconciliation between development and accounting takes days.
- Nonprofit Cloud Experience Cloud portalsVolunteer coordinators schedule by phone and email, or participants and grantees send paperwork as attachments.
- Nonprofit Cloud Marketing Cloud"Every donor gets the same appeal," or the team exports lists to a separate email tool and imports results back by hand.
- Clean fundraising data Agentforce for NonprofitGift officers spend hours on prospect research before visits, or donor services fields the same recurring-gift change requests every week.
Objections, and what to say (6)
"Salesforce is free for nonprofits, so why does this cost anything?"
Be direct: Power of Us provides 10 Nonprofit Cloud Core licenses to eligible organizations, and that is a real benefit. It does not cover additional users, add-on products or the work of designing the data model, migrating gift history, integrating payment and accounting systems and training staff. Ask how many people need access and which integrations matter, then show the license math separately from services. If services pricing comes up, Abstrakt bills $185–$225 per hour, plus a written estimate after discovery.
"We're on NPSP and it works. Why move?"
If it works and the roadmap is modest, staying can be the right answer, and Salesforce says NPSP will continue to be supported. Ask what they want next: native program and outcome tracking, volunteer management, gift commitments for pledges, prebuilt agents. Those live in Nonprofit Cloud, and Salesforce recommends it for new customers. Be honest that moving means a new data model and a migration, not a button. Offer a health check on the current org so the decision rests on facts about their customizations.
"Our donor database vendor already does fundraising."
Agree that a dedicated donor system can handle gift processing. Then ask where program data, volunteer hours, grants and case notes live, and how often staff copy data between those systems. The case for Nonprofit Cloud is one constituent record across fundraising, programs and volunteers, plus a platform the organization can extend without waiting on a vendor's release cycle. If the only need is gift entry for a small shop, say so and let them decide.
"Our board won't approve a big technology project."
Break it into phases the board can evaluate. Phase one usually covers constituents, gifts, acknowledgments and the accounting handoff, because those touch the audit and the donor experience. Programs, volunteers and portals follow once the foundation is stable. Give the executive director a one-page summary that shows the problem in board language: reconciliation hours, late acknowledgments, outcomes they cannot report. Ask whether a board member with finance or technology experience can join a working session.
"We don't have staff to run Salesforce."
This is often the truest objection in the room, so treat it seriously. Ask who maintains the current system and how many hours a week it takes. Design for a small team: fewer custom objects, standard Nonprofit Cloud features, documented processes and a named internal owner. Then decide together whether support comes from staff, a part-time admin or a partner on a defined monthly scope. A plan for year two belongs in the proposal, not in a follow-up after go-live.
"We tried Salesforce years ago and staff hated it."
Find out what they were asked to do. Many older nonprofit orgs were built by a volunteer or an early consultant, then customized by several more, until nobody trusted the reports. Ask whether gift officers or program staff got anything back for their data entry. Abstrakt offers a free health check for customers that AEs refer, which gives the organization an independent view of whether to fix, rebuild or move to Nonprofit Cloud.
Implementation watch-outs to raise before signature (6)
Settle the constituent and household model early
Nonprofit Cloud uses person accounts for individuals and business accounts linked to party relationship groups for households. Person accounts cannot be turned off once enabled. Grantmakers that fund only organizations may not need them at all, according to Salesforce's guidance. Make the decision with development and programs in the room, and document how a household is defined.
Do not build in a trial org
Salesforce's Power of Us page says trial orgs do not convert to production and that approved organizations are provisioned an org with their licenses. Teams that start configuring in a trial lose that work. Apply for Power of Us, or confirm the license path, before the build begins.
Map gift history before you promise a date
Years of gifts, pledges, soft credits, tributes and designations need to land on new objects with the right history. Duplicates and inconsistent campaign or fund codes are common in older databases. Run a data profile in discovery and budget for cleanup, test loads and a reconciliation of migrated totals against finance's records.
Agree the accounting handoff with finance
Decide which system owns funds, designations and the chart of accounts, whether Accounting Subledger output will be exported or integrated, and who resolves mismatches. Finance needs to see restricted and unrestricted revenue handled in a way that supports reporting net assets with and without donor restrictions. Get the controller's sign-off on the mapping before go-live.
Protect sensitive program data
Case notes, health information and details about vulnerable participants need tighter access than donor records. Define who sees what by role before configuring sharing, and check obligations the organization has under funder agreements or privacy law. Test access with real program staff, not only administrators.
Rebuild integrations for the new objects
Online giving, event, peer-to-peer and payment tools that wrote to NPSP opportunities will not write to gift transactions without changes. List every integration, check whether the vendor supports Nonprofit Cloud and plan cutover so no gifts are lost during the switch.
Qualify honestly
Strong fit
- Development and finance both describe reconciliation or acknowledgment problems in their own words.
- The executive director sponsors the project and can name the board members who will review it.
- They want at least two of fundraising, programs, volunteers or grantmaking in one system.
- There is a named internal owner with time allocated, or budget for ongoing support.
- A trigger exists: a capital campaign, a new executive, an audit finding or a donor database contract ending.
Risky fit
- The only motivation is free licenses, and nobody has budgeted for implementation or support.
- An NPSP org with heavy custom code where the team expects a quick upgrade.
- No one from finance has been involved, but accounting integration is in scope.
- Program data includes sensitive case information and nobody has defined who may see it.
- The board has not been told a project is coming, and the decision depends on a meeting months away.
Questions (4)
Should I sell Nonprofit Cloud or keep an NPSP customer on NPSP?
Sell Nonprofit Cloud when the customer wants program, outcome, volunteer or grantmaking capabilities, or when their NPSP org is so customized that a rebuild is already on the table. Keep them on NPSP when it meets their needs and they have no appetite for a migration. Salesforce says NPSP will continue to be supported, so there is no deadline to invent.
Can I say Salesforce handles IRS acknowledgment requirements?
No. The IRS rules on written acknowledgments for gifts of $250 or more, and on disclosures for quid pro quo contributions over $75, apply to the organization. Nonprofit Cloud can generate acknowledgments and tax receipts from templates, but the organization decides the content and stays responsible for it. Bring the finance lead into template design.
Who should I meet besides the executive director?
Meet the development lead, the finance lead and the person who maintains the current database by the second meeting. Program leadership should join when programs or outcomes are in scope. Ask about the board's review process early, because a board or finance committee approval can add weeks.
How does Abstrakt help on a nonprofit deal?
We can join discovery, profile the existing donor data, scope an NPSP to Nonprofit Cloud migration or the accounting handoff, and run a free health check for customers you refer. Abstrakt holds 138 certifications and replies to AEs within 4 business hours.
Sources (16)
- Salesforce: Nonprofit Cloud and Salesforce for nonprofits
- Salesforce: Nonprofit Cloud product page
- Salesforce: Nonprofit Cloud pricing and Power of Us licenses
- Salesforce: Power of Us program
- Salesforce: Nonprofit Success Pack and managed packages
- Salesforce Help: What's included in Nonprofit Cloud
- Salesforce Help: Complete Nonprofit Cloud prerequisites (person accounts)
- Salesforce Help: Fundraising in Nonprofit Cloud
- Salesforce Help: Welcome to Accounting Subledger
- Salesforce: Fundraising software for nonprofits
- Salesforce: Program and outcome management for nonprofits
- Salesforce: Volunteer management
- Salesforce: AI use cases for nonprofit fundraising
- IRS: Charitable contributions, written acknowledgments
- IRS: Charitable contributions, quid pro quo contributions
- Journal of Accountancy: FASB not-for-profit financial reporting standard (ASU 2016-14)