HubSpot Required Fields: How to Make Properties Mandatory in Your CRM

HubSpot required fields let you make specific properties mandatory before a record can be saved or before a deal advances to the next pipeline stage. The result is a cleaner database: your team cannot skip past key data points, so reports and automation rely on complete records rather than partial ones.

This guide covers where required fields can be set in HubSpot and how to configure them for deal and ticket stage transitions. It also addresses what to consider when deciding which fields to make mandatory.

What are required fields in HubSpot?

Required fields are properties that HubSpot enforces at a specific action point. When a user tries to perform that action without filling in the required property, HubSpot blocks the save and prompts the user to complete the field before continuing.

There are two distinct contexts where required fields operate in HubSpot:

• Pipeline stage transitions: for deals and tickets, you can require certain properties before a record can move to a specific stage. This is the most commonly used mechanism.
• Marketing forms: individual form fields can be set as required so that a submission cannot go through without the field filled in. This is configured inside the form editor and operates independently from CRM stage gates.

How do required fields work on deal stage transitions?

When you set required fields on a deal stage, HubSpot checks those properties each time a user moves a deal to that stage. If any required property is empty, a modal appears listing the fields that need to be filled in before the stage move can proceed.

This is most useful at two points in a sales pipeline: when a deal enters a qualified stage (you want basic information captured before the team invests time), and at the closed or lost transition where outcome data is needed for accurate reporting and forecasting.

One important limitation: required fields on stage transitions are enforced in HubSpot’s deal board and record views. They are not enforced by imports or API operations. If your CRM is connected to an integration that updates deal stages automatically, those updates bypass the required field check. This is worth knowing when auditing data completeness.

Where can required fields be configured?

In HubSpot, required fields on stage transitions are available for deal pipelines and ticket pipelines. Access them through Settings, under the relevant object (Deals or Tickets), in the Pipelines section.

For contacts and companies, there is no stage-transition mechanism that enforces required fields the same way. Workflow actions can flag records where a property is empty, and configuring the intake point (a form or an integration) to always collect the data at source is often more effective than relying on the UI gate alone. Combining custom properties with workflow enrollment gives you a practical alternative for contact-level data gaps.

How do you decide which fields to make required?

The most useful rule is to require only the fields that make a record unusable without them. Over-gating stages slows down your team and increases friction, which often leads to workarounds like entering placeholder values to move past the prompt.

A reliable starting point is to look at your reports. If a filter or segment regularly produces incomplete results because a property is blank for many records, that property is a candidate for a stage gate. Place the requirement at the transition just before the point where the gap appears.

For teams in Southeast Asia, company size and budget range are commonly required at a qualification stage. At deal close, teams typically require close reason as a minimum. For service teams, issue category and root cause alongside a resolution summary are the fields that most often go missing when left optional. This connects directly to what you need for accurate dashboard reporting.

Can required fields be bypassed?

Yes, in a few ways. Imports and API operations do not trigger stage-transition required field checks. Super admins with the right settings can sometimes override the prompt in certain views as well.

If stricter enforcement is important, review your user permission settings to control which roles can make stage moves without filling in required fields. Pair this with periodic data quality reviews to catch any gaps that came in through integrations or bulk actions.

What is the difference between required fields and conditional properties?

Required fields enforce that a property is filled in before an action can proceed. Conditional properties (also called dependent properties) control which additional fields appear based on the value selected in another field.

For example, if a deal property called “Lost Reason” is set to “Pricing,” a dependent property called “Competitor” might appear. That dependent property can itself be required. These features are configured in separate places within HubSpot settings but work well together for structured data capture at complex pipeline stages.

FAQ

Can I set required fields on custom objects?

Yes. Custom objects in HubSpot support pipelines, and those pipelines support required fields on stage transitions in the same way deals and tickets do.

Do required fields apply to the HubSpot mobile app?

Yes. The mobile app respects the same required field settings as the desktop version for deal and ticket stage transitions.

Can I require a property for all deals regardless of stage?

Not directly through the stage transition mechanism. For a property that should always be filled in, the most practical approach is to require it at the earliest stage a deal enters, or to configure the intake point to always collect that data at the source.

What happens if a required field property is deleted?

HubSpot removes it from the required fields list automatically. It is worth reviewing your stage requirements after any property cleanup to confirm the gate still covers what you intended.

Setting up required fields is one of the more direct ways to improve CRM data quality without changing your broader process. Start with one or two fields at your highest-value stage transitions and monitor data completeness over a few weeks before expanding further. This is an independent informational resource produced by a HubSpot Platinum Partner. HubSpot is a trademark of HubSpot, Inc.