Import history & revert
Review past import jobs and undo any import that created bad records.
Every import job is recorded permanently in the History sub-tab. From here you can check what an import did, revert one that went wrong, or recover a job that got stuck.
The import jobs table
Open Import from the sidebar, then click the History tab. Each row is one import job with the following columns:
| Column | Meaning |
|---|---|
| File name | Original file as uploaded |
| Rows | Total rows in the file |
| Inserted | New contacts created |
| Merged | Rows merged onto existing contacts |
| Skipped | Rows that matched a skip rule (e.g., duplicate without a resolvable email) |
| Errors | Rows that could not be processed (malformed email, encoding error) |
| Status | Running / Done / Failed / Reverted |
Click a row to expand the error log, which lists the row number and reason for each error.
How revert works
The Revert button appears on every job with status Done or Failed. Clicking it triggers a soft-delete of every record that import job created:
- All contacts inserted by this job are soft-deleted and removed from every list and filter.
- All companies auto-created by this job are soft-deleted.
- Contacts and companies that pre-dated this import job are never touched — even if the job merged additional data onto them.
- Merged data (fields written onto an existing contact) is not rolled back. Only net-new records are removed.
After a revert completes, the job row shows status Reverted and the Revert button is disabled. The operation is final; there is no undo of a revert.
Enrichment and revert
After every import, Nomow runs a firmographic backfill: any company in the workspace with NULL firmographic fields is filled in from contact data linked to that company. This backfill affects companies beyond the current import job. Reverting the import removes the job's contacts and auto-created companies, but does not roll back backfill data that was written onto companies from other jobs.
Recovering a stuck job
A job shows status Running while the worker is processing batches. If a job stays in Running for more than 10 minutes without the counters updating, it is likely stuck.
Click Cancel on the stuck job row. The job moves to status Failed.
Verify the file is not malformed (encoding issues, a merged cell in XLSX, or a row count that exceeds 50,000). Re-export a clean CSV if needed.
Start a new import with the corrected file. The previous job remains in history as Failed for audit purposes.
Next steps
To understand what column mappings affect job outcomes, see Column mapping. For common reasons a job produces unexpected verdicts, see Import problems.
Was this article helpful?