ImportFix

Malformed CSV repair

Fix malformed CSV files before your import breaks

Scan malformed CSV exports, preview structural issues, and repair common formatting problems before importing into another system.

What this problem usually means

Malformed CSV files usually fail for boring structural reasons: a broken quote, a row with the wrong number of cells, mixed delimiters, or line-ending issues that make the file ambiguous to the importer. The goal is not to manually edit rows one by one. The goal is to detect the structural problem quickly, repair the file shape, and export a cleaner CSV before the next import attempt.

Why it happens

  • The export was generated by a system that does not escape quoted text correctly.
  • Someone opened the file in a spreadsheet app and saved it back with a different delimiter or line-ending style.
  • Rows were copied or merged from different systems, leaving the file with inconsistent structure.

What ImportFix checks

  • Delimiter detection and delimiter mismatch suspicion
  • Inconsistent row lengths against the header
  • Duplicate headers, empty rows, and empty columns
  • Possible malformed quote patterns and mixed line endings

Common repairs

Normalize row lengths so every record matches the expected column count
Rename duplicate headers for safer field mapping
Remove empty rows or empty columns that add noise to the import
Standardize delimiters and line endings before export

When to review manually

If a row contains badly broken quoting or merged cell content, always review the repaired preview before importing. A structural repair can fix the file shape, but you still want to confirm the value ended up in the correct column.

Related guides

Keep exploring the most common import problems, or jump into the repair workspace directly.

Open repair workspace