Set up export from Salesforce NPSP

In export mode, the Salesforce NPSP integration syncs data in one direction only: from Fundraise Up to Salesforce NPSP. Data in Salesforce does not sync back to Fundraise Up.

When a donation is made, Fundraise Up sends several types of records to Salesforce NPSP:

• Contacts: A unique Contact is created for each supporter.
• Accounts: Contacts are linked to Accounts based on your Salesforce settings.
• Opportunities: Each donation creates a new Opportunity record.
• Recurring Donations: Recurring plans are synced to Salesforce NPSP using its native Recurring Donation object. Daily recurring plans are not supported by this integration. Learn why →
• Campaigns: Donations are linked to Salesforce Campaigns using rules you define in your integration settings.
• Payment — Payment details (if available).

The integration offers two ways to send data to Salesforce NPSP:

Automatic sync (recommended)

• Sends donation data to Salesforce immediately after each event — for example, a new donation.
• Keeps your Salesforce records continuously updated.
• Works silently in the background.

Manual sync

• Transfers data to Salesforce only when triggered.
• Gives you control over exactly when syncing happens.
• Offers flexibility for testing configurations.
• Ideal for migrating historical data before enabling automatic sync.

Fundraise Up does not automatically remove duplicates before syncing data to Salesforce NPSP. Instead, deduplication should be handled using Salesforce's built-in tools.

Salesforce's standard Duplicate Management system works with all objects in the NPSP integration. When duplicate rules are properly configured, they will prevent duplicates of Contacts, Accounts, and other objects automatically. For example, if a duplicate Account is detected, new Contacts will be associated with the existing Account rather than creating duplicate records.

We recommend creating two duplicate rules in Salesforce — one for the Contact object and one for the Lead object. These rules use the email address synced from Fundraise Up to check for duplicates.

Sometimes, a supporter in Fundraise Up already exists in Salesforce as a Lead. When this happens, syncing from Fundraise Up will convert the Lead into a Contact.

Salesforce NPSP supports multiple currencies. Whether or not this feature is enabled affects how donation amounts from Fundraise Up appear in Salesforce:

When a new donation is received, Fundraise Up sends the full donation amount to the Salesforce Opportunity Amount field. However, if a refund occurs, the amount in Salesforce changes to reflect the payout amount rather than keeping the original donation amount.

Salesforce sets a daily limit on the number of API requests that each user or organization can make. In most cases, the number of donations you receive each day won't exceed this limit.

To view your current limit, go to Setup > Company Information in your Salesforce account.

For high-volume campaigns (like year-end fundraising), you may need to request a temporary limit increase directly from Salesforce.

Before connecting, make sure you have:

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

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 opens the Salesforce login screen.
5. Log in to your Salesforce account.
6. Once authenticated, you'll return to the integration settings in Fundraise Up.
7. In the Export (sending data to CRM) section, click Activate.
   

After activation, the integration won't start syncing until you enable it.

Once activated, click Export (sending data to CRM) section. You'll see three tabs in the Dashboard: General settings, Mapping rules, and Special rules. Start with General settings.

General settings tab

• 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 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

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:

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.

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

Mapping rules tab

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.

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 Up	Salesforce NPSP
  Object (entity): Donation	Object (entity): Contact
  Property (field): Supporter email	Property (field): email
  Value: example@example.com	Value: 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 Up	Salesforce NPSP
  Object (entity): Campaign	Object (entity): Opportunity
  Property (field): ID	Property (field): order number
  Value: 12345678	Value: 12345678

To track supporter's mailing list consent:

1. Click Add rule.
2. Select Donation as the entity and Supporter email consent as the field on the left.
3. Map to the Salesforce Contact entity on the right. Select the field that tracks communication preferences — for example, Do not contact.

Use this mapping for matching accounts with custom name templates:

1. Click Add rule.
2. Select Donation as the entity and Supporter address postal as the field on the left.
3. Map to the Account entity on the right and select Billing zip/postal code.

Mapping rule for accounts

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.

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.

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.

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.

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

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

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

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.

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.

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.

Salesforce NPSP can display the full installment schedule for each Recurring Donation, including upcoming payments. This view is available if your organization uses Enhanced Recurring Donations in Salesforce.

To enable it:

1. Open a Recurring Donation record in Salesforce.
2. Click the gear icon and select Edit Page.
3. Find the Recurring Donation Installments section in the page editor and drag it onto the layout.
4. Click Save to publish your changes.

Salesforce will then show a full schedule of expected installments based on the Recurring Donation data. Fundraise Up does not send individual installment records — the schedule is generated automatically in Salesforce.

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

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:

• Sync specific date ranges or your entire donation history.
• Update records in Salesforce after making changes in Fundraise Up.
• Test your integration settings with controlled data transfers.
• Make bulk corrections after updating mapping rules.

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.

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.

You can deactivate export to Salesforce NPSP or disconnect the integration entirely. In both cases, if the same Salesforce account is activated or reconnected later, all previously configured settings and mappings are preserved, but past data won't sync automatically.

To deactivate export:

1. Scroll to the bottom of the integration page.
2. Click Deactivate export.

This stops only the export. If you have import enabled, it continues working without interruption. Disconnecting the integration stops both export and import, and deletes all imported data.

To disconnect integration:

1. Go to Settings > Integrations and select Salesforce NPSP.
2. Click Disconnect.

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.

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