Support for Multiple Pipelines on One Object (Record Types)

[oddieis]

Scope & Context

We would like to request improving opportunity management in Twenty CRM.
The ticket is about enabling different opportunity pipelines, allowing users to define distinct sets of stages based on the opportunity type.

Current behavior

Currently, all opportunities follow a single, fixed set of stages.
Many CRMs allow users to define multiple pipelines with different stage progressions that align with different types of opportunities.
Since users cannot currently define separate pipelines in Twenty CRM, they are forced to find workarounds.

Additionally, users cannot hide the standard Opportunity object, meaning they must work within its constraints rather than defining custom pipeline types.

Expected behavior

Users should be able to create multiple opportunity pipelines, each with its own set of stages.
When creating an opportunity, users should be able to select a pipeline that determines the opportunity's progression.

For example:

• A new customer opportunity follows an onboarding flow with specific stages.
• A prospective customer for Product A follows a different sales process with unique stages.
• A new partner follows an entirely separate partnership approval process.

Each of these scenarios should be supported by separate pipelines with their own custom-defined stages.

Technical inputs

• Modify the opportunity model to allow multiple pipelines with distinct stage configurations.
• Create an interface for defining and managing pipelines.
• Update the opportunity creation flow to allow users to select a pipeline.
• Ensure that opportunities follow the correct pipeline with appropriate stage progression.
• If possible, allow users to hide the standard Opportunity object if they prefer to use custom pipelines.

[Bonapara]

What you could do as a workaround:

• Create a different Select field with your Pipeline2 steps
• Create a second filtered view filtered on the values contained in this select
• Hide the pipeline 1 select values

We will work on a more robust solution mid-term.

[merrime-n]

We need conditional field accessibility and field groups too.

This is a game changer for custom data objects. I can think of (and actually I currently encounter) various scenarios were a dynamic (conditional) field can help. For instance, if there's a hierarchy in the organization and we create a Select field for Departments, we definitely have to create another Select field named Teams that needs to be populated according to the selected Department. And it needs some kind of Dynamic dropdown.

In SuiteCRM, they are handling this behavior by requiring the exact option prefixes as the higher-level field ID (or key). For further information, I suggest you take a look at the comment explaining this feature under a forum post.

[oshliaer]

We will work on a more robust solution mid-term.

I hope that I will have the opportunity to migrate =)

In my main case I am faced with a choice: to operate as an entrepreneur (all in one workspace) or to create several TwentyCRM workspaces. The second idea does not seem so strange. But each workspace for one papline is a bit confusing.

[pedrotalaia]

Hello @Bonapara
Actually I'm integrating TwentyCRM into a customer and I can't seem to find any more info on the multi-pipeline and setting new stages.

Is this the only possible workaround for now?

Just to be clear, I'm using this for a couple of days, in order to do this:

• Create a different Select field with your Pipeline2 steps
• Create a second filtered view filtered on the values contained in this select
• Hide the pipeline 1 select values

I need to change the data object model on the Settings to create a new field to use the pipeline fields?

[Bonapara]

Yes—your current workaround is the way to go right now. You’ll need to add a new field in Settings (data model) to represent the second pipeline’s stages, then use filtered views and hide the original pipeline field as you described.

[oshliaer]

Yes—your current workaround is the way to go right now. You’ll need to add a new field in Settings (data model) to represent the second pipeline’s stages, then use filtered views and hide the original pipeline field as you described.

The system offers a very tight connection for the first pipeline, with no editing options in the default setup. How tight is this connection? Is it possible to ignore the default pipeline altogether?

[ashepp]

Definitely would like to see this. A Consulting vs. JobHunt Pipeline would be super helpful for example.

[albert-sway]

Yeah this is specifically our use case, just checking out the product to see if it's supported and it's unfortunately a dealbreaker (unfortunate because it looks pretty ideal otherwise!)

[Bonapara]

What you can do in the meantime is create another "Select" field and create a kanban out of this field.

So for instance on your object you would have "Consulting Stage" and "JobHunt Stage" select fields with two kanban, each based on one select.

[vitolytics]

Agreed. Huge for real estate. Eg: Acquisition vs. New Development have much different stages.