Setting Up Salesforce NPSP

This article guides through how to connect iDonate to Salesforce NPSP, configure settings, field mapping, and managing the connection over time.

Prerequisites

Before beginning, make sure you have:

1. Access to an iDonate Admin user.
2. Admin access to your Salesforce account with NPSP installed.
3. A properly configured permission set in Salesforce.

Connecting to Salesforce

1. From within iDonate, click Settings Cog > Integrations (beta)
2. Click Salesforce from within the Marketplace - this will open the Salesforce Config Wizard.
3. Click Configure.
4. Click Connect and login to Salesforce via the login page that opened.
   
5. Once logged in, return to the Config Wizard and click Next.

Field Mapping Configuration

Use the Salesforce Field Mapping screen to define how data from iDonate maps to fields in Salesforce. This setup ensures that information from iDonate is stored in the right place within your Salesforce instance.

Adding or Editing Field Mappings

iDonate sets default field mappings, however, you can create or update field mappings as needed.

To map additional fields, click the + Add to iDonate <> Salesforce field mapper button. New  Source and Destination inputs will appear at the bottom of the field mapping list.

Understanding Source and Destination Fields

1. Source: The iDonate data field from the event payload.

   1. Enter the target field using the format [OBJECT_NAME].[FIELD_NAME].

1. Destination: The Salesforce object and field where the iDonate data will be saved.

Choose from the dropdown lists, which are organized by object. Scroll through the options to find and select your target field. 

Sync Settings

Sync Settings determine how data flows and behaves within your Salesforce integration. Review each setting carefully — they directly impact how information is processed and synced.

Designations and Processing

1. Default Designation: When a transaction occurs and does not have an associated designation, the export will use this designation when exporting to your CRM.
2. Donor Fee Processor: Determines how donor fees are processed.
3. Donor Fee Designation: Required if "Donor Fee Processor" is set to "Standard". The designation that will receive all donor fees.
4. Recurring Donation Processor: Select your recurring donation processor.
   1. Use Fiscal Year Recurring if you want iDonate to add recurring donation payments to the same Salesforce opportunity throughout a fiscal year. iDonate will create a new opportunity at the start of a fiscal year.
   2. Select NPSP Legacy or Enhanced Recurring if you want iDonate to create separate Salesforce opportunities for each recurring donation payment. You must have your Salesforce instance configured to use NPSP Legacy or Enhanced Recurring.
5. Closed Fiscal Year Adjustments: When enabled, this setting authorizes your integration to push opportunity changes to Salesforce for closed fiscal years. Enabled by default.

Opportunity Configuration

1. Opportunity Name Format: Opportunity Name Format uses customizable fields. The following is a list of recognized keywords that the integration can interpret. You must include the double brackets:
   1. , , , .
   2. The default is: , .
2. Closed Stage Flag: The name of the Stage that should be set on a recurring opportunity at the time the last payment in a fiscal year is made. Default is "Closed Won".
3. Fiscal Year Recurring: Opportunity Amount Calculation: Used for Fiscal Year Recurring Processing Only.
   1. For organizations using fiscal year recurring, select Fiscal Year Forecast if you want the Opportunity amount to be the amount forecasted for the current fiscal year AND Default Allocations Enabled is false in Salesforce; you cannot use Fiscal Year Forecast if your Salesforce instance is using Default Allocations.
   2. Select Cumulative Total if Default Allocations Enabled is true in Salesforce OR you simply want the Opportunity amount to be the running total after each installment.
4. Include Description:  When enabled, the transaction.description will be sent to your CRM's note field. Enabled by default.

Account and Contact Management

1. Use NPSP Account Record Types:
2. Use Company Accounts: When enabled and a donation includes a company name, iDonate will create an account representing the company and associate the opportunity with the company account. When false, iDonate associates all opportunities with the donor account. Disabled by default.

Data Export Options

1. Export Offline Gifts: When enabled, all offline gifts entered in iDonate will be exported to your CRM. Enabled by default.
2. Export Ticket Purchaser: When enabled, the integration exports the ticket purchaser as a contact to the CRM. Enabled by default.

Event Tickets

1. Ticket Description: The value that will appear in the description field in Salesforce on the ticket record. Defaults to Created by iDonate's integration.

Disconnecting the Integration

1. Navigate to the Integration Marketplace page and click on Salesforce
2. Click the ellipsis menu (...) next to Reconfigure and click Deactivate Integration.
   

Deactivating the integration will completely stop data from syncing to Salesforce. Before you deactivate, consider pausing the instance instead. This temporarily stops syncing without removing your existing settings. If you deactivate, all previous configuration settings will be lost.

Troubleshooting

If you run into issues with your integration:

1. Check the Logs tab on the Integrations (beta) page for specific errors.
2. Double check your Salesforce permissions are correct.
3. Contact iDonate support with log details and/or any other relevant information.