Offer the option to clone a workflow and change the object type

I want to clone a Companies workflow so that I can apply it to Contacts. It was quite an involved workflow (basically setting out all the US state codes and saying if State/Region was in code format, change it to the appropriate non-code format). I want to now do the same with the Contacts’ State/Region fields but there is no option to clone it and then change to Contacts - I’m going to have to recreate the entire thing.

It would save a lot of time and effort if we had the option to change the object!

It would be very useful to have the same possibility also between contact - based workflows and deal based ones.

Yes. This would be a time saver if you worked an hour on a workflow only to discover that the object it’s based on was wrong from the start. Doh!

Alternative could be cloning the components of workflow through the different workflows. This is really crucial for marketing automation.

Agree, we’d also need to clone from Contacts to Deals. We categorize countries into sales regions so it’s a lot of work to create a branching structure.

This would be a super time-saving and useful feature.

I wouldnt’ even categorize this as an idea - it’s a critical and necessary feature. I’m about to redo my work - it’ll take me probably 6 hours - which costs our company thousands of dollars - because I have to redo every single workflow. Big, big issue.

Agree this is a critical requirement to save a LOT of re-work!

This would be a time-saver from re-creating the workflows just to change the object type.

+1!

Would love to see this feature implemented, would save a lot of time.

+1 this would be a huge time-saver

This will be a great improvement and will save us time.

This is a huge one. We have clients who build massive workflows and then we need them to be on another object and we spend hours rebuilding the workflow.

This is the exact workflow I am building! It would be beneficial to be able to clone a workflow but change the primary object during the cloning process. Obviously, if the trigger conditions/properties didn’t exist in the new object this would be an issue but it should either only not be allowed in that scenario or, more usefully, just have an error if that were the case.

1000% Need this

I have a workflow to clean up typos made when entering a State. This means I have 50+ branches (including Canadian Provinces) and each of those branches has a filter for State equals PA, PA. P.A., Pensylvania, Pennslivania, Pennsilvania, Penn, Penns, and so on for as many typos as you can think of. I have to then repeat this process for every state and every province.
Currently, this workflow exists on my Contacts object and, as you can imagine, took a lot of time to create and set up. I now have this issue on my Companies object and need to clean up the states, but I’m not able to duplicate this workflow, despite EVERYTHING in it being set up identically.
I’m not going to have to spend hours recreating a workflow that already exists because I’m not able to just copy it and keep moving.

I’ve encounted this in NUMEROUS situations and chat support just keeps telling me to post in the Ideas Forum, where the issue can continue to be ignored.
SO, I’m posting here, and I’m posting in the following threads:

I will comment and upvote on all related threads and recommend you do so as well to reenforce to HubSpot how serious the need for something like this is.

I waste a lot of time doing and re-doing things that HubSpot should support me on instead of forcing me to waste valuable work day hours. No one at my company is happy with the fact that I am spending so much time doing menial work that a platform as “advanced” as HubSpot should be able to facilitate.
I would wager spending more time on QOL updates for existing customers rather than developing and pushing new AI features would be a more worthwhile venture, but I imagine that won’t make as much money so existing customers with issues will continue to be ignored.

This would be super imporant to have in the future saves a lot of manual effort!

+1 for my customer! especially when the customer wants to create a similar large workflow for another object type, having to manually re-create the workflow can be really tedious :disappointed_face: