Forecasting SaaS renewals and churn from your CRM data

Short answer: To forecast renewals and churn from CRM data, record each contract's renewal date, renewal amount, owner and status on the customer or deal record in HubSpot, Salesforce or Pipedrive, clean that data each month, weight each renewal by a probability based on its status and your own history, and reconcile the resulting bookings forecast to recognized revenue in your ledger.

The CRM holds the commercial facts finance needs: who renews when, for how much, and how the relationship is going. The accounting system holds what was billed and recognized. A renewal and churn forecast that a CFO can rely on uses both, and shows how one connects to the other.

Why the CRM is the starting point for renewal forecasts

Renewals are commercial events before they are accounting events. The account manager knows that a customer is reviewing alternatives, that a sponsor has left, or that a renewal has been verbally agreed, long before an invoice is raised. That information is captured, or should be, in the CRM.

HubSpot, Salesforce and Pipedrive can each hold the fields a renewal forecast needs, on the customer, deal or opportunity record. The choice of CRM matters less than whether the team agrees what each field means and keeps it current. Finance should own the definitions; the commercial team owns the updates.

The CRM fields a renewal and churn forecast needs

The table below lists the minimum fields for each contract, wherever your team chooses to store them in the CRM.

Optional fields such as auto-renewal terms, notice period and last contact date make the forecast easier to challenge, but the five above are enough to start.

Data hygiene: cleaning renewal data before you forecast

A renewal forecast is only as good as the CRM data behind it. Before each forecast, run a short set of checks:

• Missing renewal dates. Any active customer without a renewal date is invisible to the forecast.
• Dates in the past. A renewal date that has passed with no update usually means the renewal happened, or the customer left, and nobody recorded it.
• Amounts that do not match billing. Compare current contract value in the CRM with the latest invoice in Xero or QuickBooks Online. Differences often come from mid-term upgrades or discounts recorded in one system only.
• Duplicates. The same customer as two records, or two open renewal deals for one contract.
• Stale status. Renewals still marked "likely" with no activity for several weeks.

Send the exceptions to the renewal owners with a deadline before the forecast is run. Over a few months the exception list gets shorter, which is itself a useful sign that the data can be trusted.

Weighting renewals by probability

Probability weighting converts a list of renewals into a dollar forecast: each renewal amount is multiplied by the probability for its status, and the results are added up.

Base the probabilities on your own history. Look back over the last four to eight quarters, group past renewals by the status they had one or two months before the renewal date, and measure what share of the dollars renewed. That observed rate is a better starting point than a figure from outside the business.

Illustrative example: in the fourth quarter of 2026, a company has $1,000,000 of annual contract value up for renewal.

The probabilities in this example are illustrative. The forecast churn for the quarter is the difference, $210,500 of annual contract value, before any expansion on the renewing contracts.

Forecasting churn and contraction

Churn is the loss of a customer; contraction is a customer that renews for less. Both reduce recurring revenue, and both can be forecast in two ways:

• Inside the renewal weighting, as in the example above, where the probability already reflects the chance of losing the customer.
• As a separate line, using named at-risk accounts plus a rate for the rest of the base.

Choose one method and use it consistently, so that churn is not counted twice. Contraction is best captured through the expected renewal amount field, because a customer reducing seats from 100 to 70 is a known amount, not a probability.

Track the forecast against what happened. Each quarter, compare forecast churn and contraction with actual results by status group, and adjust the probabilities if one group is consistently too high or too low.

Reconciling CRM bookings to recognized revenue

A renewal in the CRM is a booking: a commitment to pay for future service. It is not revenue. Revenue is recognized over the service period, so a twelve-month renewal starting on October 1, 2026 adds about one quarter of its value to revenue in the fourth quarter of 2026, with the rest recognized over the following nine months.

To turn the renewal forecast into a revenue forecast, and to keep it consistent with the accounts:

1. Convert bookings to revenue using the start date and term of each renewal, on the same basis as your revenue schedule.
2. Tie closed renewals to invoices. Each renewal marked as won in the CRM should have a matching invoice in the accounting system for the right amount and period.
3. Tie the revenue schedule to the ledger. Recognized revenue and deferred revenue in the schedule should equal the ledger balances after the month-end close.
4. Explain the gaps. Differences between CRM bookings and recognized revenue are usually timing, discounts, or contract changes recorded in one system only.

Our guides on deferred revenue vs accrued revenue and why deferred revenue reconciliations break cover the accounting side of this step.

A monthly renewal forecast routine

A simple monthly routine keeps the forecast current without taking over the close:

1. Run the data hygiene checks and send exceptions to owners.
2. Review the largest renewals in the next two quarters with their owners, and update status and expected amounts.
3. Apply the probabilities and produce the weighted renewal and churn forecast.
4. Convert to recognized revenue and add it to the revenue forecast.
5. Compare last month's forecast with what happened and note the reasons for any difference.

The output feeds the board pack's retention and forecast pages, and the same data supports SaaS metrics such as net revenue retention.

How ScaleXP uses CRM data in revenue forecasts

ScaleXP builds revenue forecasts from CRM data in HubSpot, Salesforce or Pipedrive and accounting data from Xero or QuickBooks, with renewals and existing contracts included as inputs and forecasts reconciled with accounting actuals. See revenue forecasting in ScaleXP for how the forecast is built, and CRM and accounting integration for how deal and opportunity data connects to the ledger.

The same CRM data supports revenue schedules, and ScaleXP prepares the revenue recognition journals from them, which are posted once finance approves them.

In the ScaleXP demo company below, the CRM renewals summary for September to December 2026 counts the renewals that are due, complete, lost or canceled, in progress, or not renewing, with the contract value of each group.

Conclusion

A renewal and churn forecast built from CRM data depends on four or five well-kept fields, a monthly data hygiene routine and probabilities drawn from your own renewal history. Forecast churn once, convert bookings to recognized revenue on the same basis as your revenue schedule, and reconcile to the ledger, so the commercial forecast and the accounts agree.

To build this forecast without a spreadsheet, ScaleXP's revenue forecasting combines CRM pipeline, renewals, billing and actuals, and includes contracted revenue not yet invoiced and renewals due.

Frequently asked questions