n8n to HubSpot
Workflow automation platform, self-hosted or cloud, that links apps through nodes, webhooks and HTTP calls. Here it is the integration layer around a CRM, not the system of record.
n8n data can move into HubSpot, landing mainly in Data Hub. 0 of 5 mapped objects move directly; 4 items need manual work and 3 do not move. Plan roughly 1-2 weeks for a small move and 6-12 weeks for a large one.
Migration checklist for n8n
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
1-10 workflows
Mostly simple syncs.
Mid migration
10-50 workflows
Some routing logic and a hybrid setup.
Large migration
50+ workflows
Enterprise orchestration, with ETL kept outside HubSpot.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves n8n: what you need to get in, what lands in HubSpot, and what will not.
REST (public API, v1) plus server CLI and n8n CLI
An n8n API key from Settings > n8n API, or shell access to the host for the server CLI. The base URL differs for cloud (<name>.app.n8n.cloud/api/v1) and self-hosted.
Server CLI needs shell or database access to the host. API access is limited by the key's user permissions and, on Enterprise, its scopes.
Choose your route
How will you move the data?
HubSpot offers an integration for importing records from n8n.
- You need: An n8n API key from Settings > n8n API, or shell access to the host for the server CLI. The base URL differs for cloud (<name>.app.n8n.cloud/api/v1) and self-hosted.
- Permission: Server CLI needs shell or database access to the host. API access is limited by the key's user permissions and, on Enterprise, its scopes.
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- Workflow JSON export from the editor, or import via file/URL/copy-paste
- Server CLI: n8n export:workflow –all and n8n export:credentials –all
- Public REST API: list workflows and credentials with an API key
- Server CLI export also covers database entities
Limits: To confirm
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 6-12 weeks, usually phased.
Talk to a partnerWhere each object lands
In n8n
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Workflows using HubSpot nodes (CRM sync, routing, enrichment) | Custom objects | manual | Exported workflow JSON is a specification to rebuild as HubSpot workflows, not an importable asset. The label 'Custom objects' is a placeholder, since there is no HubSpot object for workflow definitions. |
| Field mappings inside HubSpot node steps | Contacts | manual | Mappings can be read from the JSON and recreated as property mappings or workflow actions. The HubSpot node covers contacts, companies, deals, tickets, engagements and lists. |
| Deal and company sync rules | Deals | manual | Companies follow the same pattern. The node supports create, update, get, search and delete operations on both. |
| Ticket automation | Tickets | manual | Rebuild as ticket workflows. The node has ticket CRUD operations. |
| Webhook/HubSpot Trigger event flows | Contacts | manual | Rebuild as workflow enrollment triggers, or keep n8n for non-CRM steps. |
What to expect
Not part of the workflow export; HubSpot has no equivalent for it. Not confirmed in the docs I checked.
Workflow JSON holds only credential names and IDs. Credential export is a separate CLI step, and the secrets would be visible in the output.
These have no HubSpot workflow equivalent, so keep them in n8n or another orchestrator.
Workflows are the only migratable asset, and each needs a decision.
The HubSpot node uses its own credential, and the trigger may need a separate one.
There is no automatic conversion from n8n JSON.
HubSpot allows only one webhook at a time per the n8n trigger docs, so activating a second trigger breaks the first.
Export only what you need, encrypt the files and rotate keys afterwards.
Change or delete IDs before importing into another instance.
Switch off each n8n workflow as its HubSpot replacement goes live.
Scrub the JSON before sharing it.
Version-control the property map and test after each schema change.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
Export paths and the API key auth are backed by n8n docs, and the HubSpot node is documented. n8n holds workflows, not CRM records, so the object mapping is analyst-level. Rate limits, certifications and residency were not researched.
Sources
Related migrations
Frequently asked questions
How do I migrate n8n to HubSpot?
1. List all workflows through the public API (GET /workflows) or the n8n export:workflow –all CLI command. 2. Tag each workflow by whether it touches HubSpot, the CRM being replaced, or non-CRM systems. 3. Create the API key with a label and an expiry, using enterprise scopes if available. 4. Record the credential names and IDs that each workflow references.
What does not move from n8n to HubSpot?
Execution history and logs, Stored credential secrets and Complex ETL, code nodes and non-CRM workflows. Plan to rebuild or retire these.
How long does a n8n to HubSpot migration take?
Small (1-10 workflows): 1-2 weeks. Mid (10-50 workflows): 3-6 weeks. Large (50+ workflows): 6-12 weeks. These are planning estimates, not a quote.
What access do I need to export from n8n?
An n8n API key from Settings > n8n API, or shell access to the host for the server CLI. The base URL differs for cloud (<name>.app.n8n.cloud/api/v1) and self-hosted. Server CLI needs shell or database access to the host. API access is limited by the key's user permissions and, on Enterprise, its scopes.
Is there a native HubSpot connector for n8n?
Yes. Confirm the supported objects in discovery.
What compliance issues apply when moving n8n data?
Check: Workflows may carry health, financial or minors' data, depending on the connected systems.. Agree consent, retention and access rules before exporting.
Moving n8n into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner