Skip to content
TheSpreadFix

How to Prepare CSV Data for a CRM Import

Updated

Whether you're moving to HubSpot, Zoho CRM, Salesforce or Pipedrive, the import will only be as good as the file. This guide covers the preparation steps that apply to every CRM, in the order that avoids rework.

1. Start from a raw export and keep it

Export from the source system as CSV (UTF-8 if offered) or Excel, and keep that file untouched. Every cleanup step should produce a new file, so you can always compare against — or go back to — the original.

2. Get the structure right

  • Headers in the first row, one per column, no duplicates or blanks.
  • One record per row; no subtotal, title or note rows.
  • Remove empty rows and columns.
  • Split records by object if the CRM imports them separately (contacts, companies, deals).

3. Check required fields

Each CRM requires certain fields for each object — typically an email or last name for contacts and a name for companies and deals. Find rows missing those values before the import rejects them, and decide whether to complete them or leave them out.

4. Standardise formats

FieldRecommended format
EmailTrimmed, lowercase, valid
PhoneE.164, e.g. +919876543210
DateYYYY-MM-DD
CountryOne spelling per country (name or ISO code — match the CRM's options)
NamesConsistent capitalisation; leave intentional mixed case (McDonald) alone
IDs & codesStored as text so leading zeros survive

5. Deduplicate last

Remove duplicates after standardising, so formatting differences don't hide them. Deduplicate contacts by email, companies by domain or name, and use a composite key (first name + last name + phone) when there's no reliable identifier. Keep the most complete record.

6. Validate, then test with a small import

Run a final check on the cleaned file: no invalid emails left unintentionally, no unreadable dates, no missing required values. Then import a small sample (20–50 rows) first and check how fields landed in the CRM before importing everything.

7. Make it repeatable

Migrations rarely happen once — there's usually a second export, a delta or a weekly sync. Record your cleanup steps so the next file is prepared identically. In TheSpreadFix, save the fixes as a recipe and run it on the next export in one click.