Would be great to be able to clone Deal Pipelines or have Deal Pipeline templates as many of our pipelines are similar and now we are manually reacreating pipelines that are simlar or identiacal to other pipeleines.
Totally agree. All of our Sales Pipelines have the same 6 deal stages, so it's just extra work to have to re-create them for each new Pipeline created.
Completely agree with all of this. My pipelines have a lot of stages and automation associated with each stage. I need the same stages and automation for different pipelines because of different types of clients. It would be great to clone a pipeline and it's associated automation rather than having to spend hours manually duplicating the same pipeline over and over.
We have courses that run every month and we have a pipeline for each month, we have to create these all manually and they are always the same with only a tweak in the date, I have searched Google and everything says that this feature is required but does not exist. One post said that there is an idea here but that URL does not exist. This is a feature that seems like a no brainer 🙂
I'm a crm veteran who just started using Hubspot. It is pretty impressive, but I seriously am really surprised that you can't duplicate a pipeline. Definitely +1 for this request!
You can do this via the workflow tool. I was previously doing it via the API, but its actually pretty easy to clone a deal (for ex. create a "duplicate this deal" field and then set the workflow criteria to kick-off when the value of that field is "Yes." The workflow actions are then to create a new deal and copy fields from the original deal to the deal that is created. You can do it all through the GUI interface. When you create the new deal set the "duplicate this deal" field to "No" on the deal that is created.
@zbelcher I want to clone the whole pipeline with all the stages and workflows, not the individual workflows within the stages. We have long pipelines which are similar in many stages but have significant differences. It is a real pain to rebuild the entire thing.
Really this would be valuable on any feature, be it individual record, pipeline or workflow. From the record side, it would be a great way to copy over historicals to a new database schema (say you're updating your pipeline process while the legacy version is still being utilized during transition) while maintaining data integrity in the legacy system.
