Maximizing Fundraising Impact with Salesforce Nonprofit Cloud

NPSP is retiring — plan the move now

Nonprofit Success Pack (NPSP) is transitioning to the Nonprofit Cloud built on Industries Common Components (OmniStudio, Business Rules Engine, Actionable Relationship Center). New implementations should start on Nonprofit Cloud; existing NPSP orgs get a documented migration path.

Key model differences to know:

Concept	NPSP	Nonprofit Cloud
Household	`npo02__Household__c` custom object	`PartyRelationshipGroup` (standard)
Recurring Gift	`npe03__Recurring_Donation__c` v2	`Gift Commitment` (standard object)
Rollups	Customizable Rollups (batch)	Actionable Segmentation + Data Cloud
Program tracking	`Program` / `Program Engagement`	`Program` / `ProgramEnrollment` (standard)

Data model: donor journey

Individual ─┬─► Contact
            └─► PartyRelationshipGroup (Household)
                 ├─► Gift Transaction ────► Gift Commitment (recurring)
                 ├─► ProgramEnrollment
                 └─► CaseSummary (advocacy)

Gift Entry that scales

Use the Gift Entry Lightning app, not custom pages. For bulk import (major-gift officer, gala reconciliation), define a Gift Entry template with allocations pre-filled:

Template: "Gala 2026 Batch"
  Default Campaign: Gala 2026
  Default GAU Allocation: 60% Programs / 30% Scholarships / 10% Operations
  Required: Donor, Amount, Payment Method

Batch processing writes GiftTransaction rows and posts allocations atomically.

Recurring giving: the compounding lever

Recurring donors give ~5× more lifetime value than one-time donors. Implementation checklist:

Enable Gift Commitment with Elevate for card processing + automatic retry on decline
Configure dunning: 3 retries over 10 days, then Case to steward
Segment lapsed recurring donors within 14 days — win-back windows close fast

Segmentation with Data Cloud

Move rollups out of the transactional org. In Data Cloud:

SELECT
  c.Id                          AS contact_id,
  SUM(g.Amount__c)              AS ltv,
  MAX(g.CloseDate__c)           AS last_gift,
  COUNT_IF(g.RecurringGift = 1) AS recurring_count
FROM   Contact__dlm c
JOIN   GiftTransaction__dlm g ON g.DonorId = c.Id
GROUP  BY c.Id

Publish as a Calculated Insight, activate segments to Marketing Cloud Engagement for email journeys.

Grants & program outcomes

Model programs with outcomes-based reporting:

Program → ProgramCohort → ProgramEnrollment
Track Indicator and IndicatorResult per enrollment
Roll up to Grant Reporting via a scheduled Flow

Compliance quick wins

Enable Field Audit Trail on donation-source fields (audit for restricted gifts)
Use Shield Platform Encryption on SSN / EIN if you accept in-kind stock
Configure Data Detect to catch PII entered into free-text notes

What to build first

Household model + Gift Entry
Recurring giving with Elevate
Data Cloud segmentation + Marketing Cloud journeys
Program outcomes dashboards
Grant lifecycle automation