Resolve import errors Live

Diagnose dropped rows from a CSV import — headers, phones, emails, duplicates, encoding — and upload a corrected file.

Updated 1 min readMaintained by Landing Zone

When an import finishes with fewer contacts than your file contains, the missing rows were invalid and dropped. Landing Zone counts and reports dropped rows so you can fix the file and upload the corrected file again.

Before you start

  • The import report from your last run — it shows how many rows were dropped.
  • The original file, so you can correct it and keep a before/after comparison.

Steps

  1. Check the import report. After a run, the report shows how many rows were imported and how many were dropped.
  2. Fix header problems. Headers belong in the first row, one unique name per column. Also recheck your mapping — a mismapped column can invalidate whole rows. See Map imported columns.
  3. Fix invalid phone numbers. Remove letters, notes, and extra punctuation from phone columns, and complete any partial numbers.
  4. Fix invalid email addresses. Correct typos, missing @ signs, and stray spaces.
  5. Remove duplicates. Deduplicate rows in your spreadsheet before uploading.
  6. Fix encoding issues. Garbled characters (like ’) mean the file was saved in the wrong encoding. Save or export it as a UTF-8 CSV, then confirm the sample preview reads cleanly.
  7. Upload the corrected file again. Open Import, upload the fixed file, and reuse your saved mapping profile — see Import a CSV.
  8. Confirm the new report. The dropped count should fall. Repeat the fixes for anything that remains.

Limitations

  • Landing Zone drops invalid rows rather than repairing them — corrections happen in your source file.
  • The report gives you the dropped-row counts; keep your original file so you can compare it against what was imported.
  • Screening exclusions (DNC & Litigator Scrub results) are separate from import drops — see Review screening results.

Frequently asked questions

Where do I see how many rows were dropped?

In the import report after the run — dropped rows are counted and reported there.

My file looks clean but rows still drop — now what?

Check the encoding (save as UTF-8 CSV), confirm the sample preview reads correctly, and recheck the column mapping. If a clean file still loses rows, reach out via the contact support page.