August 14, 2026. HighLevel shipped a HubSpot Importer on August 13, letting agencies connect a HubSpot account and pull contacts, deals, companies, properties, pipelines, stages, notes, emails and tasks straight into a sub-account without CSV exports. The changelog reassures readers that existing matching records are not overwritten. HighLevel's own help documentation, modified August 12, explains what that sentence actually means, and it is not what most people will assume.
What the HubSpot Importer moves
- Records and structure. Contacts, Deals as Opportunities, Companies, contact and deal properties as custom fields, pipelines and stages, custom folders, notes, emails and tasks, per the August 13 changelog entry.
- Not automations. HubSpot workflows and sequences are not on the supported list. HighLevel's help article points anyone with unsupported objects at a separate manual migration guide.
- Still in beta. The changelog reads as a general release. The help article states plainly that the importer is in beta and available only to select users, so the option may not appear in your account.
Not overwritten is not the same as merged
Read the two documents together. The changelog says existing matching records are not overwritten. The help article's FAQ answers the same question directly: imported records are added alongside whatever is already in the account. And the setup instructions go further, telling you to switch on Allow duplicates for both Contacts and Opportunities before you begin, because leaving duplicate blocking on causes a lot of avoidable errors during a HubSpot import.
So the importer does not match and merge. It appends. And the documented happy path asks you to turn off the one control that would have stopped duplicates, then turn it back on afterwards. That is a defensible engineering choice for a bulk import, but it inverts what a migration usually means. If you already ran a partial CSV import into that sub-account, you are not topping it up, you are building a second copy next to it. HighLevel's own first instruction is to use a clean account where possible, and the reason is now obvious.
Three limits that decide the plan
First, an opportunity with no contacts associated to it cannot be imported. Orphaned deals will not arrive, and nothing about the totals screen will make that feel like a loss, so reconcile pipeline value in HubSpot against pipeline value in HighLevel after the run rather than trusting the success count.
Second, imported emails from HubSpot are read only. The history comes across as an archive to search, not a thread anyone can reply into, which matters if you told a client their conversation history was moving.
Third, the file attachment guidance conflicts with itself inside a single article. The limitations section says file attachments are supported for contacts and opportunities. The troubleshooting section says file imports are not supported yet and that any contact or deal with a file attachment will throw an error, with the workaround being to remove the attachment in HubSpot and reattach it manually later. Until HighLevel resolves that, plan for the stricter of the two and test with a record that has an attachment before you commit a real account.
What it means for operators
The importer removes the tedious half of a HubSpot migration and leaves the expensive half untouched. Getting rows across was never what made these projects long. Rebuilding the automations, rewiring the forms and calendars, remapping the reporting and retraining the team is where the hours went, and all of that still has to be done by hand. Price the work accordingly rather than assuming the tool cut the quote.
The safe sequence: test in a fresh non production sub-account first, clean duplicates inside HubSpot before importing rather than after, align every custom field name and label in HubSpot so the key mapping does not collide, run the import, download the error CSV, then reconcile record and pipeline counts against the source before anyone is invited into the account. If you want that run planned and reconciled properly, our GoHighLevel services team does exactly this migration, and you can also hire a GoHighLevel developer to rebuild the workflows the importer leaves behind.
Frequently Asked Questions
No, and that is the point to understand. HighLevel's help article says imported records are added alongside whatever is already in the account. The importer appends rather than matching and merging, which is why HighLevel recommends importing into a clean sub-account.
No. Workflows and sequences are not on the supported object list. HighLevel's documentation directs anyone with unsupported objects to a separate manual migration guide, so automations still have to be rebuilt by hand in HighLevel.
Because leaving duplicate blocking active causes a large number of avoidable errors during a HubSpot import. HighLevel's setup guidance is to switch Allow duplicates on for Contacts and Opportunities for the run, then re-enable de-duplication after the import finishes.
Not yet. HighLevel's help article states the importer is in beta and available only to select users, so the Import from HubSpot option may not appear in your account even though the changelog entry reads as a general release.