#Nonprofit42 人がディスカッション中

Hello Sean, 

From what I understand, this doesn’t sound like a universally published Salesforce policy where a customer must buy 10 additional UE licenses for an Org Swap. Historically, Org Swaps have generally been handled based on the customer’s existing licensing and commercial agreement, with the replacement org being provisioned to match the appropriate licenses. So if another nonprofit completed an Org Swap in June without this requirement, I’d definitely ask the AE/VP to point to the specific current policy or documentation that requires the additional 10 licenses. It could be a specific provisioning or commercial constraint for this particular account rather than a blanket Salesforce policy, but I’d be interested to hear if others have seen this recently. Hope this helps!

Hi Preeti, adding a late option since the thread mentioned Skyvia and 

Apps Script. 

Disclosure: I work at TwinStack, and we ended up building a free 

AppExchange app for this after hitting the same requirement on 

nonprofit projects. 

Harry's point about Apps Script is right, and that is essentially the 

approach that works when $0 is a hard requirement. The form posts 

directly to your org, so there is no middleware to pay for. The 

downside is that someone has to build and maintain the OAuth handling, 

error retries and token refresh. 

We packaged that up so admins do not have to: 

Free with no submission cap, and no third party in the data path, 

which tends to matter for nonprofits collecting client or beneficiary 

information. 

One NPSP-specific note worth knowing before you install. It captures 

submissions to its own Form Response object rather than writing 

straight to Contact. That is deliberate: household accounts and 

affiliations mean an integration that guessed where to write would 

get it wrong. You route it with a record-triggered Flow instead, which 

also means the raw submission is preserved for audit and grant 

reporting. 

Happy to help if you try it and get stuck.

Benefit schedules can be a tricky beast to get your head around in Nonprofit Cloud. The Program Management Implementation Guide is certainly worth having to hand, although practical examples can sometimes make more sense than documentation alone. The Trailhead modules covering attendance and benefit tracking should help with the fundamentals. I think the most important part is understanding how benefit schedules connect with programme participation and outcome measurement. There is a dedicated Trailhead module covering attendance and benefit tracking in Nonprofit Cloud that should address the core questions. If you are still stuck afterwards, similar Trailblazer Community discussions may also offer useful screenshots and examples.

Hey Zachary, 

Neither Campaign nor a plain custom field is the standard NPSP approach, most orgs actually assign portfolios through Contact/Account Ownership. 

Standard NPSP pattern: assign each Individual (Contact or Household Account) directly to a gift officer using the Owner field, that's the native "who owns this relationship" mechanism NPSP is built around, then build a list view or report filtered by Owner = [Gift Officer] to see each person's portfolio at a glance. This avoids cluttering records with a redundant custom field just to store who owns them. 

On top of ownership, most orgs layer in NPSP Levels (a numeric field like Total Gifts driving a Bronze/Silver/Gold/Platinum-style tier) to help prioritize within each officer's portfolio, and Engagement Plans to automate the cultivation/solicitation task cadence per donor. 

Campaigns aren't typically used for portfolio tracking itself, they're better suited for specific asks/appeals tied to a fundraising effort, not for representing an ongoing "this person belongs to this gift officer" relationship. 

If you're on newer Nonprofit Cloud (not just NPSP), there's now a dedicated Fundraising Portfolios feature purpose-built for this exact use case, worth checking if your org has access to it before building a custom solution. 

Reference:

Opportunity + Donation Record Type + a reliable First Donation flag + Scheduled Paths

is the cleanest Flow design. 

Opportunity Created 

       | 

       |-- Record Type = Donation 

       |-- Total Gifts = 1 

       | 

       +---- Immediate Path 

       |       └── Send Email #1 

       | 

       +---- Scheduled Path: 7 Days After Created Date 

       |       └── Send Email #2 

       | 

       +---- Scheduled Path: 14 Days After Created Date 

               └── Send Email #3