Skip to Content
ContactDrive HelpHelp

Viewing Import History

See what each import did and why

Every import you run is recorded — what was imported, when, by whom, and what went wrong. When a file didn't land the way you expected, this is where you find out why.

Finding it

Import history is on the File Log page, listing past import jobs newest first. Jobs that are still running or waiting to start are listed above them, under Running and queued.

Reading a job

Each entry shows you what happened: how many contacts were created, how many matched existing contacts and were updated, and how many rows failed.

The second number is worth a look even on a clean import. A file you expected to be all-new arriving as mostly updates means your data was already there — which is good news, and a sign the duplicate matching is doing its job.

Errors

Rows that failed are recorded with the reason, and you can download them. The usual causes are a malformed email address, a date in a format that couldn't be read, a required field left empty, or a row with more or fewer values than the file has column titles. Each failed row's reason names its line in your file, so you can find it.

A failed row never stops the rest of the file from importing. The one exception is a quoted value that is never closed: the import stops at that line and says so, after importing the rows before it. See Import Tips for how to fix it and pick up from that line.

The download is the useful part: fix the rows in that file and re-import just those, rather than reprocessing the whole original.

Conflicts and partial imports

An import saves its work in batches as it goes. Two things follow from that:

  • Contacts edited during the import are left alone. If someone changes a contact after the import started, the import does not overwrite their edit. The contact is reported as a conflict, and the job's notes say how many contacts were left unchanged because they were edited after the import started.
  • A failure tells you what was saved. If an import fails partway, the entry reports what was saved up to that point instead of saying nothing was imported. An import interrupted by a server restart picks up from its last saved batch on its own.

Stopping a job

Started an import on the wrong file, or an export you no longer need? Under Running and queued, find the job and click Stop, then confirm.

  • A job that has not started yet is cancelled and does not run at all.
  • A running job stops at its next safe point. What it has already done stays done, and nothing after that point is saved.
  • A stopped import or export shows as Stopped. A stopped export does not produce a file.
  • Some jobs show Can't be stopped once started; those finish on their own.

Admins see every job that people in the workspace have started, and can stop any of them; the person who started the job is notified. Everyone else sees and can stop their own jobs.

Besides imports and exports, the list includes bulk jobs such as deleting contacts or activity, adding contacts in bulk, merging duplicates, and removing a tag from contacts.

While an import is running

Imports touch a lot of the workspace at once, so a few things pause while one is in flight — tag management, plan changes, and some billing actions all show Import in progress. Wait for the job to finish and they come back.

On this page