Still no reply by HubSpot to my content…
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.”