2 Accepted solutions
Hi @robinfvh 👋 Thanks for your suggestion. The most direct way to get this in front of the Product Team is to submit this to the HubSpot Ideas Forum. — Jaycee
Hi @robinfvh , you’re not missing anything. As of today, HubSpot still doesn’t offer a native “clone deal with line items” workflow action, and that limitation is very real if you rely on line items for ARR tracking.
The reason your “create deal” workflow falls short is structural: workflows can copy deal properties, but line items are separate CRM objects with associations, and HubSpot doesn’t expose a built-in action to replicate those associations. Manual cloning works because the UI handles that logic behind the scenes, but workflows don’t.
There are three practical workarounds I’ve seen teams use successfully:
One is a custom code workflow action that fires on deal close, creates a new deal via the API, then fetches associated line items from the closed deal and re-creates them on the new one. It’s not pretty, but it’s reliable, and it’s the closest thing to “native automation” today (https://developers.hubspot.com/docs/api/crm/line-items).
Another is rethinking the model slightly and using subscriptions or recurring revenue properties for ARR instead of cloned deals, if your use case allows it. This avoids duplication entirely and often simplifies reporting (https://knowledge.hubspot.com/reports/track-recurring-revenue-with-revenue-analytics )
Finally, if renewals are the driver, some teams keep a single long-lived deal and version the revenue via line items over time rather than cloning the deal itself.
You’re absolutely right to submit this to the Ideas Forum. This comes up a lot in RevOps teams doing renewals or expansions, and it’s one of those gaps where the product UI is ahead of workflows. If ARR accuracy is critical, custom code is unfortunately the cleanest option for now.
Did my answer help? Please mark it as a solution to help others find it too.
 | Ruben Burdin HubSpot Advisor Founder @ Stacksync Real-Time Data Sync between any CRM and Database |
 | |
Hi @robinfvh , you’re not missing anything. As of today, HubSpot still doesn’t offer a native “clone deal with line items” workflow action, and that limitation is very real if you rely on line items for ARR tracking.
The reason your “create deal” workflow falls short is structural: workflows can copy deal properties, but line items are separate CRM objects with associations, and HubSpot doesn’t expose a built-in action to replicate those associations. Manual cloning works because the UI handles that logic behind the scenes, but workflows don’t.
There are three practical workarounds I’ve seen teams use successfully:
One is a custom code workflow action that fires on deal close, creates a new deal via the API, then fetches associated line items from the closed deal and re-creates them on the new one. It’s not pretty, but it’s reliable, and it’s the closest thing to “native automation” today (https://developers.hubspot.com/docs/api/crm/line-items).
Another is rethinking the model slightly and using subscriptions or recurring revenue properties for ARR instead of cloned deals, if your use case allows it. This avoids duplication entirely and often simplifies reporting (https://knowledge.hubspot.com/reports/track-recurring-revenue-with-revenue-analytics )
Finally, if renewals are the driver, some teams keep a single long-lived deal and version the revenue via line items over time rather than cloning the deal itself.
You’re absolutely right to submit this to the Ideas Forum. This comes up a lot in RevOps teams doing renewals or expansions, and it’s one of those gaps where the product UI is ahead of workflows. If ARR accuracy is critical, custom code is unfortunately the cleanest option for now.
Did my answer help? Please mark it as a solution to help others find it too.
| | Ruben Burdin HubSpot Advisor Founder @ Stacksync Real-Time Data Sync between any CRM and Database |
| | |
Hi @robinfvh 👋 Thanks for your suggestion. The most direct way to get this in front of the Product Team is to submit this to the HubSpot Ideas Forum. — Jaycee
