No. It’s in end of sale and a maintenance phase. Here’s exactly what Salesforce has and hasn’t said, as of October 19, 2026.
| Question | Status | Detail | Source & date |
|---|---|---|---|
| Can new customers buy Salesforce CPQ? | No | CPQ entered an end-of-sale phase; Salesforce no longer sells new CPQ licenses to new customers. | Salesforce confirmation reported March 2025; Salesforce CPQ end-of-sale page, July 10, 2026 |
| Can existing customers keep using it? | Yes | Existing customers can continue using CPQ, buy additional users, renew licenses and receive support. | Salesforce CPQ end-of-sale page, July 10, 2026 |
| Will CPQ get new features? | No | CPQ is moving into a maintenance phase with support and critical fixes, but no new features or innovation. | Salesforce, July 10, 2026 |
| Is there an end-of-life date? | Not announced | Salesforce states it has not announced an end-of-life date. Dates circulating on third-party blogs are not Salesforce announcements. | Salesforce FAQ, July 10, 2026 |
| Is migration forced? | No | Salesforce says there is no forced migration from CPQ to Revenue Cloud. | Salesforce, July 10, 2026 |
| What replaces it? | Revenue Cloud Advanced | Salesforce positions Revenue Cloud Advanced as the successor. Revenue Lifecycle Management was an earlier name for this line, and branding has shifted, so check the SKU names on your order form. | Salesforce, July 10, 2026 |
| Is moving an upgrade? | No | Revenue Cloud Advanced is built natively on the platform. CPQ objects, custom fields, pricing rules and scripts don’t map directly, so moving is a re-implementation. Salesforce cites 3–6 months for a typical migration. | Salesforce FAQ, July 10, 2026 |
| What about billing? | Decide together | Revenue Cloud Billing has been available since the Spring ’25 release. If you also run the legacy Salesforce Billing package with CPQ, treat it as part of the same decision. | Industry coverage of Salesforce announcements, March 2025 |
How we verified this: We checked Salesforce’s own “Product End of Sale (Not End of Life)” page (dated July 10, 2026) and March 2025 coverage of the original announcement. Salesforce can change this guidance, so confirm current terms with your account executive before you sign a renewal or a migration SOW.
Nothing breaks on a date. What changes is that every new pricing idea now has to work around a product that has stopped moving.
You can renew CPQ. Use the renewal to buy flexibility: shorter term, or language that lets you move spend to Revenue Cloud or another tool if you migrate mid-term.
NegotiateMoving to usage, hybrid subscription-plus-services or new bundles? This is the strongest trigger. Building new logic on a frozen product adds custom code you will migrate later.
Biggest triggerQuote Calculator Plugin scripts, custom Apex on CPQ objects and custom amendment logic are what make a migration long. Inventory them now, even if you don’t move for a year.
InventoryStaying is a legitimate choice. Harden what you have, fix technical debt, document rules, and set a review date tied to your contract cycle.
Stay + hardenIf a CRM change is already on the table, don’t migrate CPQ twice. Decide the CRM first; quoting follows it.
SequenceIf the problem is subscriptions, proration and ARR that won’t reconcile, a billing engine may matter more than which CPQ you run.
Re-scopeFive real paths. Revenue Cloud is the default answer from Salesforce, not the only one.
| Option | Best when | Typical effort (JayOh guidance) | Main risk | Watch-out |
|---|---|---|---|---|
| 1. Stay on CPQ and harden | CPQ meets today’s needs, pricing is stable, no new models in the next 12 months | 2–6 weeks of cleanup and documentation | Technical debt grows; no new capabilities | Set a dated review; avoid new custom code |
| 2. Migrate to Revenue Cloud Advanced | Salesforce is your long-term CRM, configuration is complex or multi-entity, you have admin and developer capacity | 3–6+ months; Salesforce cites 3–6 months as typical | Treated as an upgrade instead of a re-implementation | Rules, scripts and objects don’t map directly; plan a fit-gap first |
| 3. Third-party CPQ on Salesforce (e.g. DealHub) | You want CPQ depth and guided selling fast, with less admin overhead, and may keep CRM options open | 6–12 weeks | Another vendor and another sync to own | Design how quotes, products and renewals write back to Salesforce |
| 4. Move quoting to HubSpot | You are consolidating the CRM onto HubSpot and the catalog is simple to moderate | Runs with the CRM migration, often 8–16 weeks | Native quoting outgrown by complex rules | Add a CPQ or billing engine if rules or subscriptions are complex |
| 5. Billing-led (e.g. Chargebee) | The pain is subscriptions, proration, invoicing and ARR, not configuration | 6–12 weeks including CRM sync | Two catalogs if ownership isn’t governed | Make billing the catalog owner; sync renewals back as opportunities |
Effort ranges are JayOh practitioner guidance for a single Salesforce org with a reasonably clean catalog. Heavy customization, multiple entities or large subscription volumes push toward the top of each range. Compare stacks side by side on our quote-to-cash & CPQ page.
| Inventory item | Low | Medium | High |
|---|---|---|---|
| Active price rules | < 20 | 20–75 | > 75 |
| Active product rules | < 20 | 20–75 | > 75 |
| Quote Calculator Plugin (custom JavaScript) | None | < 300 lines | > 300 lines |
| Apex classes/triggers on CPQ objects | 0–5 | 6–20 | > 20 |
| Quote templates | 1–3 | 4–10 | > 10 |
| Downstream integrations (billing, ERP, CLM, provisioning) | 0–1 | 2–3 | 4+ |
| Active contracts / subscriptions to migrate | < 1,000 | 1,000–10,000 | > 10,000 |
| Renewal and amendment customization | Standard | Some twin fields / custom logic | Heavily custom |
JayOh guidance, not a vendor standard. Mostly Low: plan toward the bottom of each effort range. Two or more High: budget for the top of the range and a phased cutover.
Work top to bottom. The first “stop” you hit is your path.
Use it to frame the internal conversation. Validate it against your actual org inventory.
Whatever path you pick, the first 30 days are the same: know exactly what you have.
Your CPQ inventory doubles as a health check. Our Salesforce Audit Framework and Flow Audit cover the automation around it.
We implement Salesforce, HubSpot, DealHub and Chargebee quote-to-cash. We don’t need you to pick one.
We engineer growth systems. JayOh builds the RevOps architecture, GTM execution and data infrastructure that turn messy revenue operations into predictable pipeline for B2B SaaS and PE-backed teams.
