How to Set Up a Renewal Pipeline in HubSpot (And What It Won't Catch)

A dedicated renewal pipeline gives every renewal a place to live. It does not guarantee anyone is working it.

Most HubSpot portals start by tracking renewals inside the sales pipeline, mixed in with new business. That works until the first renewal quietly expires in a stage called "Negotiation" that nobody was watching. A separate renewal pipeline fixes the visibility problem: renewals get their own stages, their own reports, and their own forecast. This article covers how to set one up properly, and then the part most guides skip: the renewal risks that a pipeline, by design, cannot surface.

Quick answers

Should I use a separate renewal pipeline in HubSpot?: Yes, once you have recurring revenue worth forecasting. A dedicated renewal pipeline separates renewal deals from new business, so renewal stages, close rates, and forecasts stop being distorted by acquisition deals. It also gives customer success a workspace that is not owned by sales.
What stages should a HubSpot renewal pipeline have?: Keep it to four or five stages that describe the state of the conversation, not internal process: Upcoming (90+ days out, not yet started), In Conversation (outreach happened, customer engaged), Commitment (verbal or written intent to renew), Closed Won, and Closed Lost. More stages than that usually means stages nobody keeps current.
How do I create renewal deals automatically in HubSpot?: Use a deal-based workflow that triggers when a deal closes won and creates a new deal in the renewal pipeline with a close date offset by the contract term, or a workflow on a renewal date property. Both approaches depend on one thing: the renewal date must exist on the object the workflow watches. If the date lives somewhere else, the renewal deal is never created.
What renewal risks does a pipeline not catch?: A pipeline only shows deals that exist in it. It cannot flag renewals whose deal was never created, deals sitting in an early stage with no next step, or accounts where the renewal date lives on a line item, quote, subscription, or custom object the automation never reads. A pipeline shows state; it does not check whether follow-up is actually happening.
How does Sighub complement a renewal pipeline?: Sighub reads renewal timing across deals, line items, quotes, subscriptions, and custom objects, then checks whether real follow-up exists: a booked meeting, an open task, a recent customer reply. When a renewal is approaching with no next step, it creates one self-resolving HubSpot task with the evidence attached, whether or not a pipeline deal exists.

Why renewals deserve their own pipeline

Mixing renewals into the sales pipeline breaks three things at once.

Forecasts blur. A renewal at 90% probability and a cold outbound deal at 90% probability are not the same 90%, but the forecast treats them identically.
Stages stop making sense. "Qualification" means nothing for a customer who has been paying for two years.
Ownership gets contested. Sales reads the pipeline as theirs, so renewal deals either get ignored or get worked like new business.

A separate pipeline resolves all three. Renewal deals get stages that describe a renewal conversation, reports that only count recurring revenue, and a space customer success can own without stepping on the sales team's numbers.

The stages that actually work

The most common failure in renewal pipelines is too many stages. Every stage is a claim someone has to keep current. Four or five is enough:

Upcoming — renewal is 90+ days out, no outreach yet. This is the default landing stage for automated deal creation.
In Conversation — outreach happened and the customer engaged. The deal should not sit here without a dated next step.
Commitment — verbal or written intent to renew, paperwork in motion.
Closed Won / Closed Lost — the standard terminal stages.

Notice what is not here: stages like "Reminder Sent" or "QBR Scheduled". Those are activities, not states. Activities belong on the timeline and in tasks, not in the stage column, because encoding them as stages guarantees the pipeline drifts out of date the first busy week.

Creating renewal deals automatically

Manual renewal deal creation fails at exactly the moment it matters — the busy quarter when nobody has time to create next year's deals. Automate it with one of two patterns:

A workflow that triggers when a deal hits Closed Won and immediately creates the next renewal deal, with a close date offset by the contract term.
A workflow on a renewal date property that creates the deal a fixed number of days before the date.

Both patterns share one dependency: the renewal date has to exist on the object the workflow watches, in the field the workflow reads. In mature portals, that assumption breaks constantly — renewal timing ends up on line items, quotes, subscriptions, and custom objects, as covered in Renewal Dates Are Scattered Across HubSpot. And when the trigger field is empty or lives on the wrong object, the workflow does not error. It silently does nothing, which is the failure mode explored in Why HubSpot Renewal Workflows Miss Accounts.

What a renewal pipeline won't catch

Here is the part most setup guides leave out. Once the pipeline is live, three classes of renewal risk remain fully invisible to it:

The deal that was never created. If the automation missed an account — empty date field, date on the wrong object, contract signed outside the standard flow — there is no deal, so the pipeline reports nothing. The renewal does not show up as at-risk. It does not show up at all.
The deal that exists but is not being worked. A renewal deal parked in "Upcoming" with no meeting, no open task, and no recent reply looks exactly like one that was triaged yesterday. Pipelines show position, not momentum — the gap described in When a HubSpot Renewal Has No Next Step.
The conversation that is not booked. A deal can advance stages on internal optimism while no meeting is actually scheduled with the customer before the contract date — the check covered in How to Find Renewals Without an Upcoming Meeting in HubSpot.

A pipeline shows state. It does not check follow-up.

This is not a flaw in HubSpot; it is what a pipeline is. A pipeline is a board of claims: this deal is in this stage. Whether the claim is current depends on a human updating it, and whether the renewal is actually being worked lives in a different layer entirely — meetings, tasks, replies, owner activity. Reporting on the board tells you what the team believes. It does not tell you what is happening.

Teams that treat the pipeline as the safety net find out at the renewal date that the net had holes shaped exactly like their automation gaps. The pipeline is the map. Something still has to check the territory.

How Sighub handles this

Sighub is that check. It reads renewal timing across deals, line items, quotes, subscriptions, and custom objects — including renewals that never got a pipeline deal — and verifies whether real follow-up exists: a booked meeting, an open task with the right owner, a recent customer reply. When a renewal is approaching and none of that is in place, Sighub creates one self-resolving task on the company record with the evidence attached, and clears it when the risk clears. The pipeline keeps showing state. Sighub checks the follow-up behind it.