Salesforce CPQ end of sale: what applies in October 2026

Salesforce CPQ is end of sale, not end of life. New customers can no longer buy it. Existing customers can keep using CPQ under their current contracts, buy additional users, renew and receive support and critical fixes. New features will not come, and Salesforce has announced no end-of-life date and says there is no forced migration. For the Salesforce Billing package there is no separate statement on a Salesforce page, only a spokesperson’s assurance of full access. So nobody has to migrate in a hurry, but the next CPQ renewal is the moment to secure the conditions for a later move to Revenue Cloud.

What exactly has Salesforce announced for CPQ?

The binding source is the Salesforce page Navigating the Future of Salesforce CPQ1. As of October 2026 it states:

• “Salesforce CPQ is end of sale, not end of life.”
• Existing customers “can continue using Salesforce CPQ, buy additional users, renew licenses, and receive support”, elsewhere on the page with the addition “under their current contracts”.
• CPQ is in a maintenance phase: “existing customers continue to receive support and critical fixes”, but CPQ “will not receive new features or innovations”.
• “Salesforce has not announced an end-of-life date for CPQ.”
• “There is no forced migration” to the new product.
• About 15 percent of Revenue Cloud Advanced customers migrated from CPQ, and a typical migration runs three to six months from discovery to go-live.

The press release on Agentforce for Revenue2 from 16 July 2025 adds that Salesforce “remains committed to supporting current Salesforce CPQ customers” and that it “rebuilt its CPQ solution as the all-new Revenue Cloud”. That last sentence explains the situation: Revenue Cloud is the successor, and Salesforce built it as a new product rather than as a new CPQ version.

Existing customers renew, add users and get support

In practice the status means:

Question	Answer for existing CPQ customers
Keep using CPQ in production	Yes
Buy additional CPQ users	Yes
Renew the CPQ contract	Yes, conditions are negotiated at renewal
Support and critical fixes	Yes
New features	No
End-of-life date	None announced
Forced migration	None
New CPQ for a new company or subsidiary org	Not as a new customer; clarify with your account team

What “no new features” means over time is easy to underestimate. Salesforce ships three releases a year. Each one adds to Revenue Cloud, and CPQ stays where it is. The Agentforce quoting functions that Salesforce announced in July 2025, for example, are part of Revenue Cloud. A CPQ org does not stop working, it just falls further behind the product Salesforce is actively building.

What applies to Salesforce Billing?

Here the statements are thinner, and I would keep to exactly what is published. The CPQ page does not mention the Salesforce Billing package at all. It names Revenue Cloud Billing as the billing product of the new suite.

The only statement on Billing comes from a Salesforce spokesperson quoted by SalesforceBen3 in March 2025: “Current Salesforce CPQ & Salesforce Billing customers will continue to receive full access”, and new customers are directed to Revenue Cloud Advanced and Revenue Cloud Billing.

Whether the Billing package is still sold to new customers is not stated on any Salesforce page I found. For your planning, the practical consequence is the same as for CPQ: existing customers keep running it, and Salesforce develops billing in Revenue Cloud Billing. If invoices come from the Billing package today, the move is a finance project as much as a CRM project. The details are in the article on moving from Salesforce Billing to Revenue Cloud Billing.

Where does the date March 2025 come from?

Many articles say Salesforce stopped selling CPQ in March 2025. That date comes from third-party reporting such as the SalesforceBen article quoted above, updated on 27 March 2025. The Salesforce page itself names neither an end-of-sale date nor an end-of-life date. If you cite a date in a board paper or a tender, mark it as reported.

The background helps when partners use different names. Salesforce CPQ and Salesforce Billing are managed packages with the namespaces SBQQ and blng. For the successor, Salesforce documentation now also says Revenue Management or Agentforce Revenue Management.

1. Dec 2015Salesforce buys SteelBrick, the base of CPQ and Billing, for $360 million according to SiliconANGLE (opens in a new tab)
2. Nov 2020Salesforce introduces Revenue Cloud (opens in a new tab), bringing together CPQ, Billing, partner relationship management and B2B Commerce
3. Spring '24The successor appears as Revenue Lifecycle Management, then as Revenue Cloud Advanced

When a partner says “Revenue Cloud”, ask whether they mean the new product or the 2020 offering of the same name. How the two products differ technically is covered in Salesforce CPQ vs Revenue Cloud: the real differences.

Secure term, price cap and parallel running at the next renewal

For me the renewal is the real deadline, because that is when you still have something to negotiate with. Before you sign, clarify these points in writing:

1. Term. A longer term gives planning certainty if the migration is two or three years away. A shorter one keeps flexibility if Revenue Cloud is already on the roadmap. Decide which you need before the account team proposes one.
2. Price increase cap. For a product without new features, I would not accept open-ended increases at the next renewals.
3. Parallel operation. Salesforce’s migration guide4 lists “Retain CPQ License” and “Coexistence During Transition” as planning topics. A migration runs CPQ and Revenue Cloud side by side for a while, so the contract should allow both without paying twice for every user for longer than necessary.
4. User growth. If you expect more quoting users, agree the price for additional CPQ users now.
5. Billing. If you also run the Billing package, renew it together with CPQ and on the same terms, so the two products do not end up with different notice periods.

A worked example: a machine builder with 60 CPQ users renews in spring 2027 and expects to move to Revenue Cloud in about two years. A two-year term with a cap on increases and a written option to run Revenue Cloud next to CPQ for six months fits this plan. A three-year term without that option would force a decision at the wrong time. How I prepare such negotiations is described under make-or-buy and licence forecasts, and which users need which licence at all is covered in Salesforce licences: does everyone need a full one?.

Does end of sale mean you should move now?

No. The status removes the urgency, and I would use that time. Whether staying, moving or a third route fits depends on your processes, your pricing master and your budget, and I go through the criteria in keep Salesforce CPQ or move to Revenue Cloud?. For manufacturers who are only now choosing a quoting system, CPQ is no longer an option at all. They compare Revenue Cloud, partner products and a custom approach, as described in from quote to sales agreement.

Find the renewal date of your contracts

Find the renewal date of your CPQ and Billing contracts, list how many users and which customisations you have, and decide before the account team calls whether you want a short or a long term. The whole path from status to migration is laid out in the masterclass chapter from CPQ to Revenue Cloud.

Sources4

1. 1Navigating the Future of Salesforce CPQ (opens in a new tab)salesforce.com
2. 2Agentforce for Revenue (opens in a new tab)salesforce.com
3. 3SalesforceBen (opens in a new tab)salesforceben.com
4. 4migration guide (opens in a new tab)help.salesforce.com