CSV guide
Why CSV Import Fails
The most common CSV import failures and how to fix them before uploading the file.
Recommended first tool
Start with CSV Data Quality Checker
Profile CSV data for missing values, duplicates, invalid formats, mixed types, outliers and more.
Open CSV Data Quality CheckerWhat this guide covers
- CSV import failures usually happen before the platform sees your data
- Use platform presets
- Check the data values, not just headers
- Keep a reviewed export
CSV import failures usually happen before the platform sees your data
A CSV can fail before a CRM, store, accounting tool, or database even checks field rules. Broken quotes, inconsistent column counts, duplicate headers, stray delimiters, and spreadsheet copy-paste artifacts can prevent the file from parsing into rows and columns.
The first check should be structural. Confirm that the header row is readable, every data row has the expected number of columns, quoted values close correctly, and the delimiter is the one the importer expects.
Use platform presets
A generic CSV validator is useful, but import readiness depends on the target platform. Shopify cares about handles, option values, variant prices and SKUs. WooCommerce cares about product type, stock status, publish state and SKU uniqueness. HubSpot and Mailchimp care heavily about email identity.
After the structural check passes, switch to the closest platform preset. The preset should flag required columns, duplicate identifiers, malformed dates, invalid prices, and controlled values that the target system will reject.
Check the data values, not just headers
A CSV can have every required column and still fail. Blank required cells, mixed number and text values, currency symbols inside numeric fields, inconsistent date formats, and invalid URLs often produce row-level errors after upload.
Run a data quality report before upload. Look for missing values by column, duplicate rows or keys, type drift, whitespace-only cells, constant columns, and suspicious outliers that may indicate exported totals or notes mixed into the table.
Keep a reviewed export
When you clean a CSV, export the reviewed output as a new file. Do not overwrite the original source export. Keeping the original, duplicate-only export, and cleaned export makes rollback and reconciliation much easier.
If the importer supports dry runs, use the cleaned file there first. A local preflight reduces obvious failures, but final acceptance can still depend on account-specific fields, custom mappings, and platform settings.
Example import workflow
Start with CSV Validator to catch quoting and row-length problems. Move to CSV Data Quality Checker to find blanks, duplicates and type drift. Then run the platform checker, such as Shopify CSV Validator or QuickBooks CSV Checker, before uploading the final reviewed file.
FAQ
Why does a CSV open in Excel but fail in an importer?
Spreadsheets are forgiving. Importers usually require strict headers, delimiters, row lengths and field values, so files that look fine in Excel can still fail automated parsing.
Should I clean duplicates before validating required fields?
Validate structure first, then inspect duplicates and required fields together. Removing duplicates too early can hide missing values that need review.
Related guides
Next workflow
Continue the preflight
CSV Validator
Validate CSV structure, delimiter parsing, row consistency and malformed records.
CSV Data Quality Checker
Profile CSV data for missing values, duplicates, invalid formats, mixed types, outliers and more.
CSV Cleaner
Clean CSV files by removing duplicates and optionally dropping incomplete rows.