Hi
Im trying to import data but its coming up with errors on the note body, I selected the Contacts, Companies and Notes properties.
When i import, its showing the following error:
When i go to the section, the cells that dont have notes in them seem to be causing an error.
I have tried to select ‘dont import this value’ on the Empty Values, but that doesnt work.
When i look at the notebody property it looks like there is an error there too. Not sure if this is related
Any help/suggestions would be great - at a bit of a loss on this one
Hi @AGibson0 , you’re running into a very specific limitation of how HubSpot treats Notes during imports, and the screenshots you shared actually tell the whole story.
A Note is not a normal CRM object like contacts or companies. For a note to be created, Note body is a required field, and HubSpot will not create a note record at all if that value is empty.
That’s why rows with blank cells are failing, even if you select “don’t import this value.” For Notes, “empty” doesn’t mean “skip,” it means “invalid,” so those rows are rejected outright (Import records for multiple objects )
This also explains why mapping Contacts + Companies + Notes together is tripping you up. If a row has contact/company data but no note body, HubSpot still tries to create a Note for that row, sees the missing required value, and throws the error. The import tool doesn’t conditionally create notes per row.
The property screen you showed with the object type error is a red herring. hs_note_body is a system engagement property, not something you should recreate or edit. Notes don’t have a selectable “object type” the way CRM objects do, and trying to define one manually will always fail. That part isn’t the cause, but it’s a good sign to stop touching that property entirely.
The clean fix is to split the import. Import Contacts and Companies first without Notes. Then run a separate Notes-only import that includes only rows where the note body is populated and properly associated (contact email, company domain, or record ID). Alternatively, if you must keep it in one file, filter out rows with empty note cells before importing notes. Once you do that, the errors should disappear immediately. You weren’t doing anything wrong; this is just one of those sharp edges in HubSpot’s import model. Hope this helps.
Thank you very much - is this really helpful. Will do the seperate import
Hi @AGibson0,
In a previous step you “told” HubSpot to create notes - so HubSpot is now expecting that note body here. If that is missing, you could do two things:
- If the import wizard lets you proceed, proceed. You’ll get errors where HubSpot cannot create a note - but that is fine.
- Split your import file in two (one with notes, one without) and import them both, the latter without selecting the note data source of course.
Best regards
Thank you, will seperate them out
