Set up the Salesforce NPSP integration

Learn how to connect, configure, and maintain your Salesforce NPSP integration.

This article walks through how to connect Fundraise Up to Salesforce NPSP, configure sync settings and mapping rules, and manage the integration over time.

This documentation covers the Salesforce NPSP integration. If you're using standard Salesforce or Nonprofit Cloud, follow the articles for those integrations instead.

Connect your accounts

 
Link copied

Before connecting, make sure you have:

  • Administrative access to your Salesforce account with NPSP fully installed.
  • Organization Administrator role in Fundraise Up.
  • The required minimum permissions configured in Salesforce.

Connection steps

 
Link copied
  1. In the Fundraise Up Dashboard, go to Settings > Integrations.
  2. Click Add integration.
  3. Select Salesforce NPSP from the options.

  4. Click Connect Salesforce — this will open the Salesforce login screen.
  5. Log in to your Salesforce account.
  6. Once authenticated, you'll return to the integration settings in Fundraise Up.

After connecting, the integration won't start syncing until you enable it. To start syncing new donations, scroll to the bottom of the integration settings page and click either Enable automatic sync or Start manual sync.

Connecting to a Salesforce sandbox will not overwrite or affect your existing production Salesforce connection. You can have multiple Salesforce NPSP integrations connected simultaneously. Each integration will appear separately in your Dashboard, allowing you to manage production and sandbox environments independently.

Configure general settings

 
Link copied

Once connected, you'll see three tabs in the Dashboard: General settings, Mapping rules, and Special rules. Start with General settings.

General settings tab

Sync options

 
Link copied
  • Sync test data: Check this checkbox to send test mode donations to Salesforce NPSP. Use this to test that your mapping rules work correctly before going live.
  • Sync subaccounts: Only appears in parent account settings. When checked, data from subaccounts will be synced to Salesforce even if those subaccounts don't have their own Salesforce connection. Use this for tracking donations if your organization has a chapter-based model.
  • Create an account if a donation is made on behalf of an organization: When a donation is made on behalf of an organization, an account will be created in Salesforce using the name provided in the “on behalf of” field.
  • Automatically remove pledged opportunities if NPSP creates them: If NPSP auto-generates pledged opportunities, enabling this setting will remove them. Has no effect if auto-generation is disabled in NPSP.

Opportunity settings

 
Link copied
  • Opportunity name: Customize how Opportunities (donations) are named in Salesforce using variables from the donation data.
  • Opportunity stages: Map Fundraise Up's donation statuses to Salesforce Opportunity stages. You can use the drop-down menus to choose how they'll appear in Salesforce, or use our default options. Supported statuses:
    • Succeeded
    • Scheduled
    • Pending
    • Retrying
    • Refunded
    • Failed
    • Disputed
When a donation is refunded, all mapped fields are updated in Salesforce. The status is set to Refunded and the amount is adjusted automatically.

Recurring donation statuses

 
Link copied

Control how recurring donation statuses appear in Salesforce NPSP. By default, Fundraise Up maps statuses to NPSP's standard recurring donation stages, but you can customize these mappings using the drop-down menus.

Default status mappings:

Fundraise UpSalesforce NPSP
ActiveActive
ScheduledActive
RetryingPaused
CompletedClosed
FailedFailing
CanceledLapsed
The Paused status is available only in Salesforce NPSP. Fundraise Up doesn’t send it, because NPSP applies this status internally to recurring gifts managed directly in the CRM.

Whenever a recurring plan is updated in Fundraise Up — for example, if the supporter changes the donation amount or pauses the plan — those changes are automatically synced to the corresponding Recurring Donation record in Salesforce.

Set up mapping rules

 
Link copied

Mapping rules determine which data fields from Fundraise Up get sent to which fields in Salesforce NPSP.

Mapping rules tab

Default mappings

 
Link copied

