Pipeline specific Default Deal Properties

Hello Team, 


Our use case:

We have various pipelines, for various sales cycles and sometimes various types of contacts or companies.

The Deal's information we need to access depend on the pipeline the deal is in. Since the "default deal properties" is made to display the "most important" information of a deal, we need this group of "most important" information to be pipeline specific.


Our suggestion:

To propose to create multiple "default deal properties", each one having a name. Then, admin should be able to decide to which pipeline to apply this "default deal properties". A "default deal properties" may be applied to one or more pipelines. It's ok to have a limit on the possible numbers of possible "default deal properties" if needed. 10 or 20 maximum would already be amazing.


Note: I've written the above with the understanding that "default deal properties" are controlling both the "about" section on the deal and the properties available when creating a new deal on the card that's opening on the right of the screen.




93 Replies
New Contributor

Hi Dylan,


Thanks for the update — the newly introduced features are great!


However (I hope I'm wrong…), this does not at all address the issue of required properties when creating a Deal? This was a core part of this thread.




Regular Contributor | Platinum Partner

Yeah it's a great feature, but the really nice things like custom properties view and dependent section, are only on Enterprise... and in any case seems that you still can't manage custom properties at the moment of creations of a new deal.



HubSpot Moderator

Hi Tim, 


When combing through the thread, I did notice this to be about 30% of the case that was mentioned. Unfortunately, this is not part of the update I posted about above but it is firmly on our radar. 


We are beginning to kick off work on that front (creating deals) but I felt as if the majority of the asks here were around the data that displays on Deals. We're well aware of the case for conditional required properties based on a pipeline an object is created in and will update this thread (or another, if it pops up) once we have that in a beta! 

Thanks as always for your continued feedback on our product 


- Dylan


New Contributor

That's great to hear, thank you!


@Dylan I am the original creator of this idea, more than 2 years ago. I think it is not right to say this idea is delivered. Below are three reasons why. Hence, could you please change the status back to submitted or something like working on? Here is why:


1/ It's Beta, not in Live: The concept of beta means it can still be stopped and never go live or can be changed.

2/ It does not cover the scope of the idea: The feature delivered does not cover new deals, which was part of the original idea (check it one more time). Hence, the feature did not deliver the idea, only a part of it. As such, please do not send to garbage the 200+ upvotes of people over 2 years by marking the idea delivered. Many also voted for the new deal components and for them it's not delivered.


Apart from the above facts, it's surprising no one has contacted me from Product Team at Hubspot. A few months after posting the first idea, I mentioned what you needed to develop was actually equivalent to Salesforce Record Type. But you kept focusing on an idea that was 2 years old. We would have liked to make the conditions based on something else than the pipe, we did not get it.


Regular Contributor

I agree this hasn't really been delivered. Properties are still created for all pipelines and only those with enterprise packages can implement a workaround.


It's really frustrating to be given a partial solution and see pretty basic functionality added for enterprise customers only (because there is a demand for it, you have to assume).

New Contributor

I wish that having properties by pipeline wouldn't be only available to enterprise users; It feels like this is basic functionality that should come with having the ability to have multiple pipelines (and atleast be available to professional users).


@Dylan Any feedback on my explanation? As the feature delivered cover only a part of the scope of the idea, could you please turn back the idea to "submitted" or "in planning"? 

HubSpot Moderator

Hi @VagaeNatus - thank you for your follow up here. 

This original idea contained 2 great feature improvements that are different segments of work for our teams and cannot be completed in tandem. Since we have delivered on one of the ideas, our community team has advised that we keep this idea marked as "delivered". 

However, since the other half of the suggestion is yet to be implemented (the ability to use different properties upon deal/ticket creation), I created another idea to track development. I've also set the idea to "In planning" as we are actively determining the best way to solve this problem and it is something we do plan to implement. 

Thank you for your continued feedback, I'm also looking forward to marking that idea delivered as well! 

- Dylan 

Regular Contributor

Hi there,


I found various related ideas in the forum that I wanted to tag here. I am a Sales Pro professional user and Marketing Pro user. I also have the reporting add on. I am very disappointed to hear that the ability to customize deal properties per pipeline that a deal is in is ONLY for enterprise level clients. My company is not big enough to be enterprise level and it doesn't make sense for us to upgrade for basic features like this. Professional level allows multiple pipelines and this need for displaying different deal properties in the "About" section so often correlates to that variable. It should not be gated to allow just Hubspot enterprise clients. This is a matter of organizing the data we have on the deal level to do the best work we can. Please extend this feature to Professional customers as well.


Related requests:






Regular Contributor

It is absurd and Hubspot upsale tactics will be the death of them. 

Occasional Contributor


Regular Contributor

Agree, as not all properties are applicable for all pipelines.