An import preview puts a whole row in one column, or an accented name appears corrupted. Inspect the file format and importer settings before correcting records in the destination system.

RFC 4180 describes a common comma-separated CSV format, while applications may expect other delimiters or additional conventions. A regional spreadsheet export does not automatically suit every importer.

Start with a small test file

This artificial example uses commas and includes one inside a quoted field:

id,name,price_cents
sample-1,"Mug, large",1290
sample-2,Türschild,2400

Quoting keeps the internal comma within one field. Replacing every comma with a semicolon would alter that content. Explicitly document the delimiter, encoding and any byte-order-mark handling.

Inspect column counts and field mappings in the preview. Then verify parsed and stored values rather than relying on a “file processed” message. Integer cents are a deliberate representation in this example; your destination may require another format.

Also test an optional empty cell and text containing quotation marks. Run against isolated data and retain the original export. Only prepare the larger dataset once the sample parses and persists correctly under the same explicit configuration.

Download the fictional CSV sample · UTF-8, CSV.

Sources