HubSpot Workflows to n8n Migration Playbook

The trigger is almost always the same. Your RevOps lead opens the HubSpot renewal quote, sees the Operations Hub Professional line item at $800 per month, and starts asking whether you actually need it. Then someone counts the active workflows, notices half of them are just reformatting fields and updating lifecycle stages, and the question shifts from “can we afford this” to “why are we paying HubSpot to run glorified if-then logic.” That is the moment teams start looking at n8n. This playbook is for that moment specifically, not a generic intro to workflow automation.

Before You Migrate

The single biggest migration failure I see is teams that export nothing, rebuild nothing in writing, and then wonder why their lead routing broke three months later when someone edits a workflow from memory. Do the boring part first.

Before you touch n8n, complete this checklist:

• Export your full workflow inventory. In HubSpot, go to Automation > Workflows, set the view to All, and export the CSV. Note enrollment trigger type, object type (contact, deal, company), monthly enrollment volume, and whether it touches sequences or email sends.
• Flag CRM-native dependencies. Any workflow that enrolls contacts into a HubSpot Sequence or sends a HubSpot marketing email cannot be fully replaced by n8n. Those actions live inside HubSpot and require HubSpot API calls from n8n, which means you need a Private App with the right scopes.
• Create a HubSpot Private App. Go to Settings > Integrations > Private Apps and generate a token with crm.objects.contacts.write, crm.objects.deals.write, and automation scopes. Store this in n8n’s credential vault, not in a workflow node directly.
• Pause your lowest-risk workflows first. Pick three to five workflows with low enrollment volume and no revenue-critical path (think: field formatting, internal Slack notifications, data hygiene). These are your migration sandbox.
• Document branch logic in plain language. For each workflow, write out the if-then tree in a Google Doc or Notion page before you rebuild. This surfaces logic you forgot existed and creates a QA reference.

What Breaks and What Does Not Transfer

Most of the logic migrates cleanly. The gotchas cluster around a few specific HubSpot-native features that have no direct n8n equivalent.

What transfers well: property-based triggers, time delays, multi-branch logic, internal notifications (Slack, email via SMTP), field updates, webhook calls to third-party tools, and data formatting. I’d argue n8n’s Code node is vastly more capable than HubSpot’s Calculate property action for anything beyond basic math.

What breaks or needs a workaround: HubSpot Sequence enrollment (n8n can call the Sequences API to enroll a contact, but the sequence itself still lives in HubSpot), list-based enrollment triggers (polling workaround below), and HubSpot’s native A/B workflow testing (no equivalent; handle randomization logic in a Code node instead).

The messiest scenario is workflows that both write to HubSpot and enroll into sequences. Those require n8n to make two sequential API calls. Per the HubSpot API docs on sequence enrollment, sequence enrollment requires the contact to be assigned to a user with a Sales Hub seat. If your sequences rely on unassigned contacts, that will surface as an error in n8n’s execution log immediately.

// Workaround: Cron trigger polling a HubSpot list
// In n8n, add a Schedule Trigger node (every 15 min)
// Then an HTTP Request node:

GET https://api.hubapi.com/contacts/v1/lists/{{listId}}/contacts/all
Headers:
  Authorization: Bearer {{$credentials.hubspotPrivateApp.accessToken}}

// Downstream: IF node checks
// "last_processed_at" property vs current timestamp
// to avoid re-processing contacts already actioned
// Store processed IDs in n8n's static data or a
// lightweight Airtable/Notion table as a state store

Verify It Worked

Before declaring the migration done, run through these concrete checks on each workflow:

1. Execution log shows zero errors for 48 hours on production traffic. In n8n, go to Executions and filter by workflow name and status “Error.” Any red rows need investigation before you delete the HubSpot original.
2. Contact properties updated correctly. Pull 10 to 20 recently enrolled contacts in HubSpot and confirm the expected properties were written by n8n (check the property history tab for the “Source” field, which will show “API” instead of “Workflows,” confirming n8n did the write).
3. Downstream tools received data. If the workflow sends data to Clay, Smartlead, or Slack, spot-check those destinations. A webhook that returns a 200 in n8n but silently drops the payload on the receiving end is a real failure mode.
4. Delay-based steps resume correctly. Enroll a test contact that will hit a Wait node, confirm the execution pauses, and verify it resumes and completes the remaining steps after the delay period.

Should you migrate now or stay on HubSpot Workflows?

Choose Migrate to n8n if

• You are on Operations Hub Professional or Enterprise and automation is a meaningful line in the budget
• You need to connect HubSpot to tools HubSpot does not have native nodes for (Clay, custom internal APIs, Postgres, etc.)
• Your workflows are getting complex enough that HubSpot's visual builder feels limiting (nested branches, code-level logic)

From ~$20/month (Cloud) or self-hosted Try n8n →

Choose Stay on HubSpot Workflows if

• Your automation stays almost entirely within HubSpot objects (contacts, deals, emails, sequences) with no external tool logic
• Your team is not technical and the visual builder is genuinely the right tool for the operators running it
• You are on Starter or Professional where the Workflows limit has not become a real constraint yet

Bundled with Operations Hub tiers See HubSpot plans →

The Part No One Talks About: Ongoing Maintenance

The migration is not the hard part. Running n8n in production is. n8n has no built-in alerting on execution failures by default on self-hosted plans. A broken workflow can silently fail for days unless you wire up error monitoring. My read is that this is the single most dangerous gap for teams coming from HubSpot, where failure notifications are on by default. Set up an Error Workflow in n8n (Settings > Error Workflow) that posts to Slack with the workflow name and error message. Do this before you go live, not after something breaks.

For teams also evaluating how automation layering fits into a broader outbound stack, the comparison of Apollo vs LeadMagic vs Clay for data quality is worth reading alongside this, since n8n often becomes the glue connecting those enrichment tools back to HubSpot.

The cost argument is real and the math is not subtle. HubSpot’s Operations Hub pricing page shows Professional at $800/month billed annually as of 2026. n8n Cloud’s Starter plan covers most mid-market workflow volumes at a fraction of that, and the self-hosted option is free for unlimited workflows if your team can manage the infrastructure.