Hi everyone,
We recently ran into a very frustrating issue with HubSpot’s blog import tool, and I wanted to check if anyone else has experienced this, and also to highlight the need for improvements from HubSpot.
When importing a CSV of blog posts, HubSpot deleted some of our existing pages without any clear warning. Specifically:
If the import contains a URL that conflicts with an existing page, HubSpot deletes the existing page (including all its multi-language variants) before creating the new one.
This triggered a cascading deletion of secondary language posts when the primary post was replaced.
There was no explicit conflict warning during import. We only discovered this after realizing our content had disappeared, forcing us to manually recreate several pages.
Unfortunately, HubSpot Support confirmed that analytics data from the deleted pages cannot be recovered.
We’ve been in back-and-forth conversations with HubSpot Support and Dev teams. While they acknowledge this is “working as designed,” they also admitted the messaging is unclear and there are no safeguards or conflict checks built into the import process right now.
This raises a few concerns:
Why isn’t there a visible warning or preview when conflicts are detected during import?
Why does HubSpot allow cascading deletions of language variants without user confirmation?
Shouldn’t analytics and historical data at least be preserved or restorable?
At the moment, this behaviour is not treated as a bug by HubSpot, but in practice, it feels like one, and it creates unnecessary risk for anyone working with multi-language blogs and imports.
👉 Has anyone else in the community faced this issue? How did you handle it?
👉 I’d really encourage HubSpot to add stronger safeguards, conflict checks, and recovery options to the import tool to prevent others from going through the same experience.
Thanks in advance for your input,
Ahmed Jamal Tariq
Marketing Coordinator @ iGoMoon AB
