How to Map CSV Columns for CRM Import
Updated
Your CSV says 'First Name' but HubSpot wants 'firstname'. Salesforce expects 'Phone' but your export has 'Mobile Number'. Column mapping is the step that connects your file's headers to the CRM's field names so data ends up in the right place.
What column mapping is
Column mapping is the process of matching each column in your CSV to a field (property) in the target system. Most CRMs have a mapping step during import, but it's error-prone: the importer shows a dropdown for each column, and if your file has 40 columns you're making 40 manual selections. Get one wrong and data lands in the wrong field — or gets skipped entirely.
Renaming your CSV headers to match the CRM's expected names before you upload eliminates this step and reduces mistakes.
Why CRMs need specific column names
Each CRM stores data in predefined properties with internal names. The import tool tries to auto-match your column headers to these properties, but it only works when the names are close enough. When headers don't match, the column is left unmapped and the data is silently dropped unless you manually assign it.
| Your CSV header | HubSpot property | Salesforce field | Zoho field |
|---|---|---|---|
| First Name | firstname | FirstName | First_Name |
| Last Name | lastname | LastName | Last_Name |
| Phone | phone | Phone | Phone |
| Company | company | Account.Name | Company |
| Job Title | jobtitle | Title | Designation |
| Country | country | MailingCountry | Mailing_Country |
The same data needs different column names depending on the CRM. A file prepared for HubSpot won't auto-map correctly in Salesforce without renaming the headers.
Step 1: get the CRM's import template
Most CRMs provide a sample import file or a list of accepted field names. In HubSpot, go to Contacts → Import → download the sample file. In Salesforce, check Setup → Object Manager → the object you're importing → Fields & Relationships. In Zoho, go to Setup → Data Administration → Import and download the template.
Use these templates as your reference for the exact column names the CRM expects, including capitalisation and separators.
Step 2: rename columns manually
- Open your CSV in Excel or a text editor.
- Compare each header with the CRM's expected field names from the template.
- Rename headers to match exactly — 'firstname' not 'First Name' for HubSpot, 'FirstName' not 'First name' for Salesforce.
- Delete columns that don't correspond to any CRM field, unless you plan to create custom properties for them.
- Save the file and verify in the CRM's import preview that all columns auto-map correctly.
Manual renaming works but doesn't scale when you import from the same source repeatedly with 30+ columns.
Step 3: use TheSpreadFix column mapper
TheSpreadFix's column mapper lets you upload your CSV, select the target CRM, and see suggested mappings for every column. It recognises common header variations — 'First Name', 'first_name', 'fname', 'Given Name' — and maps them to the CRM's internal field names. You can adjust any mapping, save it as a template for future imports, and download the file with the headers already renamed.
Tips for reliable mapping
- Map all required fields first — the CRM will reject the import if mandatory properties (usually email or last name for contacts) are missing.
- Watch for fields that look similar but aren't — 'Phone' vs 'Mobile Phone' vs 'Work Phone' are different properties in most CRMs.
- If you're creating custom properties for unmapped columns, create them in the CRM before importing so the import tool can map to them.
- Test with a small file (10-20 rows) to verify every field landed in the right place before importing the full dataset.
Frequently asked questions
What happens to columns I don't map?
Unmapped columns are ignored during import — the data is not imported. If you need that data in the CRM, either map it to an existing property or create a custom property first.
Can I reuse a mapping for future imports?
Most CRMs don't save column mappings between imports. TheSpreadFix lets you save a mapping template so the same source file can be prepared for the same CRM with one click.