- A completed import job in the intended workspace
- The original source file and approved mapping decisions
- Access to imported, skipped, rejected, and duplicate results
- An owner for correcting exceptions without reimporting successful rows
Read the result, not just the success message
Open Contacts → Import history and select the job. The detail view records the file, creator, time, total rows, consent attestation, automation dispatches, company and list effects, and per-row outcomes.
| Outcome | Meaning | Next action |
|---|---|---|
| Imported | A new contact was created | Sample identity, owner, company, lists, and consent |
| Updated | A match received permitted changes | Compare protected and overwritten fields |
| Skipped | Policy deliberately excluded the row | Review the row reason before changing policy |
| Invalid | Required or formatted data could not be used | Correct the source row |
| Failed | Execution did not complete for the row | Preserve the error and retry only the exception |
| Duplicate | Identity was ambiguous or repeated | Resolve in Duplicate contacts or correct the source |
Use All, Imported, Updated, and Issues filters to isolate the rows you need. Download the invalid, duplicate, or failure exception file when available; retain source-row numbers so your correction can be reconciled.
Reconcile the batch
- Compare Imported + Updated + Skipped + Invalid + Failed against the selected count.
- Inspect several new contacts and several updates, including rows with companies, lists, secondary methods, and consent.
- Check company and list creation counts against the approved plan.
- Confirm automation dispatch status. A completed contact import does not prove every downstream automation succeeded.
- Open Duplicate contacts when the job produced identity conflicts.
Retry only what needs retrying
Create a new file containing corrected exception rows. Do not mix already successful rows into the retry. Keep the same external identifiers and approved overwrite policy. A second run should have its own owner and reconciliation record.
Undo a wrong import
When Undo import is available, the import creator or a workspace owner/admin can request operational undo. Read the confirmation carefully: new contacts are archived, imported updates are restored, and imported notes and memberships are removed. Changes teammates made after the import are preserved where possible. Messages, webhooks, and other external automation effects are not reversed.
After undo, the job records who performed it, when, and a summary of preserved concurrent or supporting records. Reopen a sample of affected contacts before deciding whether to run a corrected import.
Escalate with useful evidence
Provide the job identifier, file name, approximate run time, source-row numbers, visible outcome, and a redacted exception file. Do not include the full customer dataset when a few sanitized rows demonstrate the problem.
- Counts balance to selected rows
- New and updated samples verified
- Exception rows isolated from successes
- Automation effects reviewed separately
- Undo or retry decision recorded