CSV Import Errors: A Checklist Before You Upload

When a CSV import fails, first check the file's structure, then check the destination app's rules. A CSV can be structurally valid and still be rejected because required headers, identifiers or allowed values do not match the receiving system.

Work on a copy and keep the original export unchanged. Avoid repeatedly importing the full file while guessing at fixes; some importers update existing records as well as creating new ones.

Confirm what the destination expects

Download the destination's current sample file or export a small record from it. Compare the header names, required columns and update behaviour. Determine which field identifies an existing record and whether empty cells clear existing values.

Use a small trial import containing records you can inspect. Shopify, for example, documents platform-specific CSV requirements and common problems; another system may use different rules. Shopify's import troubleshooting

Check separators and quoting

A comma is a common delimiter, but some exports use semicolons or tabs. If an entire row appears in one column, the separator may have been interpreted incorrectly.

Quoted text can contain commas or line breaks. Splitting every line at every comma is not a reliable CSV parser. Check that quoted fields close correctly and that rows contain the expected number of fields. A line break inside a quoted address is not necessarily a new record.

Investigate unexpected characters

If names or descriptions display corrupted characters, check the export's encoding and the importer's expected encoding. Re-exporting from the original source with the intended encoding is preferable to guessing replacements after corruption has occurred.

Some destinations require UTF-8. A universal “encoding detected” message cannot prove every byte has been interpreted as intended, so inspect a few names with accents or non-Latin characters. Shopify's documentation identifies encoding as one cause of unexpected characters; that guidance is specific to its importer. CSV requirements

Preserve identifiers as text

Account codes, SKUs and postal codes may look numeric while functioning as identifiers. Leading zeros and long digit sequences can be changed by spreadsheet conversion. Microsoft documents how to import such columns as text and control automatic conversion. Microsoft's guidance

Once a saved file has lost digits, changing the display format may not restore the original value. Return to the unchanged export rather than inventing missing digits.

Separate duplicates from legitimate repetition

Repeated product names or customer names are not automatically errors. Check the field that the destination treats as unique. Two rows with the same identifier may represent a conflict, an intentional update, or a valid repeated relationship depending on the schema.

Review leading and trailing spaces, blank identifiers and case differences. Do not trim or deduplicate blindly: spaces and letter case can be meaningful in some systems.

Validate dates and allowed values

A date such as 03/04/2026 is ambiguous without a format. Use the destination's documented format and check time-zone handling for timestamps. Confirm that status labels, country values and numeric decimal conventions are accepted.

Distinguish a parser error from a business-rule error. Fixing quotation marks will not resolve a missing required identifier.

Import, compare, then expand

After the sample import, compare selected identifiers, totals, special characters and field mappings. Check whether records were created, updated or skipped. Retain the import report and the exact file used before scaling up.

Does opening a CSV in a spreadsheet prove it is valid?

No. Spreadsheet software may infer separators and convert values. That display is useful, but it does not prove compatibility with a particular application's schema.

Is an online checker safe for customer data?

Check whether processing happens locally or files are uploaded, what is retained and whether your organisation permits it. Start with a synthetic sample when that is unclear.

Can a checker guarantee a successful import?

A structural checker can catch some problems. Only the destination's rules and a controlled test import can establish whether the file works for your actual workflow.

Try an awkward sample before the full export

This illustrative CSV has an identifier that must remain text and a company name containing a comma:

customer_id,company
00042,"Acme, Ltd"

Use a real CSV parser to confirm that the second line contains two fields. Then test the destination's mapping and check that 00042 remains unchanged. Structural validity does not stop an importer from converting an identifier into a number.

The CSV import checker runs its supported checks in your browser. Use it to inspect structure and warnings, then perform a controlled test in the actual destination. It does not certify the destination's schema, business rules or successful delivery. Microsoft's text/CSV import guide explains import controls for its own software.