Fundraise Up includes predefined mappings to get you started quickly, but you can remove or modify those rules as needed. Predefined mappings cover essential fields like:

  • Donation data to Opportunity data.
  • Recurring plan details to NPSP's recurring donation field.

Adding custom mappings

 
Link copied

To add a mapping:

  1. Scroll to the bottom of the mapping rules table.
  2. Click Add rule.
  3. Select the Fundraise Up object (entity) and property (field) on the left.
  4. Select the corresponding Salesforce entity and field on the right.
  5. Save your changes.

Here are some examples of possible mapping rules:

  • Linking the "supporter email" field from the Donation object in Fundraise Up to the "email" property of the Contact object in Salesforce NPSP.
    Fundraise UpSalesforce NPSP
    Object (entity): DonationObject (entity): Contact
    Property (field): Supporter emailProperty (field): email
    Value: example@example.comValue: example@example.com
  • Linking the "ID" field from the Campaign object in Fundraise Up to the "order number" property of the Opportunity object in Salesforce NPSP.
    Fundraise UpSalesforce NPSP
    Object (entity): CampaignObject (entity): Opportunity
    Property (field): IDProperty (field): order number
    Value: 12345678Value: 12345678
Custom field sync behavior
When you update a custom field on an installment record in Fundraise Up, it only syncs to Salesforce automatically if that field is included in your mapping rules. If the field isn't mapped, no sync is triggered. To reflect the change in Salesforce, you'll need to run a manual sync.

General Accounting Units (GAUs)

 
Link copied

In Salesforce NPSP, General Accounting Units (GAUs) help track where donation money should go — for example, to a specific fund, program, or purpose.

If you use Fundraise Up’s integration to assign donations to Salesforce Campaigns, and those Campaigns are already linked to GAUs in NPSP, then NPSP will automatically apply those GAUs to the donation records (Opportunities) created from Fundraise Up.

Payment Mappings

 
Link copied

To map data from Opportunities to NPSP’s custom Payments object, we recommend using NPSP’s built-in Payment Mappings feature. It’s the standard way to connect Opportunities and Payments, and ensures everything works as expected.

Configure special rules

 
Link copied

The Special rules tab lets you set conditions for how data is synced between Fundraise Up and Salesforce NPSP. These special rules use "if/then" logic: If X happens in Fundraise Up, map the value as Y in Salesforce.

  • Example 1: If Campaign equals "Christmas 2025" → set Salesforce Campaign to "End of Year Giving".
  • Example 2: If Designation equals "Education" → set Salesforce Campaign to "Education Fund".

To add a special rule:

  1. Go to the Special rules tab.

    Special rules tab

  2. Click Add Rule.
  3. Choose the Fundraise Up condition (IF) next to the Fundraise Up logo.
  4. Set the Salesforce mapping result (THEN) next to the Salesforce logo.
  5. Save your changes.

Salesforce NPSP objects

 
Link copied

Fundraise Up syncs data to several objects in your Salesforce NPSP instance. This section covers the main objects used for syncing: Opportunities, Contacts, Accounts, and Recurring Donations.

Opportunities

 
Link copied

Donations from Fundraise Up appear as Opportunities in Salesforce NPSP. Each donation creates a new Opportunity record.

Contacts

 
Link copied

Each supporter becomes a Contact in Salesforce NPSP. If the same person donates again, the existing Contact is reused.

Accounts

 
Link copied

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

Recurring Donations

 
Link copied

The Salesforce NPSP integration uses the built-in Recurring Donation object (also called Recurring Plan) to sync recurring plans from Fundraise Up.

When a recurring plan is created in Fundraise Up, it syncs to Salesforce as a Recurring Donation record. Fundraise Up then creates actual donation records as Opportunities. Meanwhile, Salesforce handles the creation of pledged Opportunities — placeholders for future donations — unless Fundraise Up replaces them.

Updates to the recurring plan, like amount changes or cancellations, are also synced.

How recurring donations behave in NPSP

 
Link copied

