NPSP Data Importer rules
Where the feed goes
Open the NPSP Data Importer in Salesforce, choose the CSV and map its columns to the importer's fields. The importer can do a dry run that checks the rows without importing them. Run it first, on a few records, and try the whole thing in a sandbox before your live org.
Common errors and their fixes
Gifts attach to the wrong donor, or to nobody
Cause: Donation Donor is a keyword: Contact1 for a person or household, Account1 for an organization. A donor's name typed there matches nothing. Contact2 and Account2 can't be the donor.
Fix: Use Contact1 or Account1 on every row, and put the donor's details in the Contact1 or Account1 columns.
Duplicate contacts after the import
Cause: The importer matches contacts on first name, last name, email or a legacy ID. A donor spelled differently, or with a different email, on two rows can become two contacts.
Fix: Spell each donor the same way on every row and clean the file first. The duplicate rows guide shows how to find near-repeats.
A donor with several gifts
Cause: Each row holds one gift. Putting two gifts on one row, or leaving the donor blank on the second row, doesn't work.
Fix: Repeat the Contact1 details on a new row for each further gift, with that gift's own amount and date.
Organization gifts landing on a person
Cause: A gift from a company, foundation or church needs Donation Donor set to Account1 and the name in Account1 Name. With Contact1, the gift goes to a person.
Fix: Set Donation Donor to Account1 and fill in Account1 Name for organization gifts. Leave the Contact1 columns blank.
Dates read the wrong way round
Cause: Dates follow your Salesforce locale: month/day/year, day/month/year or year/month/day. 03/04/2026 is March 4 in one and April 3 in another, and Excel changes dates when it saves a CSV.
Fix: Write the date in your org's order, and check a few after importing. See dates changing in CSV files.
Amounts with symbols
Cause: Donation Amount is a currency value. $1,250.00 can be read as text.
Fix: Write 1250.00 with no symbol or commas. The currency symbols guide shows how to clean a column.
Record type or stage not recognised
Cause: Donation Record Type Name is one of Donation, Grant, In-Kind Gift, Major Gift, Matching Gift or Membership. Donation Stage defaults to Closed Won, and any other stage must be written as it is in your org.
Fix: Leave the stage blank for completed gifts, and copy record type and stage names from Salesforce.
Campaign names that don't match
Cause: A campaign name must match a campaign in Salesforce exactly. A different spelling, extra space or old name doesn't match it.
Fix: Copy the campaign names from Salesforce instead of retyping them, and trim spaces.
Preferred email or tribute values rejected
Cause: Preferred Email is Personal, Work or Alternate, and the tribute type is Honor or Memorial. Anything else isn't a value in the list.
Fix: Use those words exactly, and only for the email column that has an address in it.
Columns that don't map
Cause: The template's headers match the importer's staging field labels. Other objects need Advanced Mapping, and a header you've renamed or invented doesn't map to anything.
Fix: Keep the headers as they are, and delete columns you don't need before a real import.
ZIP codes and phone numbers changed
Cause: Spreadsheets drop the leading zero from ZIP codes such as 02134, and long reference numbers can turn into scientific notation.
Fix: Format those columns as text before pasting. See leading zeros in CSV files.
The file won't read at all
Cause: In a CSV, a value with a comma (an address, a description) must be in double quotes, and a quote inside one is written twice.
Fix: Save from a spreadsheet as CSV rather than writing the file by hand. See commas in CSV files.
After importing
After a dry run, check that each row shows as validated and that donors were matched or created as you expected. Fix problem rows in your file and upload again, rather than editing records in Salesforce.
Clean and de-duplicate the file before importing, because merging duplicate contacts afterwards is much more work than avoiding them.
Checklist before you import
Collecting gifts from several events or offices?
Send each location a form instead of a spreadsheet. The Salesforce NPSP donations template uses the importer's column headers, takes the donor keyword and record type only from their lists, and checks amounts, dates and email addresses.
Try the donations templateRelated Guides
Relevant Templates
Import Builder is an independent product and is not affiliated with, endorsed by, or sponsored by Salesforce. Salesforce is a trademark of Salesforce, Inc. Import rules as described in Salesforce's NPSP Data Importer documentation, November 2026.