CRM · Files

How to resolve import errors and review saved data

Fix flagged rows, confirm which records were processed, and check the results in CRM.

Real CRM Mass import preview with an invalid cell flagged for correction

Published on October 16, 2026

The Mass import preview helps you find problems before saving, while the final result confirms what happened when CRM processed the file. Knowing the difference helps you correct the right rows and then verify that the information appears in the correct CRM section.

Do not confirm automatically. If the pre-import summary says that some rows will be skipped, return to the table and review the errors before continuing, unless you have decided to exclude those records.

1. Find the flagged value

After mapping the columns, check for warning icons next to cells. Hover over an icon to read the reason; for example, an incorrectly formatted e-mail address may show “The value is not a valid e-mail address.” You can also select Filter errors at the top to display only rows with issues.

Import preview with an invalid e-mail marked in the sample row — Example: the invalid e-mail is marked in the column where it was detected. The data shown is fictional.

2. Correct the row or exclude it

Click the cell with the issue, correct the value, and leave the cell so CRM can validate it again. If the row should not be part of the import, remove it from the preview using that row’s delete icon. Do not remove a row just to hide an error if you still need that record.

If the issue is with a mapping, check the field list above the column: select the right field or use Skip column if you do not want to import that data. Required fields, marked with an asterisk, must be mapped. Import cannot start while a column is unconfigured or a required field is missing.

The e-mail cell is corrected and no longer shows a validation warning — When the value is corrected, the warning for that cell disappears. The screenshot shows the interface in Spanish.

3. Check how many rows will be processed

When you select Import, the confirmation dialog shows the total and warns if rows that still contain errors will be skipped. If the number is different from what you expected, cancel and check whether you ignored the header row correctly, selected the right separator, or removed a row by mistake. Confirm when the count looks right.

When processing finishes, the CRM summary distinguishes imported, new, and updated records. If the server detects issues, review the error details and use the available action to return to the data and correct any remaining rows.

Real summary distinguishing imported, new, and updated records — This summary is for a fictional record. Counts depend on the file you import.

4. Verify the saved records

After the summary, open the list for the entity you selected. For example, if you imported Prospects, go to CRM > Prospects; for Customers, Opportunities, Sales, Companies, or Products, open the corresponding list. Use a name, e-mail address, or another unique value from the file to find a few records and confirm that the data is in the expected fields. The history confirms the operation, but it does not replace reviewing the records.

CRM Prospects list with a sample record imported from a file — In Prospects, the sample record appears in the list with its latest contact identified as imported from an external file. Names and data are fictional.

5. Review the history carefully

Go back to Tools > Mass import to review previous operations. The list shows the entity, date, number of records, and executive who performed the import. If there are several operations, use these details to identify the batch you just processed.

Mass import history showing entity, date, record count, and executive — History makes it easier to confirm when and what entity was imported. The screenshot shows a demo account.

Important before deleting. The history’s Delete action cannot be undone: it deletes contacts created by that import, but does not delete or revert contacts that were updated. Review the confirmation message and make sure you selected the right batch.