How to Track Grants in Salesforce Nonprofit Cloud: Complete Setup

If your nonprofit or foundation is running a grants program on Salesforce — either as the grantee tracking outbound applications and awards, or as the grantmaker managing inbound applications and disbursements — the data model matters enormously. This guide walks through how to track grants in Salesforce Nonprofit Cloud using the platform’s native grant management objects, the lifecycle stages that match how real foundations and nonprofits actually work, and the reporting patterns that surface program performance without endless CSV exports. If you’re still on NPSP (Nonprofit Success Pack), this guide also explains what changes when you move to Nonprofit Cloud.

The Big Shift From NPSP to Nonprofit Cloud

In NPSP, most nonprofits tracked grants as a specialized Opportunity record type. It worked, but it forced everything into the sales-shaped Opportunity object — Amount became grant amount, Stage became grant lifecycle, Close Date became award date. Custom fields carried grant-specific data. Reporting worked but often required custom report types and formula acrobatics.

Nonprofit Cloud replaces that with dedicated grants objects: Grant Application, Grant Award, Grant Deliverable, Program, and related outcome-tracking objects. Each represents one thing rather than being a rebranded Opportunity. The tradeoff is that migration from NPSP requires deliberate mapping — our post on the NPSP to Nonprofit Cloud migration timeline walks through what that looks like in practice, along with the phased approach we’ve deployed for CN nonprofit clients.

The Core Grants Data Model in Nonprofit Cloud

Understanding the shape of the data before you configure anything saves months of rework. The core grants-related objects and how they relate:

• Program — the umbrella under which grants live. A foundation’s “Youth Literacy Initiative” or a nonprofit’s “Community Health Outreach” is a Program. Everything grant-related links up to a Program.
• Grant Application — an inbound (from an applicant) or outbound (to a funder) request for funding. Applications track status through the review lifecycle: submitted, under review, approved, declined.
• Grant Award — the funded outcome of an approved application. Awards carry the actual amount, term, restrictions, and payment schedule.
• Disbursement — individual payment tranches of an Award. A three-year $300k grant paid in three annual installments is one Award with three Disbursement records.
• Grant Deliverable — reporting or milestone commitments tied to an Award. Quarterly progress reports, annual impact reports, end-of-project financials.
• Outcome / Impact Records — the results the grant funded. Number of people served, programs launched, outputs delivered.

The Grant Lifecycle Stages Foundations Actually Use

The stages your Grant Application record moves through depend on whether you’re the grantmaker or the grantee. Real-world lifecycle stages we implement most often:

Grantmaker (foundation-side) lifecycle:

1. LOI Received
2. Full Application Invited
3. Application Submitted
4. Under Review
5. Board Committee Recommended
6. Board Approved
7. Grant Awarded (creates Grant Award record)
8. Declined / Withdrawn

Grantee (nonprofit-side) lifecycle:

1. Prospect Identified
2. LOI Sent
3. Full Application Submitted
4. Under Review
5. Awarded (creates Grant Award record)
6. Active (deliverables in flight)
7. Closed / Reporting Complete

Both lifecycles map cleanly to a Nonprofit Cloud Grant Application status picklist, with automation moving the record forward and creating downstream records (Award, Disbursement, Deliverable) as the stage advances.

Tracking Deliverables Without Losing Them

Deliverables are where nonprofit grant programs most often quietly fall apart. An award has a six-month narrative report due in September, an annual financial report due in December, and an impact report due at closeout. Missing deliverables damages the funder relationship and can jeopardize future funding.

The pattern we deploy for CN clients:

• Every Grant Deliverable record has a due date and an owner — the specific person responsible, not “the grants team.”
• A Flow creates the standard deliverable set automatically when an Award is created — no manual tracking spreadsheets.
• Escalation reminders fire 30 days, 14 days, and 3 days before each deliverable due date — nobody misses a report because they didn’t know it was coming.
• A single “Grant Deliverables Coming Due” dashboard is the program director’s first-thing-Monday view.

