HubSpot ARR vs MRR for Renewal Forecasting: Choose the Right Value
By Ulas ArslanPublished
For annual renewal forecasting, ARR is usually the most useful HubSpot value when the Deal’s recurring line items and term are correct. MRR is the monthly equivalent. TCV includes recurring and one-time line items across the full term. Do not copy the nearest number. First define whether the forecast needs monthly run rate, annual recurring value or full contract value.
Give every revenue field one job
HubSpot revenue fields answer different questions. The safest forecast starts by naming the question before choosing a value.
HubSpot’s current default Deal property reference says MRR and ARR are calculated from recurring line items and their term. They do not use the Deal Amount field. TCV includes recurring revenue and one-time charges from the associated line items.
| Field | What it measures | Renewal use |
|---|---|---|
| Amount | The total Deal value entered for the Deal | Use only when your team has a clear and tested Amount rule |
| MRR | Recurring revenue per month from recurring line items | Monthly recurring portfolio view |
| ARR | Annual recurring revenue from recurring line items | Annual recurring renewal value |
| TCV | Full line-item value across the term, including one-time charges | Full contract value, not recurring value by default |
| Recurring revenue amount | A separate monthly value used by HubSpot’s recurring revenue analytics | Revenue movement reporting when your team maintains it |
Work through one Deal before building the report
Example: Delta Labs signs a 12-month software term with a recurring line item of €1,200 per month and a one-time onboarding line item of €3,000. Assume the line items and term are set correctly.
For an annual recurring renewal forecast, €14,400 is the useful starting value. The €3,000 onboarding charge belongs in TCV, but it should not be treated as recurring unless the next agreement really includes it again.
| HubSpot value | Example result | What it tells the team |
|---|---|---|
| MRR | €1,200 | Monthly recurring run rate |
| ARR | €14,400 | Annual recurring value |
| TCV | €17,400 | Twelve months of recurring value plus onboarding |
| Deal Amount | Depends on the team’s entered value | Does not change the calculated MRR, ARR or TCV |
Check line items and term before trusting ARR
ARR is useful only when the inputs describe the real agreement. Check the recurring price, billing frequency, quantity, start date and term. HubSpot says that if a recurring line item has no term length, ARR assumes a 12-month term.
ARR and MRR also have subscription requirements. HubSpot currently lists Sales Hub Professional or Enterprise for these Deal properties. If a field is unavailable, do not replace it with another value without documenting the new rule.
Do not mix calculated and manually maintained revenue fields
HubSpot’s recurring revenue analytics guide describes another field called Recurring revenue amount. It is a monthly value, but it is separate from the default MRR and ARR properties.
The recurring revenue analytics fields are maintained for reporting events such as new business, renewal, upgrade, downgrade and churn. HubSpot says the report uses the values entered in those properties rather than products or quotes. A team can therefore have calculated MRR and a different manually maintained recurring revenue amount on the same Deal.
Match the field to the forecast question
A single revenue column cannot answer every forecast question. Write a fixed rule for each report and keep the field name visible.
- For monthly recurring run rate, use verified MRR.
- For annual recurring renewal value, use verified ARR.
- For the full signed Deal value, review TCV and its one-time line items.
- For Deal pipeline forecasting, use the field and forecast rule defined by the sales team.
- For recurring revenue movement reports, follow the recurring revenue property process and its required field pairs.
- For a portfolio total, convert values to one reporting currency before adding them.
Keep booked, billed and collected revenue separate
A renewal forecast is not the same as an invoice report or a cash report. HubSpot’s current revenue reporting guide separates potential Deal revenue, booked contract revenue, contracted revenue, billed revenue and collected revenue.
Choose the stage that matches the decision. A customer success forecast may need recurring value due for renewal. Finance may need invoices sent or cash collected. Combining those stages creates a total that is hard to explain.
Handle expansions, contractions and partial terms
An upgrade can change MRR or ARR before the main renewal date. A downgrade can reduce the recurring base. A short extension can have a different TCV without changing the long-term run rate in the same way.
Keep the effective date and the commercial event beside the value. HubSpot’s contract revenue reports separate new revenue, expansion, contraction and churn. The event explains why the number moved; the number alone does not.
Keep value separate from renewal risk
ARR measures recurring value. It does not measure the chance that a customer will renew. A large ARR Deal is high exposure, but it is not proven churn. An unpaid invoice, low activity or an open renewal Deal can add context without proving the final outcome.
Record renewed or churned only from an explicit outcome or another reliable final state. Keep pending decisions visible instead of forcing them into won or lost.
Give agents one resolved value with evidence
A fixed rule should select the eligible field, currency, source Deal and effective date. An agent or LLM can explain the result, but it should not choose whichever number looks most complete.
Return the source record, field name, currency, value and scan time. If line items change after the scan, the earlier result is point-in-time evidence, not current real-time data.
Know the Sighub boundary
Renewal Radar can include value at risk when supported value evidence is available. It does not replace HubSpot revenue accounting, edit existing Deal values or promise that every account has a usable value.
Use the renewal forecast guide to define the forecast population and outcome rules. Then use the same value rule across the report, review queue and agent explanation.
