Renewal pipeline auto-routing separate from new-business pipeline

Outcome. A deal that becomes a renewal always lands in the Renewal pipeline, even if it was created or edited outside the automated flows that normally place it there, so new-business and renewal reporting stay clean.

Workflow map Enrollment, branches and actions at a glance renewal-expansion-037

flowchart TD
    A[Deal Type becomes Renewal, deal not already in Renewal pipeline] --> B[Set Pipeline = Renewal]
    B --> C[Set Deal Stage = first Renewal stage]
    C --> D[Notify owner of the move]
    D --> E{Amount unknown?}
    E -->|Yes| F[Create task: set renewal amount]
    E -->|No| G[Done]

When to use it, when not to

• UseUse it as a safety net alongside renewal-expansion-001 and renewal-expansion-026, which already create renewal deals directly in the Renewal pipeline; this fiche catches the exceptions, such as a rep manually changing Deal Type to Renewal on an existing new-business deal.
• UseUse it when renewal and new-business deals sharing one pipeline has already caused forecast or win-rate reporting to mix the two.
• SkipDo not use it if your portal intentionally keeps renewals and new business in the same pipeline with a stage-based split instead of a pipeline-based split; moving deals between pipelines can strip stage-specific automation tied to the original pipeline's stages.
• SkipDo not use it as the primary creation path; building new renewal deals correctly from the start (renewal-expansion-001) is more reliable than moving them after the fact.