If any of this sounds like the mechanical setup pattern from our post on how to track billable hours in Salesforce, it’s the same idea applied to a different problem — a purpose-built object with a lightweight Flow around it beats a generic tracker every time.

Reporting: What Program Directors Actually Ask

Once the data model is right, the standard grants reports fall out naturally. The five reports we deploy for essentially every grant program:

1. Grant Pipeline by Program — Grant Applications by Stage, grouped by Program, summed by requested amount.
2. Active Awards by Funder — Grant Awards where Status = Active, grouped by Funder Account.
3. Disbursement Schedule (Next 12 Months) — Disbursement records with scheduled payment date in the next 12 months, grouped by month.
4. Deliverables Coming Due — Grant Deliverables where due date is within 30 days and Status ≠ Complete.
5. Grant Program ROI Snapshot — awarded amount versus documented outcome/impact records, grouped by Program.

Each report is a report on one object with maybe one lookup. No cross-object join reports, no formula acrobatics, no half-loaded custom report types. This is the reporting simplicity Nonprofit Cloud’s purpose-built model was designed to enable.

A Real Example: A National Nonprofit’s Unified Donor + Grant Platform

Cloud Nexus recently built a unified donor and grant platform for a national nonprofit, consolidating separate tracking systems for individual giving, foundation grants, and government grants into a single Salesforce-based platform. The pattern — one platform for both funder relationships and grant-specific lifecycle tracking — is documented in our National Nonprofit unified donor grant platform case study. It’s the same core Nonprofit Cloud data model this guide walks through, extended for the client’s specific program structure.

Common Setup Mistakes to Avoid

• Skipping Program setup. Programs are the umbrella every grant should link to. Nonprofits that treat Program as optional end up with grants that can’t be aggregated or reported on cleanly.
• Reusing Opportunity for grants because “it worked in NPSP.” It worked in NPSP because there was no better option. In Nonprofit Cloud, use the purpose-built objects.
• Creating one Deliverable object custom field for “everything.” A single “Deliverable Type” picklist ends up carrying quarterly reports, annual reports, financials, impact reports, and closeouts. Split them into distinct records for real due-date tracking.
• Automating without a lifecycle map first. Building Flows before mapping the lifecycle produces automation that fights the process instead of supporting it.
• Letting duplicate funder or grantee Accounts pile up. A grant program with three Account records for the same foundation splits award history across all of them and makes “Active Awards by Funder” reporting unreliable. If this has already happened, our guide on how to mass merge duplicate Accounts and Contacts in Salesforce without breaking data covers the cleanup process.

Most of these are covered in our detailed rundown of the most common nonprofit Salesforce challenges — a longer document on the patterns we see in nonprofit orgs across program types.

Frequently Asked Questions

Do I have to move to Nonprofit Cloud, or can I keep tracking grants in NPSP?

Existing NPSP customers can continue on NPSP for now, and NPSP-based grant tracking still works. New nonprofit implementations should generally start on Nonprofit Cloud. When to migrate depends on scale, complexity, and how much your current NPSP-based grants setup is bending Opportunity beyond what it should carry. Our post on the NPSP to Nonprofit Cloud migration timeline is the honest scoping tool.

Can Nonprofit Cloud track both grantmaker and grantee use cases in the same org?

Yes. Some organizations do both — receiving grants from funders and making grants to sub-grantees. Nonprofit Cloud’s model can handle both by using separate record types on Grant Application and Grant Award to distinguish direction. Reporting is done separately by record type.

How do we track multi-year grants?

The Grant Award record carries the full term and total amount. Individual Disbursement records represent each payment tranche within the term. This lets you report on both the full award commitment and the current-year expected cash flow separately without duplicating the underlying grant.

Does Nonprofit Cloud handle restricted funding tracking?

Yes — restrictions are typically captured on the Grant Award record itself (fields for restricted vs. unrestricted, purpose restrictions, geographic restrictions, etc.). For deeper fund-accounting integration, most nonprofits either connect Salesforce to their accounting system (Sage Intacct, NetSuite, QuickBooks) or use a Salesforce-native accounting layer.