What does CSV stand for?

CSV stands for Comma Separated Values, a plain text format where commas separate field values and newlines separate records.

What character encoding does Salesforce expect for CSV imports?

Salesforce expects UTF-8 encoding for CSV imports, which is especially important for non-ASCII characters like accented letters.

Why should you run a small test batch before a large CSV import?

A small test batch catches CSV formatting issues, field mapping mistakes, and data type errors before the full import runs and creates a mess to clean up.

CSV (Comma Separated Values)

Development🔴 Advanced

Definition

CSV (Comma Separated Values) in Salesforce refers to the plain text file format used for importing and exporting data. CSV files use commas to separate field values and newlines to separate records. Salesforce tools like Data Loader, Data Import Wizard, Bulk API, and report exports all use CSV format. Data must conform to the correct field mappings and character encoding (typically UTF-8) for successful processing.

Real-World Example

At their company, a Salesforce developer at CodeBridge leverages CSV (Comma Separated Values) to create a robust integration between Salesforce and an external system. Using CSV (Comma Separated Values), the developer builds an efficient solution that syncs data in near real-time, handles error scenarios gracefully, and includes detailed logging for troubleshooting.

Why CSV (Comma Separated Values) Matters

CSV is the default data exchange format for most Salesforce import and export tools. Data Loader, Data Import Wizard, Bulk API, Bulk API 2.0, and report exports all read and write CSV files. The format is simple: the first row typically contains column headers matching Salesforce field names or API names, and each subsequent row represents one record with values separated by commas. Newlines separate records, and values containing commas or special characters are wrapped in double quotes.

Despite the simplicity, CSV handling has a lot of gotchas in practice. Character encoding matters (Salesforce expects UTF-8 for non-ASCII characters, and saving from Excel in the wrong encoding will mangle accented letters). Date and datetime formats must match Salesforce's expected format or conversions will fail. Fields containing line breaks need to be quoted properly, and fields containing literal quotes need them escaped. Most import failures trace back to CSV formatting issues rather than actual data problems, so careful CSV preparation saves huge amounts of debugging time.

How Organizations Use CSV (Comma Separated Values)

•CodeBridge — Exports Salesforce data to CSV nightly as part of their data warehouse pipeline. The CSV files are picked up by an ETL tool, transformed, and loaded into the warehouse, which works reliably because the CSV format is universally supported.
•TerraForm Tech — Uses CSV files for all their Data Loader imports and has a preparation checklist: validate encoding is UTF-8, confirm date formats match the target field types, check for embedded commas and line breaks, and run a small test batch before the full load.
•Quantum Labs — Discovered that an Excel-saved CSV was corrupting Spanish-language customer names because Excel defaulted to a non-UTF-8 encoding. Switching to saving via Python's csv module with explicit UTF-8 encoding fixed the issue permanently.