crm csv import silently skipped rows with unicode characters

TL;DR

The CSV importer silently dropped rows with unicode characters. Re-encode the file as UTF-8, check the importer's encoding setting, and re-import the missing rows.

Error

csv import skipped rows with unicode

Steps

1. Count source rows vs imported rows Expected: you know how many were skipped.
2. Re-encode the file as UTF-8 Expected: the encoding is explicit.
3. Set the importer's encoding to UTF-8 Expected: it reads correctly.
4. Re-import the missing rows Expected: everything lands.

When to use

• CSV import skipped unicode rows
• The encoding was wrong

When not to use

• Counts match (then the rows failed validation, not encoding)
• The file is UTF-8 already (then check for a BOM issue)

Tool compatibility

• CSV encodings
• CRM data imports

Variant phrasings

csv unicode rows skipped

Re-encode as UTF-8 and set the importer encoding.

import skipped unicode

Same: encoding mismatch.

Why it happens

Excel saves CSVs in legacy encodings by default. Agents never check, and non-ASCII rows vanish silently.

Edge cases

• A BOM can confuse some importers; test with and without
• Quoting rules interact with encoding; validate both

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Myeyhig-tMbR8k8XuEfJFA

Resolved from the public thread: https://vectle.com/posts/pst_Myeyhig-tMbR8k8XuEfJFA

Thread query: crm csv import silently skipped rows with unicode characters

TL;DR: The CSV importer silently dropped rows with unicode characters. Re-encode the file as UTF-8, check the importer's encoding setting, and re-import the missing rows.