Skip to content
Book a build

What are legacy workflows in HubSpot, and should you convert them?

In HubSpot's current documentation, legacy workflows are workflows built in the existing workflows tool. HubSpot lets eligible ones be converted to the new Agent Hub workflow builder, currently behind two betas. Conversion is one-way: triggers, actions and run history carry over and a live workflow keeps running, but version history restarts and you can't edit it in the old tool again.

On this page

What HubSpot supports natively

Workflows tool (legacy)Agent Hub workflow builder
StatusWhere existing workflows liveThe new builder; access through betas
Getting thereAutomation > WorkflowsOpen an eligible workflow, then File > Convert to new builder
RequirementsProfessional or Enterprise; Super Admin or Workflows permissionsThe same, plus two betas: “Meet Agent Builder: a new way to build automations” and “Migrate your legacy Workflow to Agent Builder”

What conversion does, according to HubSpot:

  • It’s permanent. After converting, you can’t review or edit the workflow in the old tool.
  • It doesn’t interrupt a live workflow. A published workflow keeps running.
  • Triggers and actions carry over exactly as configured.
  • Run history is kept; version history restarts. You lose access to earlier versions, so you can’t revert to them.
  • Not every workflow is eligible. If it isn’t, the Convert to new builder option doesn’t appear. HubSpot doesn’t list the criteria.
  • You can preview first before converting.

HubSpot’s conversion article doesn’t give a deadline for the old tool.

How to decide which legacy workflows to convert

  1. Inventory first. Export the workflow list and mark which workflows are active, unused or erroring. See getting a report of all workflows.
  2. Don’t convert what you’re about to delete. Clear out unused workflows before converting anything. See managing unused workflows.
  3. Capture what you’d lose. Version history restarts, so review the revision history of important workflows and note recent changes you might want to revert. A .PNG export or a written description keeps a record of the old version.
  4. Start with low-risk workflows. Convert an internal notification workflow, preview it, and check it behaves the same before moving to lifecycle or routing workflows.
  5. Document each conversion with the date and who did it, alongside your workflow documentation.

Common mistakes

  • Converting to fix a bug. Conversion carries triggers and actions over as they are, bugs included.
  • Converting right after a risky edit. Once converted, you can’t revert to versions from before the conversion, so make sure recent changes work first.

Where Jetstack AI fits

Before a conversion project, a Jetstack AI Workflow Audit gives you the inventory and the dependencies between workflows, so you can convert the ones worth keeping and retire the rest first. It reads both active and inactive workflows and doesn’t change anything in HubSpot. See the Workflow Audit overview.

Sources

Checked October 29, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.

Workflows & automation

See what needs work before you change it.

A read-only Portal Audit and Workflow Audit score the portal, trace dependencies and turn findings into a branded report.

Explore Portal Audit

Workflows & automation

Related questions.

What are legacy workflows in HubSpot, and should you convert them?

In HubSpot's current documentation, legacy workflows are workflows built in the existing workflows tool. HubSpot lets eligible ones be converted to the new Agent Hub workflow builder, currently behind two betas. Conversion is one-way: triggers, actions and run history carry over and a live workflow keeps running, but version history restarts and you can't edit it in the old tool again.

Do I have to convert my workflows now?

HubSpot's conversion article doesn't give a deadline. Conversion needs both betas enabled and only eligible workflows show the Convert to new builder option. Check HubSpot's product updates before planning around a date.

Will converting a workflow stop it running?

No. HubSpot says a published workflow continues running without interruption, and its triggers and actions carry over exactly as configured.