Skip to content

Renewal pipeline auto-routing separate from new-business pipeline

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Sales Hub Professional.

Deal6 stepsUpdated for HubSpot seat pricing
OutcomeA 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 maprenewal-expansion-037
Deal Type becomes Renewal, deal not already in Renewal pipeline leads to Set Pipeline = Renewal. Set Pipeline = Renewal leads to Set Deal Stage = first Renewal stage. Set Deal Stage = first Renewal stage leads to Notify owner of the move. Notify owner of the move leads to Amount unknown?. Amount unknown? leads to Yes: Create task: set renewal amount; No: Done. Yes No Deal Type becomes Renewal, deal not already in Renewal pipeline Set Pipeline = Renewal Set Deal Stage = first Renewal stage Notify owner of the move Amount unknown? Create task: set renewal amount Done
Deal Type becomes Renewal, deal not already in Renewal pipeline leads to Set Pipeline = Renewal. Set Pipeline = Renewal leads to Set Deal Stage = first Renewal stage. Set Deal Stage = first Renewal stage leads to Notify owner of the move. Notify owner of the move leads to Amount unknown?. Amount unknown? leads to Yes: Create task: set renewal amount; No: Done. Yes No Deal Type becomes Renewal, deal not already in Renewal pipeline Set Pipeline = Renewal Set Deal Stage = first Renewal stage Notify owner of the move Amount unknown? Create task: set renewal amount Done

When to use it, when not to

Use it

  • Use 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.
  • Use it when renewal and new-business deals sharing one pipeline has already caused forecast or win-rate reporting to mix the two.
Read more on when to use itShow less

Skip it

  • Do 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.
  • Do 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.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 3 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 6 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 5

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 4 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Renewal and expansion spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library