Required-field rules in 4 tools before stage change

• Before moving a software deal to the next stage, verify that the specific fields marked as required in your system have values.
• Each publisher defines this blocking rule differently, and some paths bypass the check entirely.
• In HubSpot, set a value on a required property before you create or update the record.
• For Zoho, supply the mandatory fields required to create a deal for a newly converted record.

The blocking rule operates at the record level. When an administrator selects the Required checkbox for a property, the system enforces that value before any creation or update action succeeds. According to HubSpot, "Select the Required checkbox to require a property." This setting applies to the object pipeline configuration. If a property is marked as required, users cannot create or update the record until they set a value for it, according to HubSpot.

The scope of this rule is specific to the property definition. It does not apply to every field on the deal. Only properties with the Required checkbox selected trigger this block. The administrator controls which properties are required. The user controls the values. The system controls the enforcement.

The system enforces it for every subsequent update. This creates a consistent data standard across the pipeline.

In Pipedrive, the requirement is a setting you apply to specific data fields. According to Pipedrive, required fields allow you to select which of your data fields should be mandatory while adding or editing a deal, contact person, or organization. The setting blocks the action if the data is missing. Users in your account won’t be able to add or edit new items or move deals until the required fields have been filled in, according to Pipedrive. If any users try to move a deal to a new stage without a required field filled in, they will be prompted to add the required information, according to Pipedrive. The system does not allow the stage change to proceed; the user must supply the value to clear the block.

In Microsoft Power Automate, the requirement is defined at the step level within a business process flow. According to Microsoft, you select Required if people must fill in the column to complete the step before moving to the next stage of the process. This setting ties the field directly to the completion of a specific step. The user cannot advance the process until that specific column contains data.

In Microsoft Dynamics 365 Sales, the mechanism is similar but described as making a step required. According to Microsoft, you can make a step required so that users must enter data for the corresponding field before they can proceed to the next stage. The focus here is on the step itself; the field is the data point that must be satisfied to complete that step. If the field is empty, the user cannot move to the next stage of the process.

The common thread across these tools is that the required field acts as a gate. In Pipedrive, the gate is on the action of adding, editing, or moving a deal. In Microsoft tools, the gate is on the completion of a step or the progression to the next stage. The user is stopped until the specific field associated with that requirement has a value. Both require the user to provide the data before the system allows the next action.

The following table summarizes the documented rules for four publishers, detailing how required fields block record changes.

HubSpot documentation states that selecting the Required checkbox makes a property mandatory, preventing users from creating or updating the record until a value is set, according to HubSpot. Pipedrive defines required fields as mandatory data fields that stop users from adding or editing items or moving deals until filled, according to Pipedrive. Microsoft Power Apps documentation notes that business process flows can have up to 30 stages and 30 steps for each stage, with required steps blocking progression to the next stage, according to Microsoft. Zoho CRM API documentation lists mandatory fields required to create a deal for a newly converted record, according to Zoho.

For Pipedrive, the required fields feature does not stop deals from progressing if fields are updated through import, bulk-editing, API, automations, or third-party integrations, according to Pipedrive. See Bulk-edit sales records: 4 checks before saving changes. Additionally, required fields are not supported on the leads detail view in Pipedrive, according to Pipedrive. Microsoft Dynamics 365 Sales documentation confirms that making a step required forces users to enter data before proceeding to the next stage, according to Microsoft. These rules apply specifically to the named products and do not generalize to every sales tool.

Check your own stage list against these publisher-specific rules before the forecast call. See Quote checks before the forecast call: 4 tools.

The default pipeline in the object settings contains seven specific deal stages, each with an assigned percentage. According to HubSpot, these stages are Appointment scheduled at 20%, Qualified to buy at 40%, Presentation scheduled at 60%, Decision maker bought-in at 80%, Contract sent at 90%, Closed won at 100% marked as Won, and Closed lost at 0% marked as Lost. These percentages are part of the default structure. See Open, won, and lost stage rules in 4 sales tools.

When configuring stage properties, certain field types are excluded from selection. According to HubSpot, properties with read-only values, such as score or calculation properties, cannot be used as stage properties. Because these values are not set by users, they will not appear as options to select as stage properties. This exclusion applies to any property where the system generates the value rather than the user entering it.

The platform also offers conditional logic for displaying fields. According to HubSpot, you can set up conditional stage logic to show certain properties when users manually create a record in or move a record to a specific stage.

For your weekly forecast call, verify that the fields you expect to be required are actually selectable in the stage settings. If a field you need is a calculation or score property, it cannot be used as a stage property and will not appear as an option to select. Check your pipeline configuration to see which properties are eligible for this rule.

When a required field is empty, the standard user interface may block a stage change, but specific technical pathways can bypass this check. According to Pipedrive, the required fields feature will not stop deals from progressing if the fields are updated through import, bulk-editing, API, automations, or third-party integrations. This means a deal can move to a new stage through these channels even if the mandatory data points remain blank. The documentation explicitly lists these five methods as exceptions to the blocking rule. The restriction applies to the manual progression path, not to these background or programmatic updates.

According to Pipedrive, required fields are not supported on the leads detail view. This means that if you are working with a lead rather than a deal, the system will not enforce any required field rules on that screen. The setting covers a deal, a contact person, or an organization.

According to Microsoft, each branch can be no more than 10 levels deep. This cap defines the maximum depth of the process flow hierarchy. This limit applies to the flow design, not to the data validation of individual fields. It constrains the complexity of the stage path you can create.

Use the worksheet below to map the fields you control against the rules documented for each tool. The table shows one example row so you can verify which specific data points block a stage move in your environment. Note the stage name, the field your team marks as mandatory, the tool where that rule lives, and whether you have tested the bypass path for that specific record type.

Review each row to ensure the "Bypass Path Checked" column reflects your actual testing. If a path does not enforce the rule, mark it clearly. This keeps your forecast call focused on fields that genuinely block the move. Do not assume a field behaves the same way across all four tools. Verify the specific setting in your own instance before relying on it during the weekly review. If a field is empty and the stage does not move, check the documentation for that specific publisher to confirm the requirement is active. Keep this checklist updated as you add or remove fields from your pipeline stages.

A manager reviews 1 deal today. The record shows 4 fields. 3 of those fields already have values, and 1 field is empty. Where an empty required field blocks the stage change, the manager cannot move the deal until that field has a value. Where the rule blocks a create or an update, the manager sets the value before the record is saved. Where mandatory fields are required to create a deal for a newly converted record, the manager fills those fields before the deal exists. The manager also pictures a process with a cap of 30 stages and a branch cap of 10 levels. Neither cap is the reason this deal stays put. The empty field is the reason. The manager writes the field down, fills it, and only then moves the deal.

Open one deal you will review today and write down any field your own screen will not let you leave blank before the stage changes. No signup and no purchase.

Which fields can stop a deal from changing stage?

Pipedrive can stop the move until its required fields are filled, and Microsoft can stop the next stage until the required field has a value.

Does HubSpot start with named stages and percents?

The default pipeline has seven deal stages: Appointment scheduled (20%), Qualified to buy (40%), Presentation scheduled (60%), Decision maker bought-in (80%), Contract sent (90%), Closed won (100%, Won), and Closed lost (0%, Lost), according to HubSpot. These values are part of the default configuration for object pipelines.

Will an import still move a Pipedrive deal if a required field is empty?

Currently, the required fields feature won’t stop deals from progressing if the fields are updated through import, bulk-editing, API, automations, or third-party integrations, according to Pipedrive. This note clarifies the specific paths that bypass the standard field check.

How many stages can a Microsoft process hold?

Use a maximum of 30 stages for each process and 30 steps for each stage, according to Microsoft. This limit applies to the business process flow created in Power Apps.

What does Zoho require to create a deal for a newly converted record?

Mandatory fields are required to create a deal for the newly converted record, according to Zoho.