CRM and platform integrations

Fundraise Up supports native integrations with these platforms:

• Bloomerang
• Bonterra EveryAction
• DonorPerfect
• Double the Donation Matching
• HubSpot CRM
• Kindful
• Microsoft Dynamics 365 F&E
• Neon CRM
• Raiser's Edge NXT
• Salesforce
• Salesforce Education Cloud
• Salesforce Nonprofit Cloud
• Salesforce NPSP
• Virtuous CRM (basic integration)
• Virtuous G&C Import Write
• Zapier

When someone makes a donation through Fundraise Up, the integration creates or updates records in your CRM. If a supporter already exists in your CRM, the integration updates their record with the new donation. If they're new, the integration creates a contact record and links the donation to it.

Data flows one way: from Fundraise Up to your CRM. Your CRM doesn't send data back to Fundraise Up. Two integrations work differently — Salesforce NPSP and Virtuous G&C Import Write can sync data in both directions.

The integration runs continuously in the background. You don't need to remember to export files or trigger manual syncs, though you can resync specific records manually if needed.

To view integrations, go to Settings > Integrations in your Dashboard. Only Organization Administrators can see this section and add integrations. This permission restriction exists because integrations connect to sensitive systems and can modify records in your CRM.

If you need access but don't see the Integrations option, ask your Organization Administrator to either grant you administrator permissions or set up the integration for you.

When you add an integration, automatic syncing is turned off by default. This gives you time to configure how data should map between Fundraise Up and your CRM before any records sync.

To connect an integration:

1. Go to Settings > Integrations.
2. Click Add integration.
3. Select the platform you want to connect.
4. Follow the authentication steps for your platform.

Most integrations use OAuth, which means you'll log in to your CRM and authorize Fundraise Up to access it. Some integrations require an API key instead — you'll generate this in your CRM and paste it into Fundraise Up.

We recommend connecting integrations through a dedicated service account rather than your personal account. Service accounts are user accounts created specifically for integrations and automated processes.

If you connect an integration through your personal account and that account gets deleted or has its permissions changed, the integration stops working. Service accounts avoid this problem because they exist independently of individual staff members.

Service accounts also let you set precise permissions. You can give the account only the access the integration needs, rather than the broader permissions your personal account might have.

You can connect to multiple instances of the same platform. This is useful when you have a sandbox environment for testing and a production environment for live data. You can set up one integration pointing to your sandbox and another pointing to production.

Four integrations allow only one connection total:

• DonorPerfect
• Double the Donation
• Virtuous CRM (basic integration)
• Zapier

You can connect Fundraise Up to multiple accounts within the same CRM platform. For example, you might connect to both your production Salesforce account and your Salesforce sandbox account. However, each CRM account can only be connected to one Fundraise Up account. If you've already connected your Salesforce sandbox to Fundraise Up, you can't connect it again to a different Fundraise Up account. HubSpot is the exception — the same HubSpot account can be connected to Fundraise Up multiple times.

After connecting an integration, you'll configure how data maps between Fundraise Up and your CRM. This happens in the integration's settings in your Dashboard, while automatic sync is still turned off.

Data mapping tells the integration where each piece of information from Fundraise Up should go in your CRM. You're creating a set of rules that say "take this field from Fundraise Up and put it in that field in my CRM."

For example, you might map the supporter's email address from a Fundraise Up donation to the email field on a Salesforce contact. The integration reads the email from the donation and writes it to the contact's email field.

Mapping connects four pieces of information:

• The object in Fundraise Up (such as Donation or Campaign)
• The property in that object (such as Supporter email or Campaign ID)
• The object in your CRM (such as Contact or Opportunity)
• The property in that object (such as email or campaign name)

Here's what a basic mapping looks like:

This mapping takes the email address from each donation and writes it to the email field on the contact record the integration creates or updates.

Some integrations create default mappings for you. These cover the most common field connections organizations need. You can modify these default mappings or remove them entirely if your organization uses different fields.

Some integrations support special rules (also called conditional mapping in other systems). Instead of always mapping a value the same way, you can set rules that map values differently based on conditions.

For example, you might use different campaign names in your CRM than you use in Fundraise Up. You could create a special rule that says "when the Campaign in Fundraise Up equals 'Shelter,' set the campaign in Salesforce to 'Animal Shelter Fund.'"

Special rules use if/then logic:

• If campaign equals "Shelter" in Fundraise Up, then set the campaign in Salesforce to "Shelter Fund."
• If designation equals "Areas of Greatest Need" in Fundraise Up, then set the campaign in Salesforce to "General Donations."

When multiple special rules could apply to the same donation, the integration uses the rule that was added most recently. In other words, if there are conflicting rules, the one that is lower in the list of special rules will take precedence and be applied to the donation.

Not all integrations support custom mapping. Some integrations let you control which fields sync and where they go. Others sync specific fields automatically without configuration options.

See the documentation article for your specific integration to learn which mapping options are available.

Organizations using subaccounts in Fundraise Up can set up one integration at the primary account level and enable subaccount syncing. When you enable this option, donation data from all subaccounts flows to your CRM through that single integration.

This works well for chapter-based or federated nonprofits where each subaccount represents a local chapter, but you want centralized reporting in one CRM

Before you enable automatic syncing, test your integration with test transactions. This lets you verify that data maps correctly and appears in the right places in your CRM.

To test your integration:

1. Go to your integration settings.
2. Enable Sync test data.
3. Create test donations in Fundraise Up using test mode.
4. Check your CRM to verify the data appears correctly.

Test mode donations are clearly marked as test transactions, so they won't mix with your live donation data. Once you've confirmed everything works correctly, disable test data syncing and enable automatic sync for live donations.

Integrations offer both automatic and manual sync options. Most organizations use automatic sync once their integration is configured, but manual sync gives you control when you need it.

Automatic sync runs continuously. When a donation comes through Fundraise Up, the integration sends it to your CRM within minutes.

Manual sync lets you resync specific donations on demand. This is useful in several situations:

• You need to resync donations that failed due to a temporary error in your CRM.
• You made changes to your mapping rules and want to update existing records.
• You prefer to sync donations on a schedule you control rather than automatically.

When you trigger a manual sync, you choose which donations to sync:

• Unsynced live donations includes donations that encountered errors during sync and donations that haven't been synchronized yet. This is the most common option when you're fixing sync failures.
• All live donations resyncs every live donation, regardless of whether it already synced successfully. Use this carefully — resyncing large numbers of donations can create duplicate records if your CRM doesn't handle duplicate prevention well.
• All test donations syncs test transactions. Use this when you're testing mapping rules or troubleshooting integration issues in a sandbox environment.

You can narrow your manual sync to a specific date range. If you only need to resync donations from a particular week, specify those dates rather than syncing everything. This reduces the load on both Fundraise Up and your CRM.

The sync log shows you which donations have synced successfully and which encountered errors. Each integration has its own sync log on its settings page.

To access it, select your integration from Settings > Integrations and scroll to Synced donations.

The sync log displays donations and recurring plans in a list. Each entry shows:

• The donation or plan ID
• Current sync status (synced or failed)
• Key donation details

Click any entry to expand it and see the sync history. You'll see each sync attempt with a timestamp and result.

By default, the log shows only failed syncs. This filtered view helps you focus on donations that need attention. Uncheck Only unsynced to see all sync attempts, including successful ones.

When a sync fails, the integration stores the error message from your CRM. Click the failed sync event to see the full error text. These messages typically explain what went wrong — a required field was missing, a value didn't match an expected format, or the CRM couldn't find a record it needed.

Click the copy button to copy the error message. You can paste it into a support ticket or share it with your CRM administrator.

For one-time donations that failed to sync, click Resync next to the donation to try syncing it again. This is useful after you've fixed whatever caused the failure.

Use the search bar at the top of the sync log to find donations by ID. This helps when a supporter contacts you about a missing donation in your CRM, or when you're investigating specific sync issues.

Check the sync log regularly — we recommend reviewing it at least weekly. Regular monitoring helps you catch sync failures before they accumulate. This ensures your CRM data stays current.Retry

You can disconnect an integration from its settings page at any time. Disconnecting stops all syncing immediately.

If you reconnect the same integration using the same credentials, your mapping rules and settings are preserved. You won't need to reconfigure everything from scratch.

Disconnecting doesn't delete any records that already synced to your CRM. Those records remain in your CRM unchanged.

Fundraise Up sends two types of emails about integrations to Organization Administrators:

• Sync reports.
• Critical error alerts.

All users with the Organization Administrator role receive integration emails by default. Each administrator can set their own preferences for sync report frequency (daily or weekly) and can disable either type of email.

If a subaccount has no Organization Administrators, emails are sent to administrators of the parent organization who have integration notifications enabled.

Sync reports summarize successful and failed syncs between Fundraise Up and your CRM. These reports are available for all integrations except Zapier and Double the Donation.

Each report includes:

• Total successful and failed syncs.
• Specific error messages for each failed donation explaining whether you need to resync from your Dashboard or fix a configuration issue in your CRM.
• API rate limit information for Bonterra EveryAction and Virtuous CRM, showing when limits were hit and when normal sync speed resumed.

Information is grouped by CRM if you have multiple integrations.

These emails are sent from hello@fundraiseup.com. To set your report frequency, go to Settings > Notifications > Summary reports. You can choose daily or weekly delivery. Each administrator can choose their own frequency. For example, someone managing finances might want daily reports to catch issues immediately, while someone in operations might prefer weekly summaries.

Reports stop automatically when you disconnect an integration.

Critical error alerts notify you when your integration stops working. When the token connecting Fundraise Up to your CRM is revoked or expires, you'll receive an email titled [Integration name] integration has been disconnected. The email explains that the token has been revoked and your integration has stopped syncing. You need to reconnect the integration to restore syncing.

These emails are sent from support@fundraiseup.com. The system sends one email per error type every 24 hours. Emails are sent 24/7 regardless of your organization's time zone.

To manage critical error alerts, go to Settings > Notifications > System issues and adjust the Integrations issue checkbox.