zintara.io

Lead management · Practical guide

CSV encoding and special characters: repair names without shifting columns

Verify both encoding and CSV structure. Garbled accents suggest an encoding problem; values appearing in the wrong column suggest a parsing or quoting problem.

Reviewed · Examples are illustrative

Who this helps: Operators preparing contact data, exclusions and campaign audiences.

Define the decision

These failures can look similar in a preview but need different repairs. Replacing accents manually can hide a file-wide encoding issue. Removing commas from company names can hide invalid quoting. Preserve the source, identify the defect and export a corrected file from a tool supporting the required format.

Work through the procedure

  1. Compare a known accented name in the source and exported file. Use an explicit UTF-8 export instead of relying on a legacy default encoding.
  2. Inspect commas, quotes and line breaks inside fields. RFC 4180's common format uses quoted fields for these cases and doubles internal quotation marks.
  3. Create a tiny sample containing difficult values. Confirm the importer keeps each value in its intended column.
  4. Inspect the saved contact and rendered email after import. Correct spreadsheet display alone does not prove exported bytes were interpreted correctly.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

email,firstName,company
[email protected],Ana,"North, South Ltd"
[email protected],René,"The ""Workshop"" Group"
Expected: company commas stay in one field; René keeps the accent

Read the result

The example tests field boundaries and character preservation separately. If a company splits into extra columns, inspect quoting and delimiters. If René becomes garbled while columns remain correct, inspect encoding. Fixing the right layer avoids destructive replacements across legitimate names and gives you a repeatable check for the next export.

Check before moving on

  1. Verify the actual delimiter; a semicolon export is not interchangeable with a comma-based import just because both end in .csv.
  2. Keep a clean original so a failed conversion can be reversed.
  3. Review imported values rather than repeatedly resaving with changing spreadsheet defaults.

Limits and next action

CSV implementations vary, and the cited RFC describes a common format, not every spreadsheet behavior. This guide does not promise automatic encoding repair by Zintara. If a corrected sample fails, provide a minimal redacted file and exact error for investigation.

Source: RFC 4180: common CSV format

Source references

Worked examples are illustrative. Editorial procedures are suggested methods, not measured performance claims or promises of additional product features.

Related guides

Explore the Zintara workflow