Bi-Directional Salesforce Sync

Neon Fundraise offers a bi-directional sync integration with Salesforce, so that data entered and changed in Salesforce gets synced to Neon Fundraise, in addition to Salesforce consuming Neon Fundraise data. This two-way sync ensures that data is consistent across both applications, regardless of where the data is entered or changed.

Records that can be synced from Salesforce to Neon Fundraise include opportunities and contacts. For the complete field mapping, please see "Field Mappings" below.

Installation

To take advantage of the bi-directional sync, you will first need to configure a Salesforce integration — click here for full instructions.

1. Ensure that the latest version of Neon Fundraise / Rallybound Custom Fields package is installed (version 2.4 or later). This package is available on AppExchange.
2. Install the newest version of Neon Fundraise / Rallybound Sync (version 3.1 or later).
3. Configure Salesforce in Neon Fundraise and connect it to campaigns.

Once the integration is configured, enable the bi-directional sync feature in your Salesforce instance:

1. Specify which Neon Fundraise Org to sync to:
   1. In Salesforce, enter Setup
   2. Navigate to Custom Code > Custom Settings (or search “Custom Settings”)
   3. Click Manage next to the “Sync Configuration” setting in the RallyBoundSync namespace
   4. Click Edit next to the Production record
   5. Enter your Neon Fundraise Org ID as Org Id and Save
2. Authenticate your Salesforce Org with Neon Fundraise:
   1. In Salesforce, enter Setup
   2. Navigate to Security > Named Credentials (or search “Named Credentials”)
   3. Press Edit next to the Rallybound record
   4. Ensure “Start Authentication Flow on Save” is checked
   5. Press Save
   6. Follow the flow to login to Neon Fundraise and grant access to Salesforce

FAQs

Can I turn this on for individual campaigns?

No. This is a global setting impacting all campaigns associated with the specific SF instance on the org. So if you add a Salesforce sandbox as well as Production, and enable it just for the Sandbox, it just applies to campaigns associated with the Sandbox.

Failed syncs: What happens if a sync fails and how do I attempt a resync?

Visibility is present in the logs of your Salesforce Instance (as to why it failed). There is no resync ability so they would need to make the change manually to our system (or delete and re-enter opp in SF).

Deleted records: Will deleted Opportunities in Salesforce sync to Neon Fundraise?

No, while updates to opportunities will sync, deleting an opportunity will not delete the donation record in Neon Fundraise.

Custom mapping: Are custom inbound mappings supported?

Custom mappings are not supported for inbound data at this time.

What happens if a gift is made to a recipient who exists in Salesforce but not in Neon Fundraise?

A Member ID, and a contact record, is created in Neon Fundraise. The Member ID is passed back to Salesforce.

What happens if Contact Name formats differ between Neon Fundraise and Salesforce?

The integration validates incoming data in the same way as it does creating donations in the Admin.

Note: Email address, and either First or Last Name are required. Any changes made to the Account are not synced (if the information is not the same as on the Account’s Contact, such as Company Name which resides on the Account Object). If there is a validation error that passed validation in Salesforce but did not pass validation in Neon Fundraise (e.g., Salesforce is configured to not validate or require any name on the contact), the validation error will be logged on the Sync Queue Item in the Salesforce instance.

Does Neon Fundraise provide support for Salesforce accounts?

No. Issues present within your Salesforce account must be handled by your Salesforce Admin or third party consultant.

Field Mappings

Opportunity

For NPSP Implementations

(when npsp__Primary_Contact__c is present)

For non-NPSP Implementations 

(Uses the OpportunityContactRole where IsPrimary is true)

Contact