HubSpot import: "Could not parse date"
HubSpot's own troubleshooting guide names “Could not parse date” as an import error, shown when a value in a date-mapped column does not match the date format you selected during import. HubSpot's own wording is blunt about what happens next: “The affected records were imported, but the date property does not contain a value” — the row goes in, the date is simply missing, and nothing in HubSpot's interface calls it a rejection.
Built for anyone preparing a contact or company file for HubSpot or Salesforce — sales operations, RevOps, and agencies migrating a client's data.
Read from HubSpot's own Knowledge BaseHubSpot Knowledge Base — knowledge.hubspot.com, read 13 September 2026.
What this error means
When you import a file into HubSpot, you choose the date format the file uses before the import runs. A cell that does not match that format — a stray note, a placeholder, or simply a typo — is not rejected along with the rest of the row: the contact is created, and the date property is left blank instead. The row you meant to carry a date now carries none, and HubSpot's own import summary does not call this out as a per-row error you would notice.
What causes it, and what our engine actually checks
CRM Import Check's dateUnparseable rule reads every cell in a date-mapped column and flags any value it cannot read as a date at all, in any shape the tool recognises — the same failure that leaves HubSpot's date property blank. A second rule, dateInconsistent, checks something HubSpot's own error message never mentions: whether the column's dates are even written the same way as each other. A column that mixes “15/01/2026” with “01/15/2026” has no single format to select in the first place, which is exactly the setup this error grows out of.
What the engine found in a sample file
One row in a five-row sample carried “N/A” in the Create Date column — not a date in any shape — and the engine flagged it as dateUnparseable, a blocker: that is the exact row HubSpot would import with a blank date property. The same column mixed two different day/month orders across its other rows, which the engine separately flagged as dateInconsistent, a warning — the column has no single format for an import to select in the first place, which is the condition this error grows out of.
dateUnparseableBlocker4“N/A”
dateInconsistentWarningBlocker stops the import outright, or lets it through with data silently lost. Warning usually gets through but is worth checking before you trust the numbers. Notice is informational — safe to leave, safe to clear.
Reproduced from a sample file — read September 13, 2026.
Check your own file for this
Drop the contact file you were about to import into HubSpot below. It is read in this browser tab, the same engine runs the same check, and you will see immediately whether it carries an unparseable or inconsistent date.
CSV, TSV or Excel, up to 20 MB
How to fix it by hand
Filter the date column for any cell that is not a recognisable date — a placeholder, a note, or a value in a different shape from the rest of the column — and correct it from the record's original source before you import. If the column mixes day-first and month-first dates, settle on one format for the whole column first: HubSpot can only be told one format per import, and a column that disagrees with itself will always leave some rows with a blank date.
Frequently asked questions
- What does HubSpot's "Could not parse date" error mean?
- It means a value in a date-mapped column did not match the date format you told HubSpot to expect for this import. HubSpot does not reject the row: it imports the contact anyway and leaves the date property blank, with nothing in the import summary calling out which row it happened to.
- Why is this worse than a normal rejection?
- Because nothing tells you it happened. A rejected row shows up in HubSpot's own error count; a row with a silently blank date looks like a success. CRM Import Check flags the exact cell before you import, rather than after, when the only sign is a property that quietly has no value.
- Can CRM Import Check fix an unparseable date automatically?
- No — inventing a date would be a guess, and this product never guesses a value into existence. It names the exact row and cell so you can correct it from wherever the record actually came from.
What CRM Import Check does with this file
Upload a file carrying this problem into CRM Import Check and it lists every cell it cannot read as a date, by row, before you import anything — the same cells HubSpot would otherwise import with the date silently missing. It also tells you when a column's dates are not written consistently, which is not something HubSpot's own error message surfaces at all.
The file you'd check is read in your browser tab — it is never uploaded anywhere.
What it cannot do here
The tool cannot tell you what the missing date should have been — that answer only exists in whatever record the row came from. It also cannot pick the correct reading of an ambiguous date like “03/07/2026” for you; it can only tell you the column is inconsistent, which is the fact a person needs to choose the right import format.