The Virtuous Raise Salesforce integration automatically syncs your fundraising data with your Salesforce CRM. Use this article to connect Salesforce, map Raise objects and fields to Salesforce, configure donor matching, and understand how donors, Gifts, Recurring Gifts, and other records sync.
Table of Contents
Integration Overview
The integration supports creating and updating the following objects in Salesforce from Virtuous Raise:
- Donors
- Gifts
- Recurring Gifts
- Campaigns
- Segments
- Projects
- Premiums
The integration supports three main Salesforce configurations: Standard (basic Salesforce setup), Nonprofit Success Pack (NPSP, standard for many nonprofits), and Nonprofit Cloud (NPC, the newer industry cloud offering from Salesforce).
Setup and Connection
Note: Before you can connect Salesforce, contact the Virtuous Support team or your Customer Success Manager to enable the integration option for your organization. Until it’s enabled, Salesforce does not display under Raise Integrations.
Also, ensure you have a Salesforce account with System Administrator permissions (or at minimum, API access and permission to authorize connected apps.)
- Navigate to Settings > Integrations.
- Select Salesforce.
- Click Connect to Salesforce. Salesforce redirects you to log in and authorize Virtuous Raise.
- Once connected, your Salesforce Organization Name and ID appears at the top. Toggle Enabled to Active to start processing data.
- After connecting, configure these settings:
- Environment: Toggle between Production and Sandbox. Use Sandbox for testing purposes. Switching environments will require re-authentication with the appropriate credentials.
- Include Tests: If enabled, transactions made in Test Mode in Virtuous Raise will also be synced to Salesforce. Disable this to keep your CRM clean of test data. Click here to learn more about Test Mode.
- Re-connect: Click Reconnect to Salesforce if you need to refresh your authentication tokens or switch users.
- Then, configure your Salesforce Instance Type and all object and field mappings. Save Changes to complete the setup. Read more below on configuration and mapping.
Moving From Legacy RaiseDonors
You cannot enable the Raise <> Salesforce integration if your organization's Legacy RaiseDonors Salesforce integration is on. This restriction prevents Gifts from syncing twice. The Enabled toggle will remain disabled in Raise with a warning until your integration with Legacy RaiseDonors is turned off. If you reconnect to a Production Environment while the Legacy integration is on, Virtuous Raise turns the sync off automatically.
The Raise integration writes one Opportunity per Gift, whereas Legacy RaiseDonors wrote one Opportunity per fund. For Gifts split across multiple funds, the split is stored on allocation records (NPSP) or Gift Designations (Nonprofit Cloud) under that single Opportunity. Single-fund Gifts are treated the same as the Legacy sync.
To move from the Legacy RaiseDonors integration to the Raise integration, contact the Virtuous support team.
Configuration
Virtuous Raise attempts to detect your Salesforce Instance Type (NPSP, Nonprofit Cloud, or Standard) automatically based on your installed packages. If you prefer to manually configure your instance type instead, use the dropdown to select the type.
Field Mapping
These settings control how Accounts are created when a new donor is synced to Salesforce.
- Household Account Record Type and Account Type: Used for individual donors.
- Organization Account Record Type and Account Type: Used when the donor is an Organization.
- Opportunity Contact Role: The role assigned to the Contact on an Opportunity (e.g., "Donor").
Object Mapping
After you configure your Account Type, Account Record Type, and Opportunity Contact Role mapping, map Virtuous Raise objects to Salesforce objects. If an object is not mapped (e.g., if Recurring Gift is left blank), those records will not be synced.
For each object, you can map specific Salesforce fields using Standard Fields or to Custom Fields in Salesforce, if enabled in your Raise Custom Field Settings. The Salesforce field options are filtered to types compatible with the Raise Custom Field. The objects to map include:
-
Donor: Donors are typically mapped to Contacts or Accounts. If mapping to Contacts, Raise first looks for an existing donor using external ID (CRM Key). If the donor is not found, it searches by Email, FirstName, LastName, and Phone. This is the default matching behavior, but you can change it. See Advanced Donor Matching Settings below. If mapping to Accounts, the system tries to find an existing Account by Name. If creating a new donor, it will create and link an Account.
- NPSP Note: The integration often relies on NPSP’s native triggers to create Household accounts for individuals, avoiding duplicate account creation logic.
- Contact Methods: Emails and Phones are mapped to standard fields (Email, Phone), while others can be mapped to custom fields (e.g., WorkEmail__c).
- Gift: The integration syncs Gifts after first syncing the donor record. The Gift is linked to the donor (Contact) and Account and creates an Opportunity Contact Role to link the Contact to the Opportunity. Gifts are linked to Salesforce Campaigns based on the Virtuous Raise Segment and Campaign mapping. The integration updates refunded Gifts in Salesforce (typically changing the StageName to Refunded). Form Name and Internal Form Name can be mapped to text fields in Salesforce.
- Recurring Gift: For NPSP, Recurring Gift schedules map to npe03__Recurring_Donation__c. When a new Recurring Gift is created, the sync checks for existing Recurring donations. All subsequent installments are linked to this Recurring Donation object. For Nonprofit Cloud, Recurring Gift schedules are mapped to GiftCommitment. The GiftCommitmentSchedule field is synced to define frequency and amount. Payments are linked to the schedule via GiftTransaction. Form Name and Internal Form Name can be mapped to text fields in Salesforce.
- Campaign and Segment: Virtuous Raise Campaigns and Segments can be synced to Salesforce Campaigns. A hierarchy is often established where the Segment in Virtuous Raise links to a Parent Campaign in Salesforce.
- Premium: Premiums map to Products (Product2) in Salesforce. When a Gift includes a Premium, the sync creates an OpportunityLineItem linking the Opportunity to the Product. This ensures the Product exists and uses the Standard Price Book.
- Project: For NPSP, Projects typically map to General Accounting Units (GAU). Allocations are synced to npsp__Allocation__c. For Nonprofit Cloud, allocations map to GiftTransactionDesignation. For any Gift with Project splits, the sync will update, create, or delete allocations in Salesforce to match the split in Virtuous Raise.
Each Donor, Gift, and Recurring Gift mapping can set fixed values on Salesforce fields. For example, you can set the same Lead Source value on every synced Donor. Fixed values apply when Raise creates and updates records. You can't use fields that Virtuous Raise manages itself.
If your mappings differ from the recommended best practices for your instance type (for example, NPSP), a notification displays. Select Apply Recommendations to configure standard object and field mappings for your setup automatically. Apply Recommendations is recommended for new integration setups.
Advanced Donor Matching Settings
You are able to control how Raise finds an existing Salesforce Contact for a donor before creating a new one. However, changing these settings can create duplicate Contacts or match donors to the wrong Contact. To view or modify the matching criteria, expand the Advanced accordion.
Under Donor matching, adjust the following settings:
- Fields that must all match: Select the checkboxes for Email, First name, Last name, and Phone. All four are selected by default. You can't select Phone alone.
- Other Contact email fields to check: Select additional email-type Contact fields, such as a work email, for Virtuous Raise to check along with the standard Email field. This setting applies only when Email is a match field.
- Match on the Legacy RaiseDonors donor ID: Toggle this setting on to match on your Legacy RaiseDonors donor ID. It is off by default. Use it only if you have confirmed that your Legacy donor ID equals your Virtuous Raise donor ID.