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.
Hi all, thanks for sharing your feedback. I'm seeing two different requests in the comments:
Ability to clone a pipeline
Ability to clone a record (i.e. deal)
For the first one (original idea), I'm curious to understand why you'd want to clone a pipeline. If you have two pipelines with the exact same stages, we don't recommend separating the pipelines, as outlined in this Knowledge Base article. That's the best practice for segregating pipelines, especially if you want to avoid hitting your pipeline limit.
@DCL Thanks for your follow up! There are a few important things to consider here:
1. Things that seem easy may not be. There may be downstream implications in other part of the product or unforseen technical challenges to work through. 2. There are a certain number of resources available to all of us (engineering, hours in a day, etc.). In order to be effective we need to increase focus on the work that benefits our customers most. There are hundreds of ideas on the forum worthy of consideration, but in order to build a great product we cannot work on all of them. 3. For everything we add to HubSpot, we are adding to the list of things our customers need to understand to use the system. With this comes an increased maintenance cost.
It's not that this idea will never be delivered. Instead, I wanted to be as transparent as possible that this is not something we plan to deliver in the immediate future.
Thank you as always for your continued feedback, it helps us build a great product.
We are constantly evaluating and re-evaluating our priorities and roadmap to deliver as much value to our customers as possible. At this time cloning a pipeline is not something our team is currently planning to build natively into HubSpot. This is certainly subject to change in the future and we will update this idea if that becomes the case.
We want our active pipeline to show only deals that will close in the current year.
Currently we have "holding tank" stages because these deals are not lost, they are just "not now" and we want to clear out these stages without losing the deals that are leads for next year. I have been asked to create a Future pipeline and it would be really helpful to just clone our current pipeline as the process will be the same but just for next year so not a focus currently.
Referring to your question regarding 1. "Ability to clone a pipeline", I can answer from our perspective:
Our business model is a "Seller-Agent" model - a bit like the business model of a real estate agent that is selling different houses. Think of the individual house as the "pipeline" and the interested house buyers as "deals".
To sell House A, we set up Pipeline A where we track all potential buyers as deals. Naturally, we want to provide the seller of House A with frequent updates about how the sales process of his/her house is going.
For House B, we need a Pipeline B, with exactly the same stages, but with different deals (i.e. only buyers interested in House B).
From that perspective, setting up Pipeline B is much easier if I can just "clone" Pipeline A with all the same stages and properties (but without House A deals, obviously).
So what we have is 1 pipeline per house we sell and 1 overarching "housing pipeline" where we track the stage of the different housing sales process. Happy to demo you this example in our hubspot.
This works great with the caviat that after 14 houses sold, we will run out of pipelines (and will have to come up with a new solution. (Given the fact that our model entails that eventually House A is sold (and thus Pipeline A isn't used anymore), it would be great to be able to archive Pipeline A.)
Hope it helps to understand OUR usecase. There might be others.
I would of course be interested: do you see a better way for a setup of such a seller-agent model?
The clone option is available in almost every other area of Hubspot seems like it should be a basic functionality for deal pipelines. My business has to have 5 seperate pipelines, all of which have similar settings and requirements, but have slightly varying deal stages. That being said, being able to duplicate a pipeline would be a major time saver, as instead of having to customize the required fields for each stage, the card and board previews, and the permissions sets, I'd only have to change the deal stages that vary for the new pipeline.
This lack of basic functionality adds a significant chunk of time to system admins' workload while proving to be incredibly redundant.
@JeannieN Here is a use case for pipeline cloning. We use the pipeline feature to manage events. We create a temporary pipeline prior to events and use it as a temporary lead management tool where stages are pre-event, during event and postevent. Once the event is done and all real opportunities are transferred to our main pipeline, we kill that pipeline.
We are open to use other features to manage the events we go to, but so far, this is the best way we found so far and the team really enjoys it as it gets them focused in these fast paced clients meeting events.
Hey @JSPrenovost , referring to your comment. I believe what you are running is a so called "seller-agent model". We have the same model, albeit not in event management.
I would be interested to know what you're setup is. When you say "kill that pipeline" do you mean "delete"? Do you mind losing all the history for those past events? (Or do you export the data to excel?)
Also interesting to know might be that @RQuinn9 was recommended to me by @JeannieN as he seems to have set up a way to run a seller-agent model with Hubspot somehow that works well. However, I haven't been able to get a hold of him yet. Maybe you want reach out to him as well...
@swissventures , we do delete the pipeline after moving all relevant information in our main pipeline(creating real deals in our pipeline, the rest are just contacts we haven't seen or talked to, so it has no real value for us.) That said all other object information are still collected(contact info, notes, etc). Otherwise, we would hit our pipeline limit and it also creates noise in our CRM.
I will look into an alternative/optimized solution once our next event is done at the end of the month.
Being in this discussion for about 4 years now and seeing that the input by Hubspot into this topic is rare, even not existing. I have come to the conclusion that it is impossible to "clone" a pipeline, simply software-wise. On the surface cloning is a simple idea. However "simple" it is not considering, what may or not may be the content of a chosen pipeline, when it comes to workflows. We know that a workflow may be a standalone "function" with or without a working pipeline. Plus we have (small) workflows that are considered being part of a pipeline because that workflow was created within the pipeline, while building the pipeline. Such (small) workflows are visible on the pipelines "automation" view, whereas "real" (standalone) workflows are not. Imagine to clone a pipeline that contains both variants of such workflows (visable - not visable in pipeline automation view).
What makes me sad, is that hubspot does not address this topic in a professional manner, and tells us -the daily users-, WHY them do not implement that cloning feature.
@JeannieN Regarding your question about our use cases. I am very sorry to write this, really am, but I have to: It is not professional from your end (not yours personnally, however hupspot's) to ask paying users for their use cases. We -as users- know (in general) what we "want" to do, yet we (sometimes) do not know "how to". Which extra information do you need to understand that. Naming use cases (most of them being pretty individual) is a dead-end-road. My guess is there a thousands of reasons, why to clone a pipeline, you could as well ask us, "why do you want to clone a workflow, give us a use case."
Debe ser un usuario registrado para añadir un comentario aquí. Si ya está registrado, inicie sesión. Si todavía no está registrado, hágalo e inicie sesión.
