Resolving records that are not imported

When importing a list of records, some records cannot be imported. There are two reasons that records from an import list are not imported:

  • The import record is identified as a duplicate.
  • The import record is missing required information.
Note: These steps apply to record import only, not lead imports. See Importing records

To resolve records that were not imported:

  1. Access the Import History detail view. See Using the Import History detail view
  2. Select the History tab.
  3. Access the source file.
  4. Use the line number, or record number listed in the Description to find the corresponding record in the source file on the History tab. See Import History - History tab
  5. Resolve the issue listed in the Description. These are the most common issues:
    • # is being skipped a record was found for Contact: the record was identified as a duplicate record and was not imported. Perform one of the following:
      • If the record is a duplicate and should not be imported, no action is required.
      • If the record was misidentified as a duplicate, edit the record so that the matching criteria no longer matches an existing record. This is based upon the Matching Criteria specified during the import. Options include Email, etc. 
    • # is being skipped a record was found for Account: the record was identified as a duplicate record and was not imported. Perform one of the following:
      • If the record is a duplicate and should not be imported, no action is required.
      • If the record was misidentified as a duplicate, edit the record so that the matching criteria no longer matches an existing record. This is based upon the Matching Criteria specified during the import. Options may include Email, etc.  
    • Value cannot be an empty string. Parameter name: the record did not have any data in the a required field.
      • Modify the record to include the required information identified in the Description that is missing from the import record.
  6. Repeat until all the errors are resolved.
  7. Save the changes to the import file.
    Note: If the import file is very large and the number of records that are not imported is relatively small, it can be beneficial to create a copy of the import file that contains only the records that require to be re-imported and re-import the updated file.
  8. Repeat the record import with the updated import file.
    Note: When the import is complete, the Import History record can list errors or duplicates. If you re-import files that are already successfully imported, then those records are identified as duplicate records.