Depending on when the first donation occurs and whether the plan is new or ongoing, the integration handles recurring donations in a few different ways. Below are the most common scenarios and what you can expect to happen in Salesforce.

1. New recurring plan — first donation already made

  • Fundraise Up creates a Recurring Donation record in Salesforce.
  • Fundraise Up prevents Salesforce from creating a pledged Opportunity for the first installment (since it’s already paid).
  • Fundraise Up creates the first Opportunity as a closed donation.
  • Salesforce automatically creates a pledged Opportunity for the next installment.

2. Ongoing recurring plan — new donation received

  • Salesforce contains a Recurring Donation with:
    • One closed Opportunity (first donation)
    • One pledged Opportunity (next donation)
  • Fundraise Up removes the pledged Opportunity.
  • Fundraise Up creates a new Opportunity for the received donation.
  • Salesforce generates a new pledged Opportunity for the next cycle.

3. New recurring plan — first donation is scheduled for later

  • Fundraise Up creates the Recurring Donation record in Salesforce.
  • Fundraise Up prevents creation of a pledged Opportunity for the not-yet-made first donation.
  • When the first donation happens, Fundraise Up creates a closed Opportunity.
  • Salesforce then creates a pledged Opportunity for the next installment.
  • The process continues as with ongoing plans.

Making the Recurring Donation object visible

 
Link copied

By default, some Salesforce users might not have access to view the Recurring Donation object.

To make it visible:

  1. In Salesforce, go to Setup.
  2. In the Quick Find box, type Profiles, then select Profiles from the results.
  3. Select the profile you want to update and click Edit.
  4. In the Custom Tab Settings section, set Recurring Donations to Default On.
  5. Save your changes.
  6. Repeat these steps for other profiles if needed.

Managing your integration

 
Link copied

After completing your setup, choose how you want data to sync — automatically or manually. Once configured, your Salesforce NPSP integration works without further maintenance.

Sync settings

 
Link copied

Find sync controls at the bottom of the Salesforce NPSP integration page in your Dashboard. These settings determine how and when data is transferred to Salesforce.

Sync options

Automatic sync (recommended)

  • By default, automatic sync is disabled when you first connect to let you configure settings before data transfers begin.
  • Enable this option once your settings and mapping rules are finalized.
  • New donations will sync to Salesforce NPSP in real time.
  • We recommend using automatic sync for most organizations.

Manual sync

Use manual sync when you need more control over when data transfers:

Integration status

 
Link copied

Your integration status appears in the top-right corner of the integration page:

  • Activated: The integration is connected and syncing data according to your settings.
  • Paused: Syncing has been temporarily stopped by an administrator.
  • Disconnected: The integration is disconnected and needs to be reconnected.

Sync log

 
Link copied

The sync log provides a record of sync activity and status for each attempt.

To access the sync log:

  1. Scroll to the Synced donations section.

    Synced donations section

  2. Review the history of sync attempts, their status, and any error messages.

Each entry shows:

  • When the sync occurred.
  • Which records were processed.
  • Success or failure status.
  • Button to resync individual records if needed.

If errors occur, the log provides details to help troubleshoot the issue.

Disconnecting the integration

 
Link copied

The Salesforce NPSP integration can be disconnected at any time. If the same Salesforce account is reconnected later, all previously configured settings and mappings are preserved.

To disconnect:

  1. Scroll to the bottom of the integration page.
  2. Click Disconnect.
Disconnecting stops all data syncing. Reconnecting keeps your previous settings, but past data won't sync automatically.

Troubleshooting

 
Link copied

If you encounter issues with your Salesforce NPSP integration:

  • Check the sync log for specific error messages.
  • Verify your Salesforce duplicate rules are configured correctly.
  • Check if you've reached your Salesforce API limits.
  • Learn how your campaigns work with Salesforce NPSP.

For persistent issues, contact Fundraise Up support with your sync log details.

 

In this article