Twenty-five days before a contract ends, your account manager learns about the renewal from the customer's procurement team, in a notice letter. The contract date was in the billing system all year, just not anywhere the account team looked.
This is where subscription management needs to move beyond tracking customer relationships. The wider subscription lifecycle in HubSpot covers acquisition, onboarding, customer health and retention. But keeping that lifecycle connected also means turning contract dates into timely renewal conversations and recognizing when an existing customer is ready to expand.
The question is no longer just whether HubSpot holds the customer information. It's whether the right people can act on it before revenue is at risk.
Every contract end date should live on one reliable HubSpot record, with an owner and a next step attached. Managing subscription renewals in HubSpot means the CRM prompts the work before the date arrives, instead of the customer prompting it.
Two records carry the core logic:
HubSpot CRM can hold the contract information, deal pipelines can manage renewal conversations, and workflows can create tasks and alerts on a schedule.
You don't need Revenue Hub, formerly Commerce Hub, to start managing renewal deals. It becomes relevant when you also want to connect contracts, billing, payments and other revenue operations inside HubSpot. Check which features your subscription includes, particularly for advanced workflows, contract records and reporting.
What this means for you: Before configuring anything, list every place a contract end date lives today. Then choose one authoritative record or connected data source for each agreement, and decide who keeps it updated.
Create a separate deal pipeline for renewals rather than adding renewal stages to your new business pipeline. Mixing them distorts both forecasts.
A renewal can look likely to close from the day it opens because the customer already has a contract. A new business deal earns its likelihood stage by stage. The two shouldn't share the same assumptions about deal progression.
A practical starting point is five phases, ending in separate closed-won and closed-lost outcomes:
HubSpot automation can then create the renewal deal, populate its amount from the agreed contract value and assign the owner.
Timing is the tricky part. Store the renewal lead time as its own property and use it to establish a renewal start date. For example, an annual contract with a 120-day preparation window should enter the workflow four months before expiry.
The renewal start date can be calculated or populated through your available HubSpot tools. Check which date calculations and workflow options your portal supports, and make sure the same agreement doesn't generate duplicate renewal deals.
Record a reason on every lost renewal using a dropdown property. Free text can't be grouped consistently in a report.
Questions to ask: Who owns a renewal once the person who sold the original deal has moved on? Does our current forecast include renewals, and on what basis?
Every renewal should have a named account owner and a follow-up schedule based on the contract's end date and notice period. Without both, even a well-configured renewal pipeline can become another list of deals nobody advances.
For an annual contract, we'd start about 120 days before renewal, well ahead of the customer's notice deadline.
The weeks between the first value review and that deadline are your window to fix an adoption problem, bring in a new stakeholder or adjust terms.
This also gives the account manager time to look beyond the commercial agreement. Support history, customer feedback and product usage can reveal problems that may affect the renewal decision. Where usage data sits outside HubSpot, it needs to be connected or reviewed separately.
The timeline below is a Markivis recommendation for annual contracts with a 30-day notice period. Stretch the early steps for multi-year contracts, and compress them for shorter terms.
At a glance: A renewal timeline for annual subscription contracts in HubSpot
| Days before renewal | Action | Owner | What triggers it |
|---|---|---|---|
| 120 | Create the renewal deal, assign the owner and confirm the contract data. | Workflow, then account manager | Renewal start date is reached |
| 105 | Prepare a review brief covering usage, support history and open issues. | Account manager | Task created when the deal enters Renewal scheduled |
| 90 | Hold the value review with day-to-day users and the budget holder. | Account manager | Review meeting booked and logged on the deal |
| 75 | Open an expansion deal where the review surfaced a qualified new need. | Account manager | Expansion interest recorded on the company |
| 60 | Send pricing and terms for the next period. | Account manager with finance | Deal moves to Terms proposed |
| 45 | Escalate any renewal not yet committed. | Customer success or sales lead | Deal still open with 45 days remaining |
| 30 | Confirm commitment or log any notice received. | Account manager | Notice deadline reached |
| 0 | Confirm the contract outcome, update the new term or expiry, and reconcile with billing. | Account manager | Contract end date reached |
Close the renewal deal when the commercial outcome is confirmed. That may happen before the contract end date. The final checkpoint should then confirm that the contract and billing records reflect what was agreed.
If you protect only one step, make it the 45-day escalation. A renewal can show warning signs at the value review and still slip if nobody checks whether the deal moved afterward.
A renewal that first gets attention inside the customer's notice period has already turned from a conversation about value into a negotiation about leaving.
What this means for you: Build this timeline into HubSpot workflows and tasks, not a process document. Each step then fires whether or not anyone remembers it.
An upsell should become its own deal, in a separate expansion pipeline, as soon as a qualified trigger shows a real customer need.
Expansion means more seats, a higher plan or an added product. It has a different trigger from a renewal, may involve a different buyer and doesn't necessarily follow a fixed date.
Folded into the renewal deal, the additional opportunity becomes harder to measure. Nobody can later say whether growth came from retaining existing revenue, additional volume or a new product.
Three expansion triggers are worth recording, each as the source of the deal:
Write down two policies as well: who owns expansion, and whether it closes mid-term or lines up with the next renewal.
Both are commercial calls. HubSpot records whichever approach you choose.
A customer adding seats halfway through the contract may need an immediate expansion deal. Another customer considering a higher plan at renewal may prefer one commercial discussion, but the added revenue should still be identifiable for reporting.
Marketing can support expansion by sending customers who match a trigger useful information about the next plan or relevant product capabilities. Leave out accounts whose renewal is at risk. An unresolved adoption or support problem deserves attention before another sales conversation.
What this means for you: Open a deal with a recorded source for every qualified expansion conversation, even a small one. You'll learn which triggers actually produce expansion revenue.
Report renewal and expansion performance separately from new business so revenue teams can distinguish what they retained from what they added.
Four numbers are particularly useful:
Build the pipeline views as reports on renewal and expansion deals, then bring them together on one dashboard.
Retention calculations need more care. GRR and NRR depend on a consistent starting revenue base and accurate records of churn, downgrades and expansion. They shouldn't be calculated by simply adding all closed-won renewal deals.
HubSpot offers recurring revenue reporting capabilities for eligible subscriptions, but these reports depend on the correct revenue properties and configuration. Check how your portal handles recurring revenue before treating its standard deal amount reports as retention metrics.
We'd review the renewal pipeline weekly alongside new business and reconcile recurring revenue figures with finance monthly.
When HubSpot and billing disagree on a contract value, fix the source data, not the report.
Look at loss reasons each quarter. A cluster of losses with the same reason points to a product, pricing or service issue. The renewal process can reveal it but can't fix it alone.
Questions to ask: Can we report net revenue retention from HubSpot today without a spreadsheet export? Which loss reasons came up most last quarter, and what did we change?
The Bottom Line
Renewals stop being a surprise when every end date has one home, every renewal deal opens on schedule and workflows carry the timeline.
Expansion deserves its own pipeline and a recorded source. Reporting both separately from new business shows leaders how much recurring revenue they're protecting, where growth is coming from and which accounts need attention before the next contract decision.
Every subscription renewal setup should begin with a date hunt. Find every place an end date, notice period or contract value sits today, from billing exports to account managers' calendars, and establish who updates each one.
The next step is choosing the right HubSpot record structure, building renewal and expansion pipelines, and setting up workflows that support the account team's actual process. A dashboard only becomes useful when the contract information feeding it is consistent.
This is where our HubSpot consulting, CRM implementation and automation services connect with subscription revenue operations. The work isn't just creating reminders. It's making sure ownership, contract data, commercial activity and reporting stay connected as customer relationships develop.
For subscription businesses, that means giving account managers a process they can use every week, rather than another dashboard they need to reconcile manually.