Skip to main content
GroupsNonprofit Ask Me Anything (Global)Natalie Larino's Post
Natalie Larino (Salesforce) posted in Nonprofit Ask Me Anything (Global)
Sep 10, 3:13 PM

Hello! Here is the recap from our September 9th installment of our AMER AMA. Special shoutout to this month's panelists @Roger Miller and @Bill Florio and of course our series co-host @Rob OBrien!  

 

Q1: Building a freelance nonprofit consulting business, struggling with imposter syndrome

 

A: Imposter syndrome is common among consultants, be patient with yourself and recognize the value you bring. Join peer groups like the "solo nonprofit Salesforce consultants" channel in the Ohana Slack, where job opportunities are posted regularly. The nonprofit consultant community is unusually supportive, lean on it. 

 

Q2: Coming from Sales Cloud, how do you make Nonprofit Cloud's (AFNP) many objects understandable for end users and reportable?

 

A: The transition from standard Sales Cloud to Agentforce Nonprofit (built on the Nonprofit Cloud/Industries data model) can feel overwhelming due to the shift in object architecture. Sales Cloud relies heavily on Accounts, Contacts, Opportunities, and Leads — Nonprofit Cloud breaks these into more specialized, granular objects (PersonAccount, Program, ProgramEngagement, BenefitAssignment, GiftCommitment, GiftTransaction) to support Agentforce automation.

 

To keep this manageable for end users and effective for reporting:

  • Role-Based Lightning Apps: Don't put everyone into one "Nonprofit" app — build specialized apps (Fundraising Hub, Program Delivery, Volunteer Management). A program manager should never see fundraising/gift commitment objects, and vice versa.
  • Dynamic Forms & Pages: Hide complex, system-driven fields (used purely by Agentforce for context) from regular users; show fields conditionally only when relevant to the record's current stage.
  • Action Launcher over Related Lists: Instead of cluttering a page with 15 related lists for junction objects, use the Industries Action Launcher so users can launch a flow ("Log a Donation," "Enroll in Program") without understanding the underlying object web.
  • Standardize Custom Report Types early: Build and lock down clear custom report types (e.g., Accounts with Gift Commitments and Gift Transactions), and rename fields to friendly internal terminology so users aren't confused by standard API labels.
  • Keep Agent fields behind the scenes: Agentforce tracks intent, sentiment, next-best-action via specific fields — keep these visible only to integration/AI user profiles.
  • Feed the agent, protect the user: A human hates clicking through three objects to log a program outcome; an Agentforce agent can read/update/summarize those three objects in milliseconds. Use automated flows so users interact with a single simplified screen.

Pre-built report packs and regular office hours (especially for smaller nonprofits) help a lot here. Also check out the community-built Home knowledge base.   

 

Q3: Best uses for Cohorts in Program Management?

 

A: Yes — you generally need to build or customize your own reports to make Program Cohort useful; out-of-the-box reporting for cohorts in Program Management (PMM) is minimal. By itself, Program Cohort is a thin grouping layer — its entire out-of-the-box footprint is Name, Start Date, End Date, Status, Description, and a lookup on Program Engagement connecting it to people. It isn't a reporting object as delivered; it's a dimension you group other objects by. 

 

Q4: Where does AFNP (Agentforce for Nonprofit) still lag NPSP, and where has it surpassed it?

 

A: 

  • Address management: Both platforms have automated address management — this isn't actually a gap.
  • Community knowledge base: NPSP simply has more community-built content because it's older, not because AFNP is harder to get support for.
  • Customizable rollups and recurring donations: Both platforms have native tools for these, and both can be supplemented with DLRS if you need more.
  • Where AFNP has moved ahead: grantmaking, case management, and relationship-center functionality are notably stronger than NPSP.

Further reading: Salesforce Ben — The State of Salesforce Nonprofit Offerings in 2026.

 

Q5: A tiny nonprofit new to Salesforce (moving off Bloomerang) just signed up for AFNP — best practices for using it as a small org?

 

A: Depends on the org's attitude, buy-in, and whether they have the structure/support to maintain it long-term.

 

Best practices:

  • Leverage the Power of Us Program's 10 free Enterprise licenses if eligible.
  • Adopt Person Accounts early — AFNP uses standard Person Accounts instead of NPSP's legacy Household Accounts; standardize this from day one.
  • Start minimalist (out-of-the-box) — avoid excessive custom dev early; AFNP's built-in Fundraising, Program Management, Volunteer Management, and Grantmaking frameworks control long-term maintenance costs.
  • AFNP includes specialized AI agents like the Prospect Research Agent and Volunteer Capacity Agent — set clear parameters so small teams can automate without manual error.
  • Implement role hierarchy and permission sets — don't put everyone on the System Administrator profile; use tightly scoped sets (Fundraising Operations, Program Manager) for clean, scalable security.
  • Turn on MFA globally right away to protect donor/constituent data from day one.

Phase 2 — Data Modeling & Mapping (before importing): Small nonprofits often import spreadsheets exactly as-is — instead map columns to standard objects: Donors/Constituents → Person Account; Donations/Grants → Opportunity or the native Gift Transaction framework; Programs/Services → Program and Program Engagement; Recurring Giving → Gift Commitment.

 

Phase 3 — Out-of-the-Box Customization: Resist downloading excessive AppExchange apps or building custom code — rely on built-in tools first. Use Engagement Plans (native checklists) to standardize donor stewardship or volunteer onboarding. Use Flow Builder instead of custom code — e.g., a flow that auto-assigns an engagement plan the moment a high-tier gift transaction closes. Use the standard AFNP dashboards to track key metrics immediately without building reports from scratch.

 

One attendee's cautionary note: their ~30-person nonprofit had a rough NPSP implementation without a proper IT team — worth planning for the maintenance and definitions work up front, not just go-live.

 

Q6: Is AmpImpact still a relevant choice for an NGO, or is there something more powerful now?

 

A: Still relevant, but it's built on NPSP — so choosing it ties you to the legacy platform. Whether that matters depends on your org's size and complexity; larger/more complex orgs may be better served moving straight to AFNP. More discussion in the Nonprofit Trailblazer Community group

 

More resources:

Upcoming from the Nonprofit Community Team:

Write a comment...
0/9000