Add to Preferred Sources
HubSpot required deal properties are deal fields that must have a value before a user can create or move a deal in the HubSpot interface, and they are set per pipeline stage rather than with one global switch. For any B2B lead generation programme, they decide whether the pipeline you report on is built from complete records or from half-filled ones.
If you are still deciding what belongs in your CRM at all, start with our B2B lead generation guide and the CRM for lead generation post. This one is narrower: which deal fields to require, where HubSpot enforces the rule, and where it quietly does not.
Quick Answer
HubSpot required deal properties are configured per stage: in Settings > Objects > Pipelines, add a conditional logic rule to the stage, add the property under Dependent properties and tick Required. When a user creates or moves a deal by hand, HubSpot then blocks the change until the field has a value. HubSpot's page on this does not describe workflows, imports, the API or fields that already hold a value, so test those routes before you trust the rule.
Deals reaching Proposal with no amount or close date?
Send us your current deal stages and the fields reps fill in at each one, and we will talk you through where the pipeline data goes thin.
What Are HubSpot Required Deal Properties?
HubSpot required deal properties are deal fields that must have a value before a record is created or moved, and they are set per stage. HubSpot's record-creation documentation says that by default the Pipeline and Deal stage properties are automatically entered, so you do not need to require those two; any other mandatory field is one you configure.
The remaining default deal properties are Deal name, Amount, Close date, Deal owner and Deal type, among others. HubSpot describes Amount as the total value of the deal in the deal's currency, and Deal stage as the field that tracks the progress of the deal. HubSpot's default deal properties page lists them all, and it does not state which are required to create a deal.
Two defaults can mask missing data, which is why they matter here. If a deal is created in an open stage without a close date, HubSpot sets the close date to the last day of the month. Deal probability and, where you have switched on automated forecast categories, the forecast category also update on their own when a deal changes stage. A deal can therefore look complete in a report while its close date is a system guess. HubSpot's page does not say whether a Required tick treats a field that already holds a default value as filled, so do not assume it forces the rep to choose a date.
Takeaway: a filled field is not a known field
HubSpot fills Pipeline and Deal stage for you and will set a close date at month-end if none is entered. A month-end default can make a close date look filled in, so a Required tick alone may not get you a date the rep actually chose. Test it, or add a separate check such as a "close date confirmed" checkbox.
Where Does HubSpot Enforce a Required Property?
HubSpot controls deal data through four separate mechanisms, one default and three enforcement tools, and each one covers a different route into the deal record. Treating them as one feature is a likely reason a "required" field turns up empty in a report.
| Mechanism | What it enforces | Where HubSpot documents a gap | Best for |
|---|---|---|---|
| Automatic defaults (a default, not an enforcement tool) | Pipeline and Deal stage are entered for you at creation | Not applicable: nothing to configure | Giving every new deal a pipeline and stage |
| Conditional logic rules with the Required checkbox | Users cannot create or update the deal until the field has a value | The page describes manual creating and moving; it does not cover workflows, bulk edits, imports, the API or fields that already hold a value | Stage-gated data such as amount, next step or loss reason |
| Property validation rules | The format of a value: unique values, number limits, date ranges, character limits | Applies when editing or importing; not enforced in workflows, chatflows, legacy form editors or meeting scheduling pages | Stopping bad formats rather than missing values |
| Pipeline rules | Where records can be created, whether stages can be skipped, whether records can move backwards, who can edit at a stage | Bypassed by Super Admins, users with specific property edit permissions, workflows and the API; bulk editing of pipeline or stage is blocked while rules are active | Protecting stage order and closed deals |
The gap column is the part many guides skip. On HubSpot's pipeline rules page, the pipeline rules are described as applying to manual changes on desktop or mobile, and records created or edited by workflows or by the API are listed as exceptions. Pipeline rules need a Professional or Enterprise subscription. For the Required checkbox itself the page you configure it from is silent on those routes, so the honest position is "unknown until tested in your portal".
Which Fields Should Each Pipeline Stage Demand?
HubSpot required properties by deal stage should be the fields the next decision depends on, and no more. A field earns a requirement when someone will be unable to forecast, hand over or review the deal without it. The table below is a practitioner heuristic for a typical SA B2B pipeline, not a HubSpot default, so rename the stages to match your own.
| Stage | Require | Why this field at this stage | Best for |
|---|---|---|---|
| Deal created | Deal owner, lead source (custom property) | Source is hard to reconstruct later and an owner prevents orphan deals | Any team with more than one closer |
| Qualified | Deal type, a buying-need field | Separates new business from renewals and records why this lead became a deal | Teams with a defined qualification rule |
| Proposal sent | Amount, a "close date confirmed" checkbox (custom), next step | Forecasting needs a value and a date the rep actually chose, which the month-end default cannot show | Teams forecasting from the pipeline |
| Closed won | Final amount, contract or order reference | Hand-over to delivery and invoicing needs it | Services firms with a delivery team |
| Closed lost | A loss-reason property with a dropdown | A dropdown can be counted, whereas free text cannot | Teams reviewing why they lose |
Associations are not properties, so a rule such as "every qualified deal has a primary contact" needs a separate check, for example a workflow or a pipeline review, rather than the Required tick. Beyond that, two limits apply. HubSpot says properties that users do not set themselves, such as score or calculation properties, cannot be used as stage properties, so you cannot require a computed field. And the dependent property must already exist before you configure the stage logic, which means you build the custom fields first. Naming them consistently saves pain later; see our CRM field naming convention post.
Decide what Amount means before you require it
An Amount field is only worth requiring once your team agrees what goes into it. In South Africa the first question is VAT: SARS says VAT is charged at the 15% standard rate on supplies by registered vendors, and a zero rate of 0% also applies to some taxable supplies. The same deal can therefore be quoted with or without VAT.
Pick one convention for Amount, either including or excluding VAT, and write it into the property description so every rep enters it the same way. Also confirm the deal currency is rand, since Amount is held in the deal's currency.
Unsure which fields your stages should demand?
Share your pipeline stages and we will tell you whether each mandatory field helps a forecast or only slows the rep down.
How Do You Set Up a Mandatory Field on a Pipeline Stage?
To make a deal property required in HubSpot, you attach it to a stage through a conditional logic rule and tick its Required box, because the requirement lives in the stage rule rather than on the property itself. HubSpot conditional stage properties, which HubSpot's own page calls conditional stage logic, are the dependent properties that rule adds, and a rule applies to the pipeline and stage you set it on.
- Create the property first. Build the custom deal property (a dropdown for loss reason, for example) so it exists before you reference it. HubSpot requires the dependent property to exist before the stage logic is configured.
- Open the pipeline. Go to Settings, then Data Management, then Objects. Choose the deal object, open the Pipelines tab and click the pipeline's name. You need permission to edit property settings.
- Add a rule on the stage. Hover over the Conditional logic rules column in the stage's row and click Add rule. Pick the operator and the stage the rule applies to; HubSpot's examples of operators include "is equal to" and "is known".
- Add the property and tick Required. Under Dependent properties click Add property, select it and tick Required, then Save logic. HubSpot's wording is that if a property is required, users cannot create or update the record until they set a value for it.
- Repeat per pipeline. A second pipeline, such as renewals, needs its own rules. Do not assume a rule carries across.
- Test every route in. Drag a deal across the board, edit it in the record, then create one through each workflow, import and integration you use. Record which routes enforce the field.
- Write down the exceptions. Whatever step 5 shows, tell the team in one line which routes bypass the rule and who checks those deals.
Check your portal's subscription before you plan this. The HubSpot page for the feature does not state a tier for deal pipelines, so confirm in your account that the Conditional logic rules column is available. Define the stages themselves first: our B2B deal stage definitions and CRM lifecycle stages posts cover the entry and exit rules that make a requirement meaningful.
Takeaway: test the routes, not just the board
A required stage property is documented for people creating or moving deals by hand. Deals that arrive through a workflow, an import or an integration are a separate path, so test each one and keep a short list of the routes that skip the rule.
When Do Too Many Mandatory Fields Hurt the Pipeline?
Too many required fields hurt a pipeline because a rep forced to fill a field with no answer will type something to get past it, and a wrong value is worse than a blank one. The aim is the smallest set of fields that makes each stage decision possible.
As a working rule of thumb, add a requirement only when you can name the report or the hand-over that breaks without it. If you cannot, make the field optional or show it on the stage without the Required tick. That shows the field to reps without blocking them.
POPIA adds a South African limit on what a field may demand. As reproduced on popia.co.za, section 10 says personal information may only be processed if, given the purpose, it is adequate, relevant and not excessive.
Section 16 asks the responsible party to take reasonably practicable steps to keep personal information complete, accurate, not misleading and updated where necessary. Deal fields are mostly commercial, but the contacts attached to a deal are personal information. As our own illustration, not a rule from the Act, a field forcing reps to capture a personal ID number with no sales purpose would be hard to justify under section 10. Our CRM data governance checklist goes deeper, and bought databases and POPIA covers the marketing side.
Decision, not result: a two-closer services firm requires Amount, close date and next step at Proposal sent, and a loss-reason dropdown at Closed lost. Everything else stays optional. The only test is whether the weekly pipeline review can run without chasing reps for those fields.
Requirements also do not clean what is already in the CRM. For existing gaps, work through the B2B pipeline hygiene checklist and the CRM duplicate contact cleanup guide first, then switch the requirements on so new data arrives clean.
Want an outside check on your pipeline data?
Ask for a free audit of where deals enter your CRM and which fields arrive empty.
Why South African Businesses Choose Growth Pulse Media
Growth Pulse Media is a Johannesburg agency founded by Dirk van Greuning, who built and scaled a large South African ecommerce business before starting the agency. Clean deal data only matters if enough qualified enquiries reach the pipeline, and that acquisition side is the work on our B2B lead generation service page: executed in-house, with a limited client load so senior attention stays on your account.
If you need the pipeline settings built inside your HubSpot portal, a HubSpot Solutions Partner is the better hire, and this post is a useful brief to hand them.
Who This Is NOT For
Mandatory deal fields pay off for teams with a defined sales process and more than one person touching deals, and they are the wrong tool in the three situations below.
Solo founders with a handful of deals. One person who remembers every deal gains little from mandatory fields. Keep the pipeline light and add requirements when a second closer joins.
Teams without agreed stage definitions. A required field on a stage nobody can define just records noise. Settle what each stage means first.
Teams expecting required fields to fix lead quality. A requirement forces data entry, not better prospects. If the deals are weak, the problem is upstream in the source or the qualification rule.
Frequently Asked Questions
These are the questions SA sales teams ask most often when they set up mandatory deal fields, answered against HubSpot's own documentation.
Which deal properties are required by default in HubSpot?
HubSpot automatically enters the Pipeline and Deal stage properties when a deal is created. Its default deal properties page does not state which other fields are required, so any further requirement is one you configure through a conditional logic rule on a pipeline stage.
How do I make a deal property required in HubSpot?
Go to Settings, Data Management, Objects, open the Pipelines tab for deals and click the pipeline's name. Hover over the Conditional logic rules column in the stage's row, click Add rule, add the property under Dependent properties and tick Required. HubSpot then stops users creating or updating the record by hand until the property has a value.
Do HubSpot required deal properties apply to workflows and imports?
HubSpot's page on conditional stage logic describes the rule for manually creating or moving a record and does not say what happens through workflows, imports or the API. HubSpot's pipeline rules, by contrast, are documented as bypassed by workflows and the API, so test each route in your own portal.
Can I make a calculated or score property required at a stage?
No. HubSpot states that properties users do not set themselves, such as score or calculation properties, cannot be used as stage properties. Require the underlying fields the rep can fill instead.
What is the difference between a required property and a validation rule?
A required stage property demands that a field has a value before a deal is created or updated. A validation rule checks the format of a value, such as a number range or a unique value, and HubSpot documents it as applying when editing or importing, not in workflows.
Fill the pipeline before you tidy it
Growth Pulse Media runs B2B lead acquisition for South African businesses from Johannesburg, with all work executed in-house. Tell us what your team sells and we will show you where qualified enquiries can come from. No obligation, and we will get back to you within 24 hours.
