Original worked guide / 2026-10-05
Prepare a HubSpot contacts CSV: checks before import
Before importing contacts into HubSpot, review the selected import mode, property mappings and unique identifier. The local CSV checker can help with file structure and the rules you specify. It does not connect to HubSpot, compare account records or certify a file as import-ready.
By Hasnain Qureshi / Karachi, working remotely with UK and US teams.
Check current official requirements first
HubSpot’s official import file guidance explains headers, properties and unique identifiers. Its import overview distinguishes creating, updating and associating records. Requirements depend on the objects and operation you choose. Review them in the account before exporting live data. Sources reviewed 5 October 2026.
For this exercise use a simple contacts-only file and map Email, First Name and Last Name to the corresponding contact properties. Download the synthetic contacts example. These example.com addresses demonstrate structure; they are not real recipients or a mailing list.
Run limited local checks
- Load the example in the CSV Cleaner & Import Checker. Confirm three headers and two data records with a comma delimiter.
- Set destination headers to Email,First Name,Last Name. Prepare mapping and inspect every source selection.
- For this example, mark Email as required and select it as the repeated-key check. That expresses the review rule for this exercise, not a universal rule for every HubSpot import.
- Run the check, review output and download a small test file. The checker tests nonblank fields and within-file repeated keys, not email deliverability, custom property types or existing account records.
- In HubSpot, inspect the actual import mode, mapping and warnings. Start with an approved test set; verify which records were created or updated and retain any error report.
Understand common boundaries
| Question | Local checker | Destination review needed |
|---|---|---|
| Are quoted commas and columns consistent? | Structural parser and width checks | Confirm accepted file format |
| Is the chosen email field blank or repeated? | User-selected required/key rule | Choose the identifier for this operation |
| Does this contact already exist? | Cannot check account records | Inspect HubSpot matching and operation |
| Will a field update the intended property? | Exports chosen layout | Review property mapping and allowed values |
Do not collapse account decisions into cleanup
Changing a header does not establish an association. A nonblank email string can still be malformed. A clean file may contain an existing contact that would be updated unexpectedly. Coordinate import permissions, backups and review with the account owner; the browser tool cannot undo a CRM import.
If the workflow repeats, plan custom data import and integration development with explicit source identifiers, destination permissions and recoverable errors. Read the conflicting-ID example before choosing any automated deduplication rule. This page is an independent preparation guide, not a HubSpot affiliation or integration already built into the tool.
Plan a CRM import workflow
Share the current workflow, constraints and desired outcome. We can review scope and agree what needs implementation.