Our flexible native Salesforce integration will allow you to send Fundraise Up donation data to Salesforce easily, including static and custom fields and objects.
User Permissions: Please ensure that the Salesforce user you use to connect Fundraise Up has full read/write permissions including to create structures, entities, objects, and so on. When in doubt, please use a Systems Administrator-level user to connect.
Salesforce Objects Used
Fundraise Up data is sent to Salesforce's Standard and Custom Objects. You can customize field mappings to Standard Objects. Custom Objects are created automatically for recurring plans.
|Fundraise Up Object||Standard Salesforce Object|
80+ Data Points
Supported Salesforce Versions
Please note: we currently do not use the NPSP Subscriptions Object. With feedback from many organizations, we built an improved Custom Object to sync Recurring Plans
Please note: It is very that possible Fundraise Up will overwrite your existing data in Salesforce ( e.g. Contact's address ) so please configure the integration using this in mind.
When Data is Synced
- Opportunities are created or updated when a Fundraise Up Donation is created or updated
- Contacts are created or updated when a Fundraise Up Supporter is created or updated
- Campaigns are created or updated when a Fundraise Up Campaign is created or updated
- Recurring Plans are created or updated when a Fundraise Up Recurring Plans is created or updated
Contact Matching and Duplicate Management
Fundraise Up does not handle any matching or de-duplication in Salesforce. This is completely managed via Salesforce Matching and Duplicate rules.
Before we create a new Contact we ask Salesforce if the Contact already exists exist in the Salesforce database.
However, contact matching can be complicated and every organization has different criteria on how to match duplicates. We rely on Salesforce duplicate and matching rules settings to find a match.
Learn more about managing the Duplicated Matching Rules in Salesforce
We recommend you to create 2 duplicated rules for both Contact and Lead objects and associate it with Email Matching Rule.
In some cases, you may already have a potential donor represented as Lead in your Salesforce database. As with Contacts we rely on your Salesforce settings to determine how to match Leads.
If Fundraise Up finds a Lead with the same information we would use to create Contact, Fundraise Up would convert that Lead to Contact instead of creating a new Contact.
By default, Fundraise Up pre-fills the following data in your Mapping rules.
Fundraise Up Supporter Object
Salesforce Contact Object
You can change this mapping or extend your contact data with more data-points that we have available. Not all SalesForce installations will have a place for all of our data. The default fields above however are usually common in all installations.
In this example, you may want to store the contact Employer Name in one of your contact fields, if you have a field for it in SalesForce:
Every Contact in Salesforce must be associated with Account.
When we create a new Contact we always create a new Account using the contact's last name.
You can change this name in your integration settings:
Fundraise Up Supporter Object
Salesforce Account Object
Last Name Household
By default, Fundraise Up does not map campaigns because Fundraise Up does not know how your organization uses campaigns in SalesForce, if even being used at all.
In your integration mapping configuration, you can set up these rules that will search by campaign name in your SF database and create a new one if not found.
You can also use Fundraise Up's Campaign's Code or ID to map your Salesforce campaigns. In this case, we will search for the campaign with this ID in Salesforce, attach Opportunity to this campaign if found. If it is not found, we will ignore the campaign field.
When a new donation or recurring installment happens we create a new Opportunity object in Salesforce. By default we create an object with only 2 fields:
Fundraise Up Donation Object
Salesforce Opportunity Object
Fundraise Up however can pass over 40 additional data-points associated with the donation such as tribute, comment, designation, etc.
It is up to you which data points you prefer to record and where.
Opportunity Mapping with Multiple Currencies
If your Salesforce account does not have multiple currencies enabled
By default, all transactions are written to SalesForce in your Fundraise Up base currency (this is determined by and same as your Stripe account base currency). This means that if you received a €100 EURO donation in Fundraise Up, it will be recorded to Salesforce as about $120 USD (something like $119.87) since your base currency is USD.
If you have multi-currency account enabled
The default is the original transaction amount and currency. For example, one transaction may be recorded as €100 EURO and another as £100 GBP
Please check here how to enable/disable multi-currency Salesforce setting
You have the option to change the default behavior and explicitly tell Fundraise Up how to map donation amounts, ignoring your Salesforce configuration, by making overriding rules in Mapping Rules.
Custom Object "Recurring Plan" is created automatically for each recurring plan. When recurring plan changes happens ( e.g. changes in donation amounts or payment method ) those changes synced with associated "Recurring Plan" object. New installments will be added as Opportunity with link to Recurring Plan.
The Recurring Plan object contain the fields bellow.
- Fundraise Up ID
- Amount in USD ( or your Fundraise Up default account currency )
- Last Payment Date
- Next Payment Date
- Payment Method Type
- Payment Last Four
- Payment Method Expiration Date
- Tribute Type
- Tribute From
- Tribute Honoree
- Tribute Message
- Tribute Hide Amount
- Tribute Sharing
- Tribute Recipient First Name
- Tribute Recipient Last Name
- Tribute Recipient Email
- Tribute Recipient Address Line 1
- Tribute Recipient Address Line 2
- Tribute Recipient Address City
- Tribute Recipient Address Postal
- Tribute Recipient Address Region
- Tribute Recipient Address Country Code