Start with delimiter and row shape
A CSV can look fine in a text editor but parse incorrectly if the delimiter, quotes, line endings, or row lengths are inconsistent. Run delimiter and validation checks before changing values.
Data troubleshooting
CSV failures usually come from shape problems, not from the idea of CSV itself. Diagnose delimiter, header, row, encoding, and missing-value signals before converting the file or uploading it again.
Details
A CSV can look fine in a text editor but parse incorrectly if the delimiter, quotes, line endings, or row lengths are inconsistent. Run delimiter and validation checks before changing values.
Duplicate, blank, spaced, mixed-case, or punctuation-heavy headers often break import templates. Normalize headers only after checking the destination system's required column names.
A structurally valid CSV can still fail when required columns are blank, date formats vary, or numeric-looking values contain text. Use missing-value and column-profile reports before exporting.
XLSX can make data easier to review, but it can also hide delimiter problems that matter to the destination system. Validate and clean CSV first, then create a workbook handoff if needed.
Related tools