Could it be possible to export or archive our old sales pipelines without having to delete them? Having multiple pipelines (from past years) could be confusing for our sales team.
Although we want to keep them for archive purposes.
It would be great to retain a pipeline in the system for data/reporting purposes, but agree that there should be a way to differentiate active pipelines from inactive pipelines to make it easier for sales to do their jobs without risk of error or rework.
Was disappointed to learn this isn't possible! We have a few pipelines that are no longer being used but we would like to still have access to the archives if needed for future reporting. I hope you will consider making this change!
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). And so on...
Current Solution (how we use Hubspot today)
We have 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 (without loosing the history). When we sell House A, we no longer need Pipeline A, but want to keep the history for future reference (e.g. the use case being a bit like "remember the house C we sold in 2022 - let see who was interested in the house back then but didn't get to buy it and contact them again about house X".
Problem:
1. Today, we cannot "archive" a Pipeline, only "delete" it. This way, after 14 Houses sold (assuming we use one Pipepline as a "Master Pipeline" where each deal is one house (A, B, C, D,...)), we either need to start deleting Pipelines (in which case we loose the history - not an option), export the data before deleting (kind of missing the point of having a CRM), or upgrade to Enterprise (but besides being more expensive and cluttering the pipeline list we'd have the same problem again after 100 pipelines.)
2. Today, when we want to create a new pipeline for a new house, we need to configure the pipeline from scratch (e.g. create the pipeline stages, deal tags, etc.)
Expected Behaviour
1. If it were possible to archive a Pipeline with all deals in it, it would be possible to keep the "pipeline" history while staying below 15 open pipelines.
2. Setting up a new Pipeline B (for House B) with the same pipeline settings like Pipeline A is much easier if I can just "clone" Pipeline A with all the same stages and properties (but without House A deals, obviously).
I don't understand the reluctance to allow for cloning of pipelines
We're in the roofing business, and handle our pipelines by year, since some projects are quick, and others are sold in one year and drag on through multiple years (large condo projects)
Some prospects begin one year and then get stuck - not lost - and actually begin the next year or even a few years later.
For those instances we move the deal to the current year pipeline.
Our reports are cleaner, and everything is more organized when you separate deals by year in different yearly pipelines.
So frustrating they won't give us that. I have to manually make the pipeline, and all the properties, all the required fields - numerical, text, date, etc. And then repeat it every year.
Seriously tedious to the point some years are melded together.
I summarized the requirements for this feature together with some practical use cases here to give the Hubspot Product Owners some more meat to the bone:
