This guide walks you through connecting Big Give to MoveData. Big Give is a UK match-funding platform, best known for the Christmas Challenge, where donations to a campaign are matched by champions and pledgers. MoveData processes Big Give's Campaign Donations CSV export and imports donations and donor contact details into Salesforce.

Supported extensions#

This integration requires the Fundraising and Donations extension.

Supported file types#

MoveData supports the Campaign Donations export from Big Give. This is the only file type supported for this integration.

Big Give writes that export from two places, and the difference matters more than the name suggests:

Both exports have the same 22 columns. They differ in which of those columns Big Give fills in.

Columns in the Campaign Donations export#

There is no campaign column. The campaign is the report you asked Big Give for, not a field inside it, which is why every Big Give donation lands under a single campaign in Salesforce—see How campaigns are organised.

Handling your CSV file#

Always upload the original file exactly as downloaded from Big Give. 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 the file, 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 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 Campaign Donations report from Big Give and upload it again.

Salesforce records created#

MoveData creates different Salesforce records depending on your data model.

All amounts are imported in pounds sterling. The export carries no currency column and Big Give is a UK platform, so MoveData records every donation as GBP.

Before you begin#

You need access to the MoveData app in Salesforce. You also need a Campaign Donations CSV export from Big Give. Download it from your Big Give charity account; there is nothing to configure on the Big Give side.

Setting up the integration#

Step 1: Export your Campaign Donations report#

In Big Give, open the campaign you want to import and download its Campaign Donations report in CSV format.

Note which list you opened the campaign from, Big Give Campaigns or My Campaigns. That decides whether you need to set a donation date in Step 4.

Step 2: Open the Integrations tab#

In the MoveData app in Salesforce, click the Integrations tab in the navigation bar.

Step 3: Create a new integration#

Click New Integration and select Big Give from the list of available platforms.

Step 4: Name the integration and set the Donation Date#

Enter a descriptive name for this integration, for example "Big Give - Christmas Challenge".

If the file you are about to upload came from My Campaigns, set Donation Date to the date you want those donations recorded on. If it came from Big Give Campaigns, leave it empty: the file carries its own dates and MoveData uses those.

Leave Key prefix, under Advanced Settings, empty unless MoveData support asks you to set it.

Click Save.

Step 5: Upload your CSV file#

Click Upload File on the integration record and select the Campaign Donations CSV you exported in Step 1. MoveData begins processing the file automatically.

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

Setting the Donation Date#

Big Give records a date against each donation in a matched campaign and no date at all against donations in your own campaigns. The Donation Date on the integration fills that gap: when a row has no date of its own, MoveData dates it with whatever Donation Date the integration is carrying at the time of upload.

Two consequences are worth knowing before your first upload.

A My Campaigns export uploaded with no Donation Date set fails rather than guessing. You will see:

This export has no Donation DateTime, which is how Big Give exports a Regular Campaign. Set the Donation Date on the Big Give integration and upload the file again.

And if you are uploading several My Campaigns exports in one sitting, change the Donation Date between files. The setting applies to the upload, not to the file, so leaving it on the first campaign's date would record the second campaign's donations on that same day.

A file that carries its own dates ignores the setting entirely, so you can leave an old date sitting there without affecting Big Give Campaigns uploads. MoveData records which of the two sources each donation's date came from, so support can answer a question about a past upload without asking you for the file again.

How campaigns are organised#

MoveData creates one campaign named Big Give and hangs every imported donation off it, whichever report the donation came from. The export has no campaign column to build a hierarchy from.

If you want to report on a single Big Give campaign separately, use the donation dates or a Salesforce report filter rather than expecting a campaign per Big Give campaign.

How donations are processed#

Fees. MoveData records the fee the donor sees: the admin fee plus the VAT charged on it, as a single platform fee.

Match funding. Champion and pledge match amounts are stored on the donor's own donation rather than as separate donations, because the export names neither the champion nor the pledger. Both amounts are kept independently, and a donation commonly carries both.

Anonymous donations. A row flagged as anonymous creates a donation with no contact or person account attached. Big Give writes the literal last name Anonymous on these rows; MoveData does not turn that into a contact.

Gift Aid. Where the donor declared Gift Aid, the Gift Aid amount is imported with the donation. Where Big Give has already claimed the Gift Aid itself, MoveData also records the date of that claim, which marks the donation as one you must keep out of your own Gift Aid claim. This is the same signal MoveData sets for JustGiving donations that JustGiving has claimed.

Communication preferences. A donor who opted in is recorded as opted in. A donor who did not is left unset rather than recorded as a refusal, so a Big Give upload cannot withdraw a consent you captured somewhere else.

Common upload errors#

Migrating historical data#

You can import past donations through the same upload process. Export each campaign's Campaign Donations report from Big Give and upload the files one at a time, remembering to set the Donation Date for any that came from My Campaigns.

Other resources#

• Big Give — Big Give's main website
• Big Give for charities — campaign participation and match funding details
• MoveData Support — for setup assistance and technical support

Related articles#

• Reading and Understanding Error Messages
• How to Reprocess Failed Notifications
• Duplicate Rules