HubSpot import guide
HubSpot import date format errors
HubSpot date properties are a common failure point during CSV imports. Use one of the formats HubSpot accepts at mapping time, and clean up spreadsheet-only date values before upload.
What the error means
A HubSpot date import error means a date value in your CSV does not match the date format selected during HubSpot's import mapping step. Platform research for ReadyCSV found dates to be a top community-reported import failure source.
HubSpot accepts date values when they match the mapping choice: MM/DD/YYYY, DD/MM/YYYY, or YYYY-MM-DD. Do not assume HubSpot will understand every date that Excel or Google Sheets can display.
Why HubSpot rejects it
Spreadsheet tools often store and display dates differently from the raw CSV text. Values like Excel serial numbers, written-out dates, or dot-separated dates can look understandable to a human but fail HubSpot's import parser.
- Excel serial numbers such as
45292are spreadsheet storage values, not HubSpot date strings. - Written-out dates such as
January 31, 2026are not one of the three accepted CSV formats. - Dot-separated dates such as
31.01.2026may be common locally, but they do not match the listed HubSpot formats.
How to fix it manually
Pick one date format and make the entire column consistent before importing.
- Decide which HubSpot mapping format you will use: MM/DD/YYYY, DD/MM/YYYY, or YYYY-MM-DD.
- Convert every date-like value in the CSV column to that exact format.
- Replace Excel serial numbers with real calendar dates.
- Replace written-out month names with numeric dates.
- Review a few rows manually after export to confirm the CSV text is what you expect, not just the spreadsheet display.
How ReadyCSV catches it locally before import
ReadyCSV flags date-like HubSpot columns when values do not match MM/DD/YYYY, DD/MM/YYYY, or YYYY-MM-DD. The warning calls out Excel serials and written-out dates as review risks before you upload to HubSpot.
The check runs locally in your browser against the current working copy. ReadyCSV does not upload your CSV, send date values to a server, or call AI to inspect the file.
Related HubSpot import guides
HubSpot invalid email import error
Understand INVALID_EMAIL, INVALID_DOMAIN, duplicate emails, and additional email address imports.
HubSpot lifecycle stage import error
Check lifecycle stage and lead status values before HubSpot rejects an import row.
Check your CSV before importing
ReadyCSV preflights HubSpot contact CSVs locally in your browser. Your CSV contents stay on your device: no upload, no account, no AI calls, and no license server call for local checks.
It is still your responsibility to review every finding, cleaned export, Issue Report, and HubSpot import setting before importing. ReadyCSV cannot guarantee that HubSpot will accept every row.
Open ReadyCSV local preflight