You are here:
Troubleshoot NPSP Data Importer Errors
Learn how to find and fix NPSP Data Import errors.
- Overview
Understand why errors can occur when you use NPSP Data Importer. - Error Examples
There are many reasons why failures occur. - View Data Import Wizard Errors
When using the Data Import Wizard to import your data into NPSP, errors are captured in Bulk Data Load Jobs results files and error notification emails from Salesforce. - View Failed NPSP Data Import Records
You can find details about errors that occur during NPSP Data Importer processing on failed NPSP Data Import records. These errors aren't logged in the NPSP Error Log. - Still Need Help?
Learn how to contact Salesforce Support.
Overview
Understand why errors can occur when you use NPSP Data Importer.
Errors can occur when you enter data through Gift Entry or import spreadsheets using Data Import Wizard and NPSP Data Importer. Some required data might be missing, data can be improperly formatted, or maybe there are customizations in your org preventing the import from successfully processing. Despite the best efforts of you and your staff, your data import or data entry can sometimes fail.
Data import errors occur when:
-
NPSP can't create NPSP Data Import records. When you use the Data Import Wizard to import data into the NPSP Data Import object, you'll see these errors in Bulk Data Load Jobs results files and error notification emails from Salesforce. Learn more in Open the result file from Bulk Data Load Job page. When using Gift Entry, the error is reported on screen to the user.
-
NPSP Data Importer can't create or update the target records (Accounts, Contacts, etc.). NPSP captures these errors in the Status and Failure Reason fields on as NPSP Data Import records. The NPSP Data Importer process can also partially fail, meaning that it creates some, but not all, NPSP records. Learn more in View Failed NPSP Data Import Records.
Error Examples
There are many reasons why failures occur.
Let's look at some example errors and their causes:
| Cause | Error Result | Error Location | Example Error Message |
|---|---|---|---|
| Validation rule on the NPSP Data Import object | Salesforce couldn't create the NPSP Data Import record | Bulk Data Load Jobs (when using the Data Import Wizard) | FIELD_CUSTOM_VALIDATION_EXCEPTION, You must have a Mobile Phone for all Contacts processed through NPSP Data Import.: [] |
| Required custom field on the NPSP Data Import object | Salesforce couldn't create the NPSP Data Import record | Bulk Data Load Jobs (when using the Data Import Wizard) | REQUIRED_FIELD_MISSING, Required fields are missing: [External Batch Number]: [External Batch Number] |
| Required field or validation rule on the NPSP Data Import object | Salesforce couldn't create the NPSP Data Import record | On screen when using Gift Entry | ,"DMLErrorFieldNameMapping":}Id not specified in an update call |
| Improperly formatted email address | Salesforce couldn't create the NPSP Data Import record | Bulk Data Load Jobs (when using the Data Import Wizard) | INVALID_EMAIL_ADDRESS:Contact1 Personal Email: invalid email address: importtest.org:npsp__Contact1_Personal_Email__c -- |
| Currency symbol included in Donation Amount | Salesforce couldn't create the NPSP Data Import record | Bulk Data Load Jobs (when using the Data Import Wizard) | INVALID_FIELD:Failed to deserialize field at col 8. Due to, '$225.00' is not valid for the type xsd:double:npsp__Donation_Amount__c -- |
| Improperly formatted Donation Date | Salesforce couldn't create the NPSP Data Import record | Bulk Data Load Jobs (when using the Data Import Wizard) | INVALID_FIELD:Failed to deserialize field at col 9. Due to, 'Jan 1st 2021' is not a valid value for the type xsd:date:npsp__Donation_Date__c -- |
| Invalid Id for Contact1 Imported | Salesforce couldn't create the NPSP Data Import record | Bulk Data Load Jobs (when using the Data Import Wizard) | MALFORMED_ID:Contact1 Imported: id value of incorrect type: 0034u00002XHNRLXXX:npsp__Contact1Imported__c -- |
| Missing Contact1 Last Name | Salesforce couldn't create the Contact record | NPSP Data Import record | You must specify Last Name. |
| Before Insert trigger on the Opportunity object | Salesforce couldn't create the Opportunity and Payment record | NPSP Data Import record | npsp.TDTM_Opportunity: execution of AfterInsert caused by: System.DmlException: Insert failed. First exception on row 0; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, oppProcesses: execution of AfterUpdate caused by: System.FinalException: Record is read-only (): [] (npsp) |
| Required custom field on the Payment object | Salesforce couldn't create the Payment record | NPSP Data Import record (or on screen when using Gift Entry) | Required fields are missing:custom_phone |
View Data Import Wizard Errors
When using the Data Import Wizard to import your data into NPSP, errors are captured in Bulk Data Load Jobs results files and error notification emails from Salesforce.
Learn more in View Bulk Data Load Job Details and Open the result file from Bulk Data Load Job page.
View Failed NPSP Data Import Records
You can find details about errors that occur during NPSP Data Importer processing on failed NPSP Data Import records. These errors aren't logged in the NPSP Error Log.
Failed NPSP Data Import records have a Status value of Failed. This status means that the NPSP Data Importer either completely or partially failed to process the record. Learn more about why the record failed in the record's Failure Information field.
Create and Subscribe to a Failed NPSP Data Import Records Report
While you can view NPSP Data Import records individually and with list views, there's no built-in method for receiving notifications from NPSP when there are failed NPSP Data Import records. To receive notifications, create and subscribe to a custom report.
-
Click the Reports tab.
-
Click New Report.
-
Search for and select NPSP Data Imports.
-
Click Continue.
-
Click Filters.
-
Click Show me, select All npsp data imports, then click Apply.
-
In Add filter, search for and select Status.
-
Select Failed and click Apply.
-
Click Outline.
-
In Add column, search for and select Failure Information.
-
Add additional columns to include in the report.
-
Click Save & Run.
-
Enter a Report Name such as Failed Data Imports.
-
Choose a Folder where you'd like to store the report and click Save.
-
Next to Edit, click the arrow and select Subscribe.
-
Choose a Frequency (we recommend Daily) and a Time.
-
Save the report.
According to the frequency you chose, Salesforce sends an email with a report summary and a link to view the report.
Analyze Failed NPSP Data Import Records
Let's look at a failed NPSP Data Import record in detail. In this example, a validation rule on the Payment object prevented NPSP Data Importer from creating or updating one or more records. But how can you tell which records?
Within an NPSP Data Import record, you'll see Imported and Import Status fields for each record NPSP Data Importer tried to create or update. When NPSP Data Importer can't create or update a record, the Imported field is blank and the Import Status describes what happened.
Let's look at the Imported and Import Status fields to understand which records the NPSP Data Importer successfully processed.
| Field Name | Field Data | Result |
|---|---|---|
| Contact1 Imported | Donor's Name | Successful - NPSP created the donor's Contact record. |
| Contact1 Import Status | Created | Successful - NPSP created the donor's Contact record. |
| Household Account Imported | Donor's Household Name | Successful - NPSP created the donor's Household Account. |
| Donation Imported | Donation Name | Successful - NPSP created the donation Opportunity record. |
| Donation Import Status | Created | Successful - NPSP created the donation Opportunity record. |
| Payment Imported | Blank | Failure - NPSP couldn't create the donation Payment record. |
| Payment Imported Status | Missing Batch Number | Failure - NPSP couldn't create the donation Payment record. |
From this field data we can see that the donor's Contact, Household Account, and Opportunity records were created, but not the Payment record.
Resolve a Failed NPSP Data Import
For this example, you could resolve the issue by disabling or adjusting the validation rule so that it doesn't execute when using Gift Entry or during data import. For more information see Managing Validation Rules.
To reprocess failed NPSP Data Import records:
-
Open the App Launcher and click NPSP Data Imports.
-
Select the Failed Data Imports list view.
-
Click Import All Data Import Records. If you selected some records to import, click Import Selected Data Import Records.
Note Start Data Import reprocesses all failed Data Import records. -
Click Begin Data Import Process.
-
When the data import process completes, you'll see the results including the number of records processed, imported, and failed. Click Close to return to the NPSP Data Import tab.
Still Need Help?
Learn how to contact Salesforce Support.
If you’re still having problems with Gift Entry or data import, open a support case. See How to Create a Case on Salesforce Help.

