Winter ’27 is about to land in most nonprofit production orgs. If your Salesforce instance follows the usual pattern, you have somewhere between a few days and two weeks before it shows up.
We’ve read the official release notes so you don’t have to. Here’s the short version: this is a small release for Agentforce Nonprofit. There are a handful of targeted features, a couple of them genuinely useful, and several need an add-on license before you can use them. The bigger to-do list for most organizations is on the platform side: security and email changes that affect every org, including those still on NPSP.
This post covers what’s new, what it means for your team, and what to test in your sandbox this week.
First, when does Winter ’27 hit your org?
Salesforce rolls out major releases in waves, instance by instance. According to Salesforce Trust, the Winter ’27 schedule looks like this (Eastern time):
-
- Preview sandboxes: upgraded August 28 to 29, 2026
-
- A small group of production instances: September 4 to 5, 2026
-
- Most production instances: the overnight windows of October 2 to 3 and October 9 to 10, 2026
-
- Non-preview sandboxes: October 9 to 10, 2026
To find your exact date, go to status.salesforce.com, search for your instance or My Domain, and open the Maintenances tab. If your sandbox is a non-preview sandbox, it upgrades the same weekend as production, which means you don’t really get a test window. It’s worth checking now. (Salesforce’s newsroom lists the release as generally available October 12, 2026.)
The naming thing, one more time
The Winter ’27 notes make it official: “Nonprofit Cloud is now Agentforce Nonprofit,” and Education Cloud is now Agentforce Education. Salesforce also says you’ll keep seeing “Nonprofit Cloud” in some screens and documentation for a while. The rename doesn’t change your data model or your reports, and the notes don’t mention any licensing change.
Fundraising: households finally maintain themselves
This is the headline for fundraising teams, and it’s the feature we expect clients to ask about first.
1. Automatic household naming
Anyone who has run a donor database knows the household-naming problem. A couple gets married, a spouse passes away, an adult child moves out, and suddenly your year-end appeal goes to “The Smith Household” when it should say “Maria and James Lopez.” Someone on staff has to notice and fix it by hand, one record at a time.
Winter ’27 lets your admin set up formula-based naming templates once. After that, Salesforce recalculates household names automatically whenever members are added, removed, or updated. There are also new controls to exclude specific people or households from auto-naming (for those donors who are very particular about how they’re addressed) and to set the order members appear in the name. Admins can also recalculate household names and greetings from a flow.
What it means for you: cleaner mailings, fewer awkward salutations, and one less cleanup task before every campaign.
2. Create households during gift entry
Gift processors can now check Auto Create Household in the Gift Entry Grid when adding a person account as a donor. If that donor doesn’t belong to a household yet, Salesforce creates one and adds them on the spot. The same option exists in the Business Process API, which matters if your online giving platform or a partner integration creates gifts in bulk.
What it means for you: no more “orphan” donors who show up in reports without a household, and no custom automation for your admin to build and maintain.
The honest caveat: both household features require the Automatic Household Creation and Naming add-on (Enterprise, Unlimited, and Developer editions). Before you promise automatic household names to your development director, confirm that add-on is on your contract.
3. Household soft credit fields
The Fundraising object changes include new fields for household soft credits: a source field on gift soft credits (for example, a household relationship), a total of hard and soft credits across household members on the donor gift summary, and a formula to exclude certain households from soft credit creation. Salesforce doesn’t publish a separate feature note explaining how these work together, so treat this as “coming into focus” and test it in a sandbox before you change any giving reports.
Programs: a ready-made participant portal
4. Program Participant Portal template
This one is for human services, youth development, workforce, and any organization running programs with applications and enrollments. The new Program Participant Portal Experience Cloud template gives participants secure self-service access to their programs, applications, enrollments, benefit assignments and disbursements, and referrals. It comes with preconfigured pages, navigation, and components, so you start from a working site instead of a blank page.
What it means for you: fewer “did you get my application?” phone calls, and more of your case managers’ time spent on actual casework.
The honest caveat: you need Program Management and Track Applications turned on, plus the Program and Case Management for Experience Cloud add-on. Each participant needs a permission set. Portals also bring their own security questions (see the guest user change below), so plan for a real configuration and testing effort, not a same-day launch.
5. Easier setup for Program, Case, and Outcome Management
Salesforce Go now walks admins step by step through setting up Program Management, Case Management, and Outcome Management from a single page, with feature usage tracking and help content built in. It isn’t flashy, but if you’re a small team turning on case management for the first time, guided setup saves real hours and reduces the chance of a missed step.
Grants: consistent, fairer reviews
6. Standardized and secured grant evaluation stages
For grantmakers, Winter ’27 tackles two long-standing headaches. First, you can build reusable Action Plan Templates for application evaluations, so every grant cycle follows the same multi-stage review instead of being rebuilt by hand. Second, with Compliant Data Sharing, you can limit reviewers to only the evaluation sections that match their expertise.
What it means for you: a repeatable review process, less setup at the start of each cycle, and a cleaner answer when your board or funders ask how you keep reviews fair. This applies to Grantmaking customers on Enterprise, Unlimited, and Developer editions.
Related: action plans across Industries clouds now support up to 200 tasks (up from 100), and you can report on action plan owners and targets.
Volunteers and AI: set up by agent
7. Turn on and configure Volunteer Management with AI agents
This is the most forward-looking item in the release, and the one to approach with the most care. Salesforce published a set of AI “skills” that let an agent turn on Volunteer Management, assign permissions, recommend a structure for your volunteer program (initiatives, positions, shifts, qualifications), and create records after you confirm the plan. It works through developer-oriented agent tools like Agentforce Vibes or Claude Code, and it requires connecting to the Headless 360 MCP Server, which is still in beta.
Our take: this is a partner and admin tool, not something your volunteer coordinator will use on Monday. It’s a clear preview of where Salesforce is headed with agent-driven setup, and it builds on the Headless 360 direction we covered after Summer ’26. The agent works with the permissions of the person who signs in, so the same rule applies as always: sort out your permissions before you connect an AI tool. Explore it in a sandbox.
We didn’t find any new Agentforce agents specifically for nonprofits, or any nonprofit Data 360 features, in the Winter ’27 Nonprofit notes.
Data and reporting: quieter Data Processing Engine improvements
Data Processing Engine (DPE) runs many of the rollups behind Agentforce Nonprofit. Winter ’27 adds several admin-level improvements:
-
- Clearer currency handling for multi-currency orgs
-
- Multiple sequenced formulas in a single step
-
- An option to roll up only the lowest-level values in a hierarchy
-
- A new “Completed with Failures” status, so partial failures don’t hide behind a success message
If you’ve ever wondered why a donor summary number looked off after a nightly job, that last item is the one to appreciate.
The platform changes that matter more than the features
These apply to every nonprofit org, whether you’re on Agentforce Nonprofit or NPSP:
-
- Profile filtering is enforced this release. Users won’t see other profile names unless they have the View All Profiles permission. If someone on your team manages users or builds reports on profiles, assign that permission first.
-
- Email verification exception (enforced December 1, 2026). If Salesforce Support once turned off email verification for your org, you need to set up an authorized email domain. If you don’t, unverified users can’t send email from Salesforce. That would be a bad surprise in the middle of year-end giving.
-
- Outlook users, check your sync. Microsoft is retiring Exchange Web Services for Office 365 starting October 2026, and Lightning Sync setups that use EWS will stop syncing unless you move to Microsoft Graph. Lightning Sync itself retires in 2027. Salesforce for Outlook is also being retired, but the notes give conflicting dates (November 1, 2026 and November 2027).
-
- Connected apps are moving to External Client Apps. Salesforce ends support for connected apps in Summer ’27. Now is a good time to inventory your integrations (payment processors, email marketing, event tools) and ask each vendor about their plan.
-
- Guest user data in portals. A new release update, enforced in Spring ’27, separates what guest users can see from what logged-in portal users can see. If you run a public donation page or a participant portal, review it.
What about NPSP?
Winter ’27 includes nothing specific to NPSP. The Nonprofit notes don’t mention it at all, and they don’t announce a retirement date or a migration deadline. NPSP orgs still get every platform change above, so regression testing still matters. Our view hasn’t changed since Dreamforce: NPSP keeps working, but new capability is being built for Agentforce Nonprofit, and releases like this one widen that gap a little more each time.
What to do this week: a sandbox testing checklist
-
- Find your upgrade date on Salesforce Trust, and confirm whether your sandbox is a preview sandbox (Setup, then Sandboxes, then the Release Type column).
- Check Release Updates in Setup. Look for Profile Filtering, Maintain Your Email Verification Exception, and Migrate All Connected Apps. Follow the testing steps for each one that appears.
- Run your core fundraising flows in the sandbox: a single gift, a recurring commitment, a soft credit, and a batch through Gift Entry. Then compare your donor summary rollups before and after.
- Test your integrations: your payment processor, online forms, email marketing sync, and any accounting export.
- Log in as a non-admin user. With profile filtering enforced, check that user management, reports, and list views still work for the people who rely on them.
- Check portals and public forms as a guest user.
- Confirm your licenses before you plan anything. Household naming and creation need the Automatic Household Creation and Naming add-on. The participant portal needs the Program and Case Management for Experience Cloud add-on.
- Pick one feature to pilot after go-live. For most fundraising teams, that’s household naming. For program-heavy organizations, it’s the participant portal. For grantmakers, it’s standardized evaluation templates.
GA or beta? A quick reference
-
- Generally available with Winter ’27 (edition, license, and setup required): automatic household naming, household creation during gift entry, the Program Participant Portal template, Salesforce Go setup for Program, Case, and Outcome Management, grant evaluation templates with Compliant Data Sharing, the Action Plans improvements, and the DPE improvements.
-
- Needs an add-on: household naming and creation (Automatic Household Creation and Naming), the participant portal (Program and Case Management for Experience Cloud).
-
- Depends on a beta: Volunteer Management setup with agents (requires the Headless 360 MCP Server, beta).
Frequently asked questions
Do we have to do anything when Winter ’27 arrives?
The new nonprofit features don’t turn on by themselves. Your admin decides when to set them up. The platform release updates are different: some are enforced on Salesforce’s schedule, so review them in Setup now.
Is automatic household naming included in our license?
Not automatically. Salesforce lists it as requiring the Automatic Household Creation and Naming add-on. Check your contract or ask your account executive before planning around it.
We’re on NPSP. Does this release affect us?
Yes, but only through the platform changes. None of the Agentforce Nonprofit features in this post apply to NPSP, and no NPSP retirement date was announced.
Is the new participant portal ready to use out of the box?
It’s a strong starting point with prebuilt pages, but you’ll still brand it, configure access, and test security before inviting participants. Most organizations should plan for a small project, not a toggle.
Should we use AI agents to set up Volunteer Management?
We’d explore it in a sandbox for now. The setup depends on a beta component, and it’s built for admins and partners who are comfortable with developer tools.