Salesforce CSV Import: Data Loader, Wizard, and Field Mapping

Two Primary CSV Paths in Salesforce

Data Import Wizard suits simpler standard objects and smaller volumes. Data Loader (or modern bulk APIs) suits large volumes, custom objects, upserts, and deletes. Pick based on object complexity and row count—not habit.

Step-by-Step: Prepare the CSV

Salesforce rejects rows for validation rules you cannot see in Excel.

• Export a report or Data Loader extract to learn API field names when needed.
• Use column headers that match labels or API names per your tool’s mapping UI.
• Include Id for updates; include an External ID field for upserts.
• Respect picklist values exactly (case and spelling).
• Format dates the way your org/locale expects—or use ISO where accepted.
• Save UTF-8 CSV; check in the Online CSV Editor.
• Run insert/upsert on a sandbox first when possible.

Record IDs, External IDs, and Upserts

Updating without Id creates duplicates. Upserting without a defined External ID field fails. Plan the key strategy before building the sheet.

• Update: CSV includes Id (18-character Salesforce IDs preferred).
• Insert: omit Id; satisfy required fields.
• Upsert: map External ID column; ensure uniqueness.
• Relationships: use related record Ids or external ID relationship fields.

Validation Rules and Required Fields

Org-specific rules are the surprise killers. Export failing rows from Data Loader’s error CSV, fix the cause (missing Industry, bad email, locked record), and reload only failures—not the entire success set again.

Real-World Examples

Admin workflows that stay calm.

Common Mistakes

Avoid these Data Loader nights.

• Inserting when you meant update.
• Using 15-character IDs in case-insensitive tools incorrectly—prefer 18-character IDs.
• Picklist values that do not exist in the org.
• Lookup fields populated with names instead of Ids.
• CSV opened in Excel that corrupted IDs into scientific notation.

Best Practices

Operate like a release engineer.

• Sandbox first for new mappings.
• Keep success and error CSVs with the batch.
• Upsert with External IDs for integrations.
• Minimize columns—only fields you intend to change.
• Preview with Convert CSV Online before upload.

Why Use Convert CSV Online?

Convert CSV Online is free, browser-based, and requires no account for everyday conversions. Clean Salesforce exports, fix encoding, and convert Excel mapping sheets to UTF-8 CSV before Data Loader. Client-side workflows work on Windows, macOS, and Linux browsers.

Conclusion

Salesforce CSV work is key strategy plus validation awareness. Choose Wizard vs Data Loader deliberately, map fields carefully, and reload only error rows until the batch is clean.