Most nonprofits switch on Salesforce Nonprofit Cloud, set up fundraising, and then quietly skip the case management piece. Beneficiary cases end up in spreadsheets, or in a loose mix of Tasks and custom objects that nobody documented. Six months later, the team can't answer a basic funder question about client outcomes without three people digging through tabs.
The Salesforce documentation doesn't help much here. It assumes you already know the data model, throws around terms like Care Plan and Indicator with little context, and never tells you which decisions to settle before you start clicking. So the task lands on an admin or an IT director who reads for an hour and comes away more confused than when they started.
This guide walks through what Nonprofit Cloud case management actually does, the decisions to make before you build, how to set it up step by step, and the mistakes that force teams to rebuild later. We've helped nonprofits across the UK, US, Europe, Africa, and Australia configure case management on Salesforce, so the advice here is grounded in real implementations.
One naming note before we start. Salesforce renamed Nonprofit Cloud to Agentforce Nonprofit in late 2025, so you'll see both names across Salesforce's own pages and in the wider community. They refer to the same product. This guide uses "Nonprofit Cloud" throughout for clarity, and everything here applies to Agentforce Nonprofit too.
What Is Salesforce Nonprofit Cloud Case Management?
At its simplest, Nonprofit Cloud case management tracks the people you serve through a structured support journey: intake, assessment, a care plan, the services you deliver, and the outcomes you measure. Salesforce calls the people you serve participants. Everything about a participant's engagement lives in one place, so your case managers get a full view of progress, spend less time on administrative tasks, and stop piecing it together from inboxes and spreadsheets.
If your org grew up on the older Nonprofit Success Pack (NPSP), case management was a separate managed package bolted on top of the platform. Salesforce stopped adding new features to NPSP in March 2023 and now puts its investment into Nonprofit Cloud, where case management is built into the core platform natively. NPSP still works and is still supported, so existing orgs have time to weigh NPSP against Nonprofit Cloud and plan a move at their own pace.
A handful of objects do the heavy lifting. The Person Account holds the individual you serve. A Referral records a request for help. A Case acts as the folder for that person's whole relationship with your organization. The Care Plan pulls together their goals, the benefits and services they receive, tasks, and notes. Outcomes flow through the Indicator and Outcome objects, which is how you prove impact to funders.
Case management fits any org that supports individuals over time: social services, homelessness and housing organizations, health and human services, workforce development, and refugee resettlement. If your work is purely fundraising, you may never need it. If you run programs that follow people from intake through to outcome, case management becomes the core of your system and a steady source of operational efficiency.
Nonprofit Cloud vs. Standalone Nonprofit Case Management Software
A question we hear often: "We're already on Salesforce. Do we still need separate nonprofit case management software like Apricot, CharityTracker, or CaseWorthy?" Many nonprofits buy one of these tools simply because they didn't realize Nonprofit Cloud already includes case management.
Nonprofit Cloud is usually the stronger fit when you're already on Salesforce, you want donor, program, and case data in a single system, you have an admin or partner who can configure it, and your needs sit within what the platform supports. Keeping everything in one place removes the data silos that appear once you run a separate case tool alongside your CRM.
A standalone system can still make sense in narrow situations, for example highly specialized legal case management, court-mandated fields, or specific regulatory requirements the platform doesn't cover out of the box. Being honest about that matters. The goal is the right fit for your programs, and occasionally that means a dedicated tool.
For most nonprofits already invested in Salesforce, buying separate case management software adds cost, another login, and another integration to maintain. Nonprofit Cloud handles the core client journey well, and it keeps your case data next to your fundraising and program data, which is exactly where your reporting needs it.
Before You Build: 6 Decisions to Make First
This is the part the documentation skips, and it's where most re-work comes from. Settle these six questions before you touch configuration. Get them right and setup moves quickly; get them wrong and you'll be rebuilding after go-live.
- Who are the people you serve? Individuals, families, or organizations? This shapes how you set up Person Accounts and household relationships from day one.
- What does your intake process look like? Mapping it first determines how you design your intake forms and the path from referral to active case.
- What outcomes do you need to report? Funders ask for outcome data, so map your indicators before you build anything. Adding them after the fact is painful.
- Do you need to assign staff to specific clients? This affects your relationship setup and how you share records across the team.
- Do you need a portal for external access? Bringing Experience Cloud into the picture changes the whole architecture, so decide early.
- How does case management connect to fundraising and program data? This needs object relationship planning across the entire org, including the links back to fundraising and program data. The thread running through all six is the same: map the full client journey on paper before you configure a single field. We've seen it in our own projects. The implementations that go smoothly are the ones where the data model was agreed before anyone opened Setup.
How to Set Up Salesforce Nonprofit Case Management Step by Step
Here's the practical sequence. This isn't a full technical manual, but it's enough for a competent admin to follow along and understand what each step is for and why it matters.
- Enable case management. Nonprofit Cloud case management isn't switched on by default. Turn on the feature and assign the relevant permission sets so your case workers can see and use it.
- Configure Person Accounts. Nonprofit Cloud uses Person Accounts to represent individuals, which behaves differently from standard Contacts or Leads. Setting this up correctly upfront saves a messy rework later.
- Use a guided intake flow. Salesforce provides OmniStudio (OmniScripts and FlexCards) with Discovery Framework for dynamic assessments, plus Action Plan Templates for intake checklists — or the standard intake path to capture referral details and turn them into a Case. Note that OmniStudio is migrating from its managed package to a Standard Runtime, so check which one your org is on before you build.
- Build Care Plan Templates. Create reusable templates for common situations such as housing support or food assistance, each with the goals, tasks, and benefits it needs. Templates save your team from rebuilding a plan for every participant.
- Configure benefits and service tracking. Set up the benefits and services you deliver, and define how staff log each delivery against a Case and Care Plan, including what was delivered, when, and by whom.
- Set up outcomes tracking. This is the step teams skip most often. Configure your Indicators and Outcomes so you can report measurable impact to funders. Funders increasingly require this, and retrofitting it is hard.
- Test with a sample case. Before go-live, run a fictional participant through the full journey from intake to case close. Check that every object populates correctly and your reports return what you expect. Treat that sample case as your dress rehearsal. If something doesn't populate the way you planned, fixing it now is far cheaper than discovering it once real client data is flowing in.
Common Salesforce Case Management Mistakes (And How to Avoid Them)
A few patterns come up again and again, often in orgs that read the docs but skipped the planning. Each one is avoidable.
- Skipping the data model design phase. When objects get used in ways they were never meant for, reports break and data turns messy. Map the full client journey before you configure anything.
- Leaving outcomes tracking until later. Funder reports depend on outcome data, and adding indicators after go-live means reworking existing records. Map your outcomes before you build the rest.
- Ignoring permission sets and data visibility. If every case worker can see every client, you have a data protection problem, and under GDPR that's a real risk for UK and EU organizations. Design your sharing rules before go-live. We've helped nonprofits refine exactly this kind of sharing and access model after a quick initial setup left everyone seeing everything.
- Building without an Experience Cloud plan. Retrofitting a participant or partner portal onto an existing case setup is slow and expensive. Decide upfront whether you need external access.
When to Bring in a Specialist
Plenty of nonprofits configure Nonprofit Cloud case management themselves, and that's a reasonable path if you have a strong NPC-certified admin, a clear data model, and a small program team. If that describes you, this guide may be all you need.
It's worth bringing in a partner when you're migrating data from a legacy case management system, when you need an Experience Cloud portal alongside case management, when funders impose complex outcomes frameworks, or when you've already built something that isn't working and needs untangling.
We've worked at both ends of that spectrum through our Salesforce Nonprofit Cloud implementation work: standing up case management from scratch and repairing implementations that drifted off course. We rebuilt a costly events integration for a UK humanitarian nonprofit, migrated and deduplicated millions of records for an animal-welfare nonprofit moving onto the platform, and built a beneficiary portal for a social-housing enterprise in Africa where families could submit applications and track requests in real time.
Why MagicFuse for Salesforce Nonprofit Cloud
- Salesforce Summit Partner with 11+ years in the Salesforce ecosystem and 150+ delivered projects.
- 80+ certified Salesforce consultants and 270+ Salesforce certifications, including Nonprofit Cloud and architect-level specialists.
- Nonprofit experience across the UK, US, Europe, Africa, and Australia, spanning fundraising, program delivery, portals, and large-scale data migration.
- A track record of building on the core platform, including AppExchange managed packages, so your case management setup is designed to scale with your programs.
FAQs
- What is Salesforce Nonprofit Cloud case management?
It’s the part of Nonprofit Cloud that tracks the people you serve through a structured journey: intake, assessment, a care plan, the services you deliver, and the outcomes you measure. It keeps client data in the same system as your fundraising and program data, so your team works from one full view of each participant.
- What are the main features of Salesforce Nonprofit Cloud case management?
The core case management features follow the whole client’s journey: intake and referrals, assessments, care plans, service delivery, and outcomes tracking. Case managers can log services, incidents, notes, and supporting files against each Case, and built-in document management keeps consent forms and records attached where they belong. Together these case management capabilities give the team a full view of every participant in one system. They sit on the same Salesforce platform as your fundraising and program data, so reporting draws from a single source.
- Is NPC case management the same as the old NPSP case management package?
No. The NPSP version was a separate managed package added on top of the platform, and Salesforce stopped adding new features to it in March 2023. Nonprofit Cloud has case management built into the core platform with a different data model, so it works differently. Existing NPSP orgs remain supported and can plan a move on their own timeline.
- Do I need separate case management software if I’m already on Salesforce?
Usually no. If you’re already on Salesforce, Nonprofit Cloud includes case management, and keeping everything in one system removes the data silos a separate tool creates. A standalone tool can still fit narrow needs such as highly specialized legal case management or court-mandated fields the platform doesn’t cover out of the box.
- How long does it take to set up NPC case management?
There’s no single answer. Setup time depends on the complexity of your programs, how many integrations and data migrations are involved, the state of your existing data, your team’s availability, and how ready your org is to start. A simple single-program setup is far quicker than a multi-program org with a legacy migration and a portal. The honest way to scope it is a short conversation about your specific situation.
- What is a Care Plan in Salesforce Nonprofit Cloud?
A Care Plan is the record that pulls together everything your team uses to support one participant: their goals, the benefits and services they receive, tasks, and notes. You build Care Plans from reusable templates, so common situations like housing support follow a consistent structure every time.
- Can beneficiaries access their own case information through a portal?
Yes. You can give participants or partner agencies secure access through Experience Cloud, for example to submit applications, view their status, or track requests. Because a portal changes the underlying architecture, decide whether you need one early, before you finish building case management.
- What are Salesforce case management best practices for nonprofits?
The most reliable best practice is to map your client’s journey and data model before you configure anything. Settle who you serve, your intake process, and the outcomes you report, then design sharing rules so case managers see only the clients they should. Done well, a nonprofit case management system improves operational efficiency, cuts repetitive administrative tasks, and removes the data silos that slow reporting down. It also makes collaboration with other agencies easier, because everyone works from the same records, and the setup can be configured to your organization’s unique needs.
