Key Takeaways
- Map your grant lifecycle before you change anything in Salesforce.
- Keep grants separate from individual gifts so restrictions and deadlines have a home.
- Build funder reports during setup and test them against a real funder request.
- Salesforce still supports NPSP for existing customers and recommends Agentforce Nonprofit (formerly Nonprofit Cloud) for new ones.
A grant award letter is good news that comes with homework. The funder expects you to spend the money on what you proposed, hit the milestones you promised, and report back on their schedule, sometimes for several years. A one-time online gift rarely asks for any of that.

Many nonprofits manage this work in Salesforce NPSP, the Nonprofit Success Pack. NPSP handles grants well when someone has decided, up front, how a grant should move through the system. When that planning gets skipped, grant details end up in spreadsheets and inboxes, and every funder report becomes a last-minute search for numbers.
We see grant work from more than one side. At Vectr Solutions, we have built grant lifecycle systems for funders, including the proposal and contract management solution we delivered for BioMADE, a nonprofit that awards funding to biomanufacturing projects.
Our public sector and federal work also keeps us close to the audit and reporting expectations that come with government money. That experience shapes how we think about what a grantee’s Salesforce org needs to hold. This guide walks through how to plan a grant workflow in NPSP, the setup mistakes we run into most often, and what Salesforce’s newer nonprofit product means for your plans.
What the Nonprofit Success Pack Does and Where Grants Fit
The Salesforce Nonprofit Success Pack is a free, open-source add-on (Salesforce calls it a managed package) that sits on top of standard Salesforce and adds the records nonprofits need to track people and money. A handful of terms come up in every NPSP conversation:
Together, these give your development team one place to see who supports you and how. That is the core of nonprofit donor management in Salesforce.
The word “grants” causes confusion because it describes two different jobs. This article covers grants your organization receives: you apply to a foundation, corporation, or government agency, win an award, and report back on how you used it. Grantmaking is the reverse, where your organization gives money out and runs the applications, reviews, and payments. Grantmakers need different tools, and Salesforce sells Grantmaking as its own edition of Nonprofit Cloud.
Received grants need more planning than donations because the money comes with conditions. A grant may cover only one program, require a budget-to-actuals report every quarter, or pay out in installments tied to milestones. A three-year foundation grant can keep your team reporting to that funder long after the first check clears, so the system has to hold those obligations from day one.
Planning a Grant Management Workflow in Salesforce
The strongest Salesforce grant management projects we see start at a whiteboard. Before anyone opens Setup, map each stage a grant moves through at your organization and write down what happens at each one. Most grant lifecycles look something like this:
-
1Prospecting and application
Researching funders, writing letters of inquiry, and submitting proposals
-
2Award
The funder approves the request and sends an award letter or agreement
-
3Terms and restrictions
What the money can pay for, and for how long
-
4Spending and deliverables
The work you promised and the budget you track against
-
5Reporting
Interim and final reports, both narrative and financial
-
6Renewal
Reapplying, or closing the grant out
Reapplying starts the cycle again at step 1
Decide which records represent each stage
In NPSP, a grant is usually an Opportunity with the Grant record type. Its stages, the steps a record moves through, can mirror your real process: Prospecting, LOI Submitted, Proposal Submitted, Awarded, Declined. Each grant should link to the funder’s Organization Account, the program officer’s Contact record, and the staff member who owns it internally. When a grants manager leaves, the relationship history stays in Salesforce instead of leaving with them.
Define ownership and handoffs
Grants touch development, finance, and program staff, and each team needs to know what it updates and when. Development writes proposals and manages the funder relationship. Finance tracks payments and spending against the grant budget. Program staff deliver the work and collect the outcome data the funder wants to see. The moment a grant moves to Awarded is a natural handoff point: development updates the stage, finance sets up the payment schedule, and program staff get a task to review the deliverables.
Keep grants distinguishable from individual gifts
One $250,000 multi-year grant can make your average gift look enormous and throw off donor retention numbers. Use record types and report filters so leadership can see individual giving and institutional funding side by side. NPSP’s donor rollups, the automatic totals that show lifetime giving on each Contact and Account, can also be set up through Customizable Rollups to include or leave out specific record types.
Tracking Funding and Reporting to Funders
Once a grant is awarded, the work shifts from winning the money to accounting for it. Record the full award amount on the grant’s Opportunity, then use NPSP Payments to schedule each expected installment with its amount and due date. Payments are child records attached to the grant, and finance marks each one paid as it arrives, so development and finance work from the same schedule.
Restrictions need a home too. NPSP includes General Accounting Units, usually shortened to GAUs, which represent the funds or programs your money supports, such as a youth literacy program or a capital campaign. GAU Allocations let you split one grant across several of them, so you can show exactly which programs a grant pays for and how much of it is restricted.
Reporting deadlines buried in a PDF award letter are easy to miss. NPSP includes Grant Deadlines, a related list on each grant where you log every interim report, final report, and milestone with its due date. From there, a simple Flow (Salesforce’s point-and-click automation tool) can email the owner 30 days before each deadline.
Each expected installment, marked paid as it arrives
- $30,000Jan 15Paid
- $30,000Apr 15Paid
- $30,000Jul 15Scheduled
- $30,000Oct 15Scheduled
Which programs the grant pays for, and how much is restricted
- Youth literacy program$90,000
- Capital campaign$30,000
Every report and milestone, logged with its due date
- Interim reportJun 30Due soon
- Program milestoneSep 1Upcoming
- Final reportDec 31Upcoming
Who changed a value, when, and what it was before
-
Award amount:
$100,000→ $120,000 Development Director, Mar 3 -
Stage:
Submitted→ Awarded Grants Manager, Feb 18 -
Payment date:
Jun 15→ Jul 15 Finance, Mar 10
Example grant record in Salesforce NPSP
Outcome data belongs in the same system. If program staff already track attendance, services delivered, or volunteer hours in Salesforce, funder reports can pull from the records they use every day. We cover that side in our guide to Salesforce nonprofit program management.
Build at least one funder report during setup and test it against a real requirement from a current funder. If a funder asks for participants served by zip code and nobody collects zip codes at intake, you want to learn that in month one, well before the report is due.
Finally, turn on field history tracking for the fields that matter most, such as award amount, stage, and payment dates. Salesforce then logs who changed each value, when, and what it was before (up to 20 tracked fields per object). In our work with government agencies and federal contractors, a change log like this is a basic audit expectation, and grant dollars deserve the same care. When a program officer or auditor asks why an award amount changed, you can answer in minutes.
Common NPSP Setup Mistakes
We are often brought into NPSP orgs after these problems have piled up for a few years. Each one is far cheaper to prevent during setup than to untangle later.
Treating grants like donations
When grants use the same record type and fields as individual gifts, restrictions and deadlines have nowhere to live. Staff start tracking them in a spreadsheet, and within a few months that spreadsheet and Salesforce disagree.
Letting duplicates build up
Without a data-entry standard, one foundation can end up as three Accounts: “Smith Family Foundation,” “The Smith Foundation,” and “Smith Fdn.” Each holds a piece of the relationship history. Salesforce duplicate and matching rules can flag likely duplicates as staff type, and they work best paired with a short written standard for entering names and addresses.
Customizing without documentation
Custom fields and automations added over the years with no notes on why they exist make an org fragile. The next administrator is afraid to touch anything, and upgrades drag on. A shared document listing each customization, its purpose, and its owner prevents most of this. Reports nobody trusts, automations nobody can explain, and staff keeping side spreadsheets are all signs your Salesforce org needs a health check. Our article on the risks of DIY Salesforce implementations explains how this kind of technical debt builds up in small teams.
Waiting for a funder to ask for a report
Reports built in a rush after a request usually expose missing data. By then, the only fixes are manual cleanup or asking program staff for numbers they never recorded.
No named data owner or training plan
Every NPSP org needs a named administrator, even a part-time one, who owns data quality and approves changes. New staff also need onboarding on how your organization uses Salesforce, because a well-built system still breaks down when five people enter data five different ways. Choosing between an in-house Salesforce admin and a managed services provider usually comes down to how many admin hours you can realistically fund.
If some of these sound familiar, you don’t have to sort them out alone. Our team reviews existing NPSP orgs, finds what is causing reporting problems, and helps fix the setup so your staff can run it going forward. Speak to an expert about where your org stands.
NPSP and Nonprofit Cloud: What to Know Before You Plan
If you are planning grant work in NPSP today, you will hear about Salesforce’s newer nonprofit product. Salesforce launched Nonprofit Cloud in 2023 and in December 2025 renamed it Agentforce Nonprofit. Both names show up online, so we use Salesforce Nonprofit Cloud here because it is the name most teams still search for.
The NPSP vs Nonprofit Cloud question starts with how each one stores data. NPSP is an add-on built on Salesforce’s Sales and Service Cloud, organized around Household Accounts and Opportunities. Nonprofit Cloud is built into the core Salesforce platform and uses a different set of records:
Because the underlying records change, moving from NPSP to Nonprofit Cloud means remapping your data, automations, and reports onto a new structure, usually in phases. Teams sometimes hope to lift and shift their data over as is, and the different data model rules that out. Plan for it the way you would plan a new implementation.
On its own nonprofit pages, Salesforce describes NPSP as its original nonprofit data model, says it will continue to support NPSP for its many customers, and recommends Nonprofit Cloud for new customers. Salesforce no longer adds new features to NPSP, and since December 2025 new Power of Us orgs start on Agentforce Nonprofit instead. It has not announced a retirement date for NPSP. Check Salesforce’s current nonprofit pages and Help documentation before you commit to a direction.
For organizations that give grants, Salesforce points new customers to its Grantmaking edition of Nonprofit Cloud. Salesforce describes it as covering applications, reviews, and awards; grantee budgets and progress reports; requirements, contracts, and disbursements; and outcome tracking. NPSP grantmakers have used the free Outbound Funds Module for this work. For most operating nonprofits that only receive grants, a well-planned NPSP setup covers the need. If you also re-grant funds to partners or run your own application process, a dedicated grantmaking tool is worth evaluating.
When teams compare NPSP and Nonprofit Cloud, the right answer depends on a few practical questions:
-
How healthy is your current org?
Clean data and documented automations make any future move easier, and a messy org carries its problems with it.
-
How much staff time can you give the project, especially during grant reporting season?
-
When do your major funding cycles and fiscal year end fall?
Avoid a cutover near a big report deadline.
-
Does Nonprofit Cloud’s data model fit how you work, including apps you connect to NPSP today?
-
What are your timeline and budget?
Nonprofit Cloud implementation cost depends heavily on how much data and customization you bring over.
For many organizations with a working grant process, improving the current NPSP org is a sensible near-term step. The cleanup pays off whichever platform comes next. Organizations new to Salesforce should start on Nonprofit Cloud.
How Vectr Solutions Helps Nonprofits Become Self-Sufficient Salesforce Users
Our goal on every nonprofit project is simple: when we step back, your team owns and runs Salesforce with confidence. We take a delivery-first approach led by Salesforce architects, and our team holds more than 85 Salesforce certifications. Most of our work is in public sector, federal, and nonprofit environments where audit trails and reporting rules are part of daily operations, and we bring that same discipline to grant workflows.
Through Salesforce implementation and advisory and governance support, we help you make the data model and workflow decisions covered in this article, whether you are refining NPSP or planning a phased move to Nonprofit Cloud. For BioMADE, that meant digitizing its proposal process from application to contract close, centralizing project information and tasks, and adding document generation and e-signature through DocuSign inside Salesforce.
We also help organizations build internal Salesforce practices through training, written documentation, and coaching for your administrator. The result is a team that can add a funder report or update grant stages without calling a consultant.
Adoption is where many rollouts stall, so we use Prosci-certified change management to prepare development, finance, and program staff for new ways of working. For organizations that want ongoing help, Managed Services provide senior Salesforce support and regular org reviews while your staff stays in charge.
Plan a Grant Workflow Your Team Can Run on Its Own
A grant workflow works best when your own team can run it, report from it, and adjust it. Vectr Solutions helps nonprofits plan their Salesforce data model and reporting, then builds the internal skills to keep it running. Talk with an expert about where to start.