Skip to content

This guide walks you through connecting Benevity to MoveData. This integration processes CSV disbursement reports and imports donation data into Salesforce.

Field Detail
Product Benevity
Method CSV file processing
Frequency Manual upload

Supported extensions#

This integration requires the Fundraising and Donations extension.

Supported file types#

MoveData supports the disbursement report from Benevity. This is the only file type supported for this integration. You can export disbursement reports from the Benevity Causes Portal.

Example disbursement file#

The table below describes the columns you will find in each row. You can download an example file to use as a test upload.

Column Description Example
Company Employer name Acme Corp
Project Benevity project or designation Community Support Programme
Donation Date Date and time of the donation 2024-12-03T12:25:03Z
Donor First Name / Last Name Donor name ("Not shared by donor" if anonymous) Sarah, Williams
Email Donor email ("Not shared by donor" if anonymous) s.williams@acmecorp.com
Address, City, State/Province, Postal Code Donor address ("Not shared by donor" if anonymous) 12 Elm Street, Bromley, Kent, BR6 0BH
Activity Sub-campaign name (may be blank) Community Fundraiser
Comment Donor comment (may be blank) Free text
Transaction ID Unique transaction identifier 61U7SRG4XK
Donation Frequency One-time or recurring One Time, Unspecified
Currency Three-letter currency code GBP
Project Remote ID Remote project reference (may be blank) Community Support 1888218 - FN00180
Source Donation source channel My Rewards, BlueSnap, Donation
Reason Donation reason User Donation, Match
Total Donation to be Acknowledged Employee donation amount 15.00
Match Amount Employer match amount (0 if none) 100.00
Cause Support Fee Platform fee 8.28
Merchant Fee Payment processing fee 2.50
Fee Comment Fee notes (may be blank) Free text

Handling your CSV file#

Always upload the original file exactly as downloaded from Benevity. Do not open or resave it in Microsoft Excel, Google Sheets, or Numbers. These applications silently reformat dates, strip leading zeros, and alter CSV encoding in ways that cause import failures.

If you need to inspect or edit specific values (for example, to adjust a currency code), use a plain text editor such as Sublime Text, Notepad++, or VS Code. Do not alter column headers, delimiters, or file encoding. Any modifications to the disbursement file are at your own risk.

Date formatting errors are the most common cause of failed imports. If MoveData reports date errors after upload, the file has almost certainly been opened in a spreadsheet application. Re-export the original file from Benevity and upload it again.

Salesforce records created#

MoveData creates different Salesforce records depending on your data model.

Benevity data Nonprofit Success Pack (NPSP) Nonprofit Cloud
Donor Contact Person Account
Employer / Company Account Account
Benevity campaign Campaign (with hierarchy) Campaign (with hierarchy)
Employee donation Opportunity Gift Transaction
Employer match Opportunity Gift Transaction
Recurring donation Recurring Donation Gift Commitment

Before you begin#

  • You need access to the MoveData app in Salesforce.
  • You need a disbursement report exported from Benevity in CSV format. Contact your Benevity administrator to obtain this file.

Setting up the integration#

Step 1: Export your disbursement report#

Contact your Benevity administrator to export a disbursement report in CSV format.

Step 2: Open the integrations tab#

In MoveData, click the Integrations tab from the main navigation.

Step 3: Create a new integration#

Click New Integration to open the integration selector.

Step 4: Select Benevity#

Choose Benevity from the list of available integrations.

Step 5: Name your integration#

Enter a descriptive name for your integration. This helps you identify it later, especially if you manage multiple Benevity uploads.

Step 6: Save the integration#

Click Save to create the integration record.

Step 7: Upload your CSV file#

Click the Upload File button and select your Benevity disbursement CSV file. MoveData processes the file automatically after upload.

After uploading, check the Notifications tab or Executions tab in MoveData to monitor processing status.

Success

MoveData uses Salesforce Flows for processing, so you can extend the integration with custom field mapping, custom object creation, or business rules through your own Flows.

How campaigns are organised#

MoveData creates a campaign hierarchy (a structured grouping of campaigns) from your Benevity data:

  • Top-level campaign: MoveData creates a campaign named "Benevity" automatically.
  • Activity-level campaigns: When the Activity field contains a value, MoveData creates a sub-campaign using that value as the name.

How employer matching works#

A single row in your CSV can generate both an employee donation and an employer match:

  • Employee donation is created when Total Donation to be Acknowledged is greater than zero.
  • Employer match is created when Match Amount is greater than zero. This creates a separate Opportunity (NPSP) or Gift Transaction (Nonprofit Cloud) record linked to the employer.

MoveData uses the Transaction ID as the unique key for employee donations. For employer matches, it appends _matched to the Transaction ID (e.g., TXN123_matched).

Migrating historical data#

You can import historical donation data through the same file upload process. Export your past disbursement reports from Benevity and upload each CSV file using the Upload File button.

Other resources#

Ask MoveData AI
Ask about setup, configuration, or troubleshooting
How can I help you with MoveData today?