Fix HubSpot field mapping problems before import
HubSpot mapping problems often start before the mapping screen: inconsistent headers, missing identifiers, extra sheet structure or values that do not fit the destination property.
Start with the file structure
HubSpot requires a supported spreadsheet or CSV, a single sheet, and a header row whose columns can be mapped to HubSpot properties.
What ReadyRows checks
ReadyRows normalizes common contact headers, detects duplicate or blank headers, converts multi-sheet XLSX input to a single analyzed sheet for CSV export, and proposes a mapping plan for built-in and likely custom properties.
Identifiers matter when updating
For updates and associations, HubSpot relies on unique identifiers such as Record ID, Email or Company domain name depending on the object. ReadyRows warns when a contact file has no strong deduplication identifier.
Official reference
HubSpot documents the relevant import rule in its import file formatting guide.
Check the file before you re-import it
ReadyRows scans the file locally in your browser, highlights platform-specific import risks and separates rows that need attention from rows that are ready to export.
Open the free HubSpot fixerReadyRows is an independent tool and is not affiliated with HubSpot. Import rules can change; confirm account-specific behavior in the platform's official documentation.