I would find it extremely handy if I could use a pipeline with existing stages to create new pipelin
Comments
-
You can set up an automation to duplicate the deal?
You can create a custom field, change this field, and trigger an automation based on changes to this field.
0 -
Why do you need another pipeline with the same stages @Adina Faiman if your process is the same, would custom fields and filters not be easier for you?
0 -
Mike van der Valk said:
Why do you need another pipeline with the same stages @Adina Faiman if your process is the same, would custom fields and filters not be easier for you?
We prefer to have for each product a separate pipeline.
0 -
Mike van der Valk said:
Why do you need another pipeline with the same stages @Adina Faiman if your process is the same, would custom fields and filters not be easier for you?
@Adina Faiman fair enough, can you explain the reasoning behind it?
0 -
I have same issue, we prefer to have a separate pipeline for territories, and with multiple territories is a tedious work to create pipeline after pipeline with the same stages manually. Would be better if we hade a duplicate pipeline function, and then we can just rename it.
0 -
Luis Ramirez said:
I have same issue, we prefer to have a separate pipeline for territories, and with multiple territories is a tedious work to create pipeline after pipeline with the same stages manually. Would be better if we hade a duplicate pipeline function, and then we can just rename it.
Gotcha @Luis R. Ramirez what's the reasoning why multiple pipelines is more convenient over tagging your deals with the territory and then creating a filter per territory keeping it all in one Pipeline?
0 -
Luis Ramirez said:
I have same issue, we prefer to have a separate pipeline for territories, and with multiple territories is a tedious work to create pipeline after pipeline with the same stages manually. Would be better if we hade a duplicate pipeline function, and then we can just rename it.
the only reason is that we split the REPs per territory and the Visibility Function is very confusing, combined with filters it's a hit and miss. Sometimes you get it right, but most of the time is difficult to fully utilise the functionality of the system. So in this case a work around the technicalities, is replicating pipelines with same stages for different users. Will try your way, but the Visibility function should be easier to handle. It's like an inverse function rather than straight forward.
0 -
Luis Ramirez said:
I have same issue, we prefer to have a separate pipeline for territories, and with multiple territories is a tedious work to create pipeline after pipeline with the same stages manually. Would be better if we hade a duplicate pipeline function, and then we can just rename it.
Sorry to hear about that confusion with the feature usage. Perhaps what you can do is think through how you'd like the system and visibility to be fully set up and reach out to our support team with this. Eventually they can help you out and if you set it up right, it should make life easier with one Pipeline and overview there
0 -
Luis Ramirez said:
I have same issue, we prefer to have a separate pipeline for territories, and with multiple territories is a tedious work to create pipeline after pipeline with the same stages manually. Would be better if we hade a duplicate pipeline function, and then we can just rename it.
We need several Pipelines, that's it. Please stop asking why, can we duplicate existing ones or not?
Thanks
1 -
Luis Ramirez said:
I have same issue, we prefer to have a separate pipeline for territories, and with multiple territories is a tedious work to create pipeline after pipeline with the same stages manually. Would be better if we hade a duplicate pipeline function, and then we can just rename it.
Hi @Pedro
Sorry about that. Currently it's not possible to duplicate.
The reason I asked more clarifying questions is because we don't usually recommend duplicating exactly the same pipelines. This makes your data reside in other places in the app and you might lose track of it and it costs more overhead to keep up to date.
Often people create different Pipelines per team member, geo, industry etc.. However, by assigning ownership of deals to users or adding specific custom fields for geo and industry for example and then using filters you can easily use just one Pipeline and use the filter drop down on the top right to quickly switch between overviews as well as have one shared overview for all your deals, which you won't have if you split it up in different pipelines.
Check here more about custom fields and filters, I hope it helps.0 -
Luis Ramirez said:
I have same issue, we prefer to have a separate pipeline for territories, and with multiple territories is a tedious work to create pipeline after pipeline with the same stages manually. Would be better if we hade a duplicate pipeline function, and then we can just rename it.
Hi Mike,
Don't worry, I know you are here to help, thanks a lot! I will take that into consideration
Cheers
0 -
Luis Ramirez said:
I have same issue, we prefer to have a separate pipeline for territories, and with multiple territories is a tedious work to create pipeline after pipeline with the same stages manually. Would be better if we hade a duplicate pipeline function, and then we can just rename it.
Mike van der Valk
Are there any videos on using custom fields and filters in pipelines and being able to pull reports on those opportunities? Having one massive sales board, doesn't seem to tell me how much I could make on one possible audience.
When my boss and I meet about sales, I want to be able to show him where I am at with a specific audience, so we can dive deeper on what's working and what's not. Where and how can I do that without creating different pipelines?
0 -
Luis Ramirez said:
I have same issue, we prefer to have a separate pipeline for territories, and with multiple territories is a tedious work to create pipeline after pipeline with the same stages manually. Would be better if we hade a duplicate pipeline function, and then we can just rename it.
Here you can learn about custom fields and filtering.
Here you can learn more about Insights reporting, a little piece there is also talking about custom fields.
0 -
Mike van der Valk said:
Why do you need another pipeline with the same stages @Adina Faiman if your process is the same, would custom fields and filters not be easier for you?
This is incredible customer service, not. us: "can we have very simple feature X?", pipedrive guy: "but why do you want that?" You provided the ability to have multiple pipelines, it should be sufficient to just enable duplication of pipelines with their stages unpopulated. It really can't be a big deal to implement and it seems like the reason you're looking for is "it's more intuitive to work like this" as it's the reason I've also ended up reading this because I googled "can I duplicate a pipeline in pipedrive". I'm also a programmer so it's presumably just CreateNewPipeline(somename) and then a for loop to copy the parameters for the stages, surely?
1 -
Mike van der Valk said:
Why do you need another pipeline with the same stages @Adina Faiman if your process is the same, would custom fields and filters not be easier for you?
nb someone actually made a plugin to do this 6 years ago lol
https://www.youtube.com/watch?v=QPHjPrTrCOg
0 -
Mike van der Valk said:
Why do you need another pipeline with the same stages @Adina Faiman if your process is the same, would custom fields and filters not be easier for you?
This really should be a standard feature of Pipedrive. I'm shocked that it is not.
0 -
Is this a feature yet? Can I duplicate a pipeline? What if I want the same pipeline but want to just change one stage, why can I not to that?
Also, the filters for pipelines just are not very good.
0 -
@Erin Schackman @Torq IT @Wendy Keller @Pedro_24658 @Adina Faiman
Here's the workflow using Make/Integromat.
0 -
Unfortunately, the integration is too expensive
0 -
Hi @Erin Schackman - Do you mean the Make/Integromat subscription, or the blueprint for the automation?
0
