In short: HubSpot pipeline rules restrict skipping stages and moving backwards, but HubSpot's own documentation says those rules do not apply when a record moves to Closed or Closed Lost. The lock you set on a middle stage gets bypassed by closing directly. If the requirement is non negotiable, it has to live on the closing stage too.
The scene repeats itself. Someone reviews the pipeline, sees deals that went from "First call" to "Closed Won" with no quote, no close date and no amount, and reaches the usual conclusion: "the team does not follow the process". So pipeline rules get turned on, "restrict skipping stages" gets checked, and the next month deals still show up closed out of nowhere.
The team did not find a trick. The rule, as HubSpot documents it, simply does not cover that move.
On HubSpot's pipeline rules page, updated on September 9, 2026, the sentence is written plainly: "Users will still be able to skip stages if a record is moving to a Closed/Closed Lost stage".
The backwards rule has its own exception: "Users will still be able to move a record backwards from a Closed/Closed Lost stage if a record is reopened". If a closed deal gets reopened, the move backwards goes through.
Put differently: the two rules meant to keep the pipeline honest are built to guard the journey, not the exit. And the exit is exactly where reporting breaks, because a closed deal with no data is the one nobody can explain in the revenue review.
The same page lists who bypasses them, and the list is long: super admins, anyone with the "Edit property settings" permission, records created or edited by workflows, and records created or edited by API. The rules apply on desktop, in the mobile app and, per the documentation, through integrations and public APIs when a user ID is passed. The page does not clarify how that sentence and the API exception fit together.
This matters more than it sounds. If your portal receives deals from an integration, from a form with a workflow or from a migration script, what pipeline rules control is the people working by hand, not the systems. And in most portals we audit, the volume of stage changes coming from a system beats the volume coming from a click.
The tool that actually blocks is a different one. In each pipeline's setup, every stage can carry conditional stage logic: properties that appear when someone creates a record in that stage or moves a record to it, and that can be marked as required. The documentation says it this way: "If a property is required, users cannot create or update the record until they set a value for it".
The design difference is the whole point. A pipeline rule watches the path. A conditional stage property watches the arrival. If the requirement is "no deal closes without an amount and a date", do not put it on the negotiation stage hoping nobody skips it: put it on the closing stage, which is where everyone lands.
| What you want to prevent | Pipeline rule | Conditional stage property on the closing stage |
|---|---|---|
| A deal jumping from stage 2 to stage 5 | Yes, it blocks it | Not applicable |
| A deal jumping straight to Closed Won | No, it is excluded | Yes, if the field is required there |
| A deal closing with no amount or no date | No | Yes |
| An integration closing empty deals | No, the API bypasses it | Partially, see below |
| A deal reopening without a trace | No, reopening is excluded | No, property history solves that |
Starting with API version /2026-09/, released on September 8, 2026, HubSpot began enforcing on CRM write paths the rules that used to live only in the UI: conditionally required properties and required fields on record creation. The example the page itself gives is, fittingly, close_date required when dealstage is closedwon.
But the same entry carries a correction published on October 27, 2026: required associations are still enforced only in the app UI, not on public API write paths. So half the lock is real and half is still a team agreement. If your process depends on every deal carrying an associated company, the system does not guarantee that today.
If more than one source writes into the pipeline, say a billing integration, a form with a workflow and the sales team by hand, the order of the rules stops being obvious: one validation can break an integration that had been running for months. The move is to map who writes what first, and set the locks after. That is part of what we do in a diagnostic, and you can see how we work and what it costs on our pricing page.
If you want to know where your HubSpot stands today, our free self assessment takes 3 minutes: run the self assessment (in Spanish).
No, they work for the middle of the journey. They stop a deal from jumping from discovery to proposal, which is the jump that ruins stage conversion reporting. What they do not do is prevent a direct close or a reopen, and they do not stop super admins, workflows or records created through the API.
HubSpot's page lists Professional or Enterprise for object pipeline rules, with super admin permissions to configure them. Custom object pipeline rules require Enterprise, and the deal approval process requires Sales Hub Enterprise. Check your own portal before promising anything to the team.
Conditionally required ones do, starting with API version /2026-09/, returning MISSING_CONDITIONAL_REQUIRED_PROPERTY. Required associations do not: the October 27, 2026 correction clarifies those remain UI only.
That is the signal that the lock is asking for something the rep does not have at that moment. A required field only works when the data already exists when it is asked for. If it does not, move it to another stage or drop it: a field full of "N/A" hurts reporting more than an empty one, because it looks like information.