Loading

Import Wizard fails with generic error message

Julkaisupäivä: Jun 17, 2026
Kuvaus

This article is a supplement to the known issue: The import wizard fails with a generic error.

When using the Salesforce Data Import Wizard, you may encounter a generic error message when importing a file even though the data appears to be correctly formatted. These generic errors typically occur in older versions of the Salesforce Data Import Wizard and can be frustrating because they do not indicate the specific cause of the failure.

Common causes of generic import errors:

  • Unique field violations (duplicate values in a unique field)
  • Missing required fields in the import file
  • State or Country picklist values not configured in Salesforce
  • Empty rows in the import file
  • Import file is too large
  • Validation rules evaluating to true on imported records
  • Restricted picklist values that do not match existing active values
Ratkaisu

Addressing common Data Import Wizard errors to ensure your file is properly formatted:

1. Check for Unique Field violations
Find out whether the object you are importing into has unique fields. If it does, ensure the import file does not contain a value that already belongs to an existing record in Salesforce. Duplicate values in unique fields cause the import to fail with a generic error.

2. Verify Required Fields are present
Find out whether there are required fields on the object in question. If there are, ensure they are included in the import file with valid values. You may also see a "Data already exists" error message when some required fields are missing.

3. Validate State and Country Picklist values
If the State and Country Picklist feature is enabled in your org, you must import values that are predefined in the State and Country Picklist configuration page. If the import file contains State values not yet configured in Salesforce, the import fails. Either deactivate this feature temporarily or ensure the import file only contains States already created in Salesforce.

4. Remove empty rows from the file
Ensure the import file does not contain any empty rows before the last row of data. Empty rows in the middle or at the end of the file (before the final record) cause parsing errors.

5. Split the file into smaller batches
Try splitting the import file into smaller files with fewer records per file and import them separately. This can help isolate which records or data values are causing the error.

6. Temporarily disable Validation Rules
If you are uncertain whether a Validation Rule is evaluating to true for imported records, temporarily deactivate Validation Rules on the object in question. Note that deactivating Validation Rules may affect data quality, so re-enable them immediately after the import.

7. Check Restricted Picklist values
Review the import file for picklist field values that do not match an active value in the Salesforce picklist configuration. Either add the missing value to the picklist definition in Setup, or update the import file to use an active value.

Using the Unified Data Import Wizard — Reviewing import jobs:
With the Unified Data Import Wizard, you can review your import jobs by accessing the Bulk Data Load Jobs section as outlined in Determine which records are imported using Data Import Wizard.

Note: The Monitoring Bulk Data Load Jobs setup section is not available in all Salesforce Editions. See Salesforce editions with API access for more details.

Alternative import tools if the Import Wizard continues to fail:


Knowledge-artikkelin numero

000384955

 
Ladataan
Salesforce Help | Article