How to Normalize Name Casing and Compound Surnames for Salesforce Import

Why does Salesforce keep names in ALL CAPS or broken casing after import?

The Salesforce Data Import Wizard does not standardize letter case during import. Names written as JONES or in disjointed lowercase are written to your records exactly as they appear in the CSV, which then breaks personalization on outbound mail-merge and receipts.

The import wizard behaves as a passive consumer of your file: it maps columns to fields and writes the raw strings. It never applies Title Case, never fixes casing, and never repairs encoding. So a lead list full of JONES, mary o'brien, or mixed-case junk becomes permanent record data, and every automated email that greets the contact by name inherits the formatting errors.

How do I fix compound surnames like de la Cruz or McDonald automatically?

A naive text-transform capitalizes the first letter of every word and mishandles surname prefixes — it turns mcdonald into Mcdonald and de la cruz into De La Cruz. CleanCrumbs applies casing rules that recognize compound and prefixed surnames and produces correct output such as McDonald and De la Cruz.

Standard uppercase or capitalize formulas fail on real-world names because they treat every space-delimited token identically. CleanCrumbs uses a dictionary-aware casing engine that understands prefixes (de, la, van, mac/mc) and internal capitals, so names are normalized to their conventional form instead of a mechanical Title Case.

Why do accented names like Chloé break during Salesforce import?

Character-encoding mismatches turn UTF-8 characters into mojibake — Chloé becomes chloé — when a file is saved with the wrong encoding. CleanCrumbs enforces clean UTF-8 output so accented and international names survive the import intact.

Encoding damage is easy to miss in a spreadsheet preview but corrupts profile-matching keys and personalization downstream. CleanCrumbs reads and re-writes your data as UTF-8, repairing common mojibake patterns so Chloé, José, and Renée stay correct all the way into Salesforce.

Does name cleaning happen privately in my browser?

Yes. Name casing and encoding repair run inside a Web Worker on your device. Raw file data never leaves the browser, enforced by a strict Content Security Policy.

No rows are uploaded to a server. You can review every change in a row-level diff view before exporting, then run the Pro Salesforce NPSP readiness scan to validate the file against import rules.

How CleanCrumbs fixes this in your browser

CleanCrumbs normalizes name casing with a prefix-aware engine, repairs UTF-8 encoding, and lets you review every change before export — all locally in your browser. Your cleaned names map cleanly into Salesforce NPSP fields with professional Title Case. Start free with up to 3,000 rows per file.