> ## Documentation Index
> Fetch the complete documentation index at: https://visaflo.ca/knowledge-base/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting CSV import errors, duplicate records, and failed migrations

> Fix CSV import problems by validating source rows, required fields, duplicate handling, and partial-import state before retrying.

## Check whether the import partially succeeded

Before uploading again, search VisaFlo for a few rows from the attempted file. An import can create some records before an error is reported. Re-running the full file without checking can create duplicates or make the result harder to reconcile.

## Validate the source file

Review the file for one record per row, consistent headers, valid emails where required, and no merged cells or hidden characters. Normalize email addresses and remove duplicate rows in the source file before importing. Keep a copy of the original export and a dated copy of every cleanup version.

## Diagnose common errors

| Symptom                      | Check first                                                                                      |
| ---------------------------- | ------------------------------------------------------------------------------------------------ |
| Invalid email                | Spaces, invisible characters, multiple addresses in one cell, or missing values.                 |
| Duplicate client or lead     | Existing record by email, previous partial import, or duplicate source row.                      |
| Columns mapped incorrectly   | Header names, sample row values, and whether the target expects separate first/last name fields. |
| File is rejected             | File type, encoding, required headers, and size.                                                 |
| Case migration is incomplete | Whether the source contains data that has no direct VisaFlo equivalent.                          |

## Retry with a small sample

Correct the source file, then import a small representative sample. Confirm that names, emails, assignees, and stages are correct before importing the remaining rows. Treat a full case migration as a separate mapping exercise; document files, task history, and custom fields may need a staged transfer rather than a spreadsheet upload.

## Escalate with a sanitized sample

Send support the import type, error text, source column headers, sample row number, and a sanitized sample file if secure transfer is not arranged. Do not attach an entire client export to a general support message.

See [CSV imports](/knowledge-base/faq/how-to-import-clients-leads-and-cases-from-csv-or-another-platform).