Wrong pipeline-stage combination flag

Outcome. A deal carrying a stage value that does not belong to its own pipeline, a state that should not be reachable through the UI but can appear after an API import or a pipeline restructure, gets flagged for correction before it distorts stage-based reporting.

Workflow map Enrollment, branches and actions at a glance deal-hygiene-046

flowchart TD
    A[Pipeline and Deal stage known] --> B{Stage valid for this deal's pipeline?}
    B -->|no| C[Set Pipeline Stage Mismatch Flag = true]
    C --> D[Create fix-it task for sales ops]
    D --> E[Notify sales ops]
    B -->|yes| F[Set flag = false, exit]

When to use it, when not to

• UseUse it after any bulk import, a pipeline merge, or a migration from another CRM, these are the situations most likely to produce a deal whose Deal stage value belongs to a different pipeline than the one on the Pipeline property.
• UseUse it as an ongoing safety net if deals are regularly created or updated through the API or a third-party integration that does not enforce the same pipeline-stage pairing the HubSpot UI does.
• SkipDo not use it if every deal in your portal is created and edited exclusively through the HubSpot UI, the interface itself prevents this mismatch from happening in normal use, this fiche exists for the integration and migration paths that can bypass that.
• SkipDo not treat every flagged deal as urgent, a mismatch does not usually block a deal from closing, it distorts stage-based counts and reports until corrected.