Objects

Donations synced from Fundraise Up are written as an Opportunity object in Salesforce NPSP. Any time a new donation is synced from Fundraise Up, it’s created as a new Opportunity in Salesforce NPSP.

Supporter records from Fundraise Up are synced as Contacts objects in Salesforce. Every unique Supporter record creates a new Contact in Salesforce NPSP.

Every time a new Contact is added to Salesforce NPSP, an Account object is also created automatically.

GAUs are General Accounting Units, and the NPSP’s way of representing internally where the money received from each Opportunity should go.

Fundraise Up’s mapping tools can be used to create Opportunities that are automatically assigned to specific Salesforce Campaigns. As long as those Salesforce Campaigns are associated with the NPSP’s GAU Allocations, NPSP will automatically create the corresponding GAUs on those Opportunities.

When mapping data from the Opportunity object to the NPSP custom Payments object, we recommend using the Payment Mappings feature already built into NPSP.

The Salesforce NPSP integration uses the built-in NPSP Recurring Donation object (sometimes labeled as Recurring Plan) to sync recurring donation plans. Fundraise Up automatically creates the first opportunity (a donation) in Salesforce for each new recurring plan.

Here are some examples of exactly how this plays out in Salesforce NPSP, step-by-step: For a newly-created recurring plan with the first installment already made, it works like this:

• Fundraise Up creates a new NPSP Recurring object in Salesforce, and prevents the creation of the first pledged opportunity (that’s the first installment that has already been paid)
• Fundraise Up creates the first opportunity in Salesforce (the first donation)
• Salesforce automatically creates the second, pledged, opportunity (for the second donation)

For an existing recurring plan for which we’ve just received the second installment (as an example):

• In Salesforce, there's a Recurring object with one closed opportunity (the first donation from before) and one pledged opportunity (the incoming second donation)
• Fundraise Up removes the pledged opportunity
• Fundraise Up creates a new opportunity for the second donation
• Salesforce creates another pledged opportunity (the 3rd installment). The process then repeats for each following installment.

For a recurring plan with the first installment scheduled for a later date:

• In Salesforce, Fundraise Up creates an NPSP Recurring object and prevents the creation of the first pledged opportunity (for the delayed first donation)
• When it's time for the installment (e.g. a month later), Fundraise Up creates the first successful opportunity, and Salesforce automatically creates the second, pledged opportunity for the donation the month after.
• After that, the flow continues as in the ‘existing recurring plan’ example above.

Fundraise Up has a variety of different potential statuses for recurring plans. In Salesforce NPSP, all statuses other than ‘canceled’ are considered to be ‘active’.

When a recurring plan is updated or changed in Fundraise Up, the changes are synced to the relevant record on the Recurring Plan object in Salesforce.

Updating tab visibility for Recurring Plans

In some cases, the Recurring Plan object that Fundraise Up creates in your Salesforce NPSP instance may not be visible to some Salesforce users.

If you need to make the Recurring Plans object visible to other Salesforce users, navigate to:

Setup > Users (in the “Administration section”) > Profiles

Select the profile you want to give access to, and then in the Tab Settings section, set the Recurring Plans property to Default On. Repeat this step for other user profiles as needed.

Field history

We recommend tracking field value changes for the Amount and Status fields in Salesforce NPSP. This essentially lets you easily monitor changes to recurring plans, and be aware of upgrades, downgrades, cancellations and more.

To enable field history tracking for the Amount and Status fields, navigate to:

Setup > Objects and Fields (in the “Platforms Tools” section) > Object Manager > Recurring Plan > Fields & Relationships.

Then, select Set History Tracking. Select the options for Amount and Status. Save your changes.