Quoting systems
Salesforce CPQ end of life: what to do now, and what can wait
Salesforce CPQ is end of sale, not end of life. What that means for your renewal, how to list what your quoting setup does, and how to pick a path.
A common reading of the Salesforce CPQ news is that the product is going away and every customer needs a migration plan before the next renewal. That is not what Salesforce has said. Salesforce describes CPQ as end of sale, not end of life: it no longer sells CPQ to new customers, but existing customers can keep using it, renew, add users and receive support. So for now the real work is planning: learn exactly what your quoting setup does, then choose a path on your own schedule rather than a vendor’s. A migration decision can wait. Updating your admin contacts and saving the current documentation should not.
What end of sale means for a company already on CPQ
Salesforce’s end of sale page says CPQ is in a maintenance phase. Existing customers keep support and critical fixes, but no new features are coming. Salesforce says no end of life date has been announced and there is no forced migration. Its new investment goes into Revenue Cloud Advanced, which it names as the successor and places inside a suite it calls Agentforce Revenue Management. Some older guides call the same product Revenue Lifecycle Management; Salesforce says that was an earlier name.
One practical change landed this summer. A Salesforce help article dated July 10, 2026 says CPQ documentation is no longer published as web pages on Salesforce Help and is now a downloadable PDF. Support entitlements did not change. If your admin or partner relies on bookmarked help links, save the PDF somewhere the whole team can find it.
If Salesforce does set a retirement date later, its published retirement policy says administrators get written notice by email, with reminders before the date. The policy does not promise a fixed length of notice and allows shorter notice in some cases, so make sure the system administrator contacts on your Salesforce account are current people who read their email.
Write down what your CPQ setup actually does
In our experience, the cost of any move depends far less on your user count than on how much quoting logic lives inside CPQ. Salesforce’s own page says CPQ objects, custom fields, pricing rules and scripts do not map directly to Revenue Cloud Advanced, and that a migration usually takes three to six months from discovery to go live, longer when the setup is complex. Before anyone prices a move, list these with your admin or partner:
- Products and bundles. How many active products, how many bundles, and which options depend on other options.
- Price rules and product rules. Every rule that changes a price, adds a product or blocks a combination, with a note on who asked for it and whether it still matters.
- Discounts and approvals. Discount schedules, approval steps and the thresholds that trigger them.
- Quote templates. Each document customers receive, and any terms that change by product or customer.
- Custom code. Any custom scripts or triggers that run during quoting. These are the items most likely to need a rebuild rather than a move.
- Connections. Where an accepted quote goes next: an ERP for orders, an accounting system for invoices, a contract or e-signature tool.
- Renewals and subscriptions. Whether CPQ creates renewal quotes or contracts that other teams depend on.
Most of the list comes from CPQ setup screens and object counts your admin can pull. Expect to find rules nobody remembers creating. Ask the sales manager who owns pricing to confirm which ones still reflect how you sell today, because an estimate built on dead rules overstates the work. Knowing what exists comes before choosing what replaces it.
Three ways forward from Salesforce CPQ
With the list in hand, the choice usually comes down to three paths. The prices below are Salesforce’s US list prices as published on October 30, 2026, per user per month and billed annually.
| Path | Signs it fits | What to watch |
|---|---|---|
| Stay on CPQ and keep it tidy | Few custom scripts, rules that still match how you sell, no new pricing model planned | No new features; you rely on maintenance and the PDF documentation |
| Move to Revenue Cloud | Subscriptions, usage pricing or contract changes are growing; you want quoting, orders and invoicing in one Salesforce product | Growth is listed at US$150 and Advanced at US$200; Advanced needs an annual contract; rules and scripts are rebuilt, not copied |
| Simplify quoting | Quotes are mostly a product list with standard discounts, and much of the CPQ setup goes unused | A lighter tool may lack approvals or renewal logic you depend on, so check the list first |
Revenue Cloud Growth covers quoting and the configurator, order capture and subscriptions. Advanced adds contracts and orders plus consumption and invoicing. For a company whose quotes are mostly simple, Growth or a lighter tool may be a better comparison than Advanced. For a company that bills on usage, Advanced is the one to price.
Staying put is a fair choice. If your CPQ setup is small, stable and supported, a migration now spends money to replace something that works. The case for moving gets stronger when the list shows logic you will need to change soon anyway, such as a new pricing model, because building it twice costs more than building it once.
Questions to raise at your CPQ renewal
If your CPQ renewal comes up in the next few months, the list above also prepares you for that conversation. Get your account executive’s answers by email: how long a term is available and at what price, and whether Salesforce can say anything about future renewals of CPQ. Ask what moving to Revenue Cloud would cost for your user count, including any other Salesforce licenses it needs underneath. If a move is a real option, ask how a CPQ renewal term and a later Revenue Cloud contract would fit together, so you are not paying for both for long. Our article on the Salesforce renewal price increase in 2026 covers the wider renewal window and timing.
If the quoting decision is tangled up with an ERP connection or data that lives in more than one system, a short diagnostic can map those dependencies before anyone commits to a path.
The first piece of the inventory is the quickest to get. An export of every active price rule, product rule and custom script, with the date each was last changed, will show you most of what the choice depends on, and it is worth having on the table before the renewal call.