Salesforce CPQ End of Sale: What It Means (and What It Doesn't)
Salesforce CPQ is end-of-sale, not end-of-life. What each term means, what Salesforce has and has not announced, and the three real paths forward.
Salesforce CPQ is end-of-sale, not end-of-life. Here is what each term means, what Salesforce has actually announced, and the three real paths forward.
The short answer (2026)
Salesforce CPQ is end-of-sale: no longer sold to new customers, with roadmap investment moved to Revenue Cloud. It is not end-of-life. Existing orgs keep working, existing customers can continue to renew, and Salesforce has not publicly announced a firm end-of-life date at this writing. The 2029–2030 dates repeated across the market are analyst inference, not Salesforce policy. So this is a real decision window, not an emergency — and the three paths are migrating to Revenue Cloud, moving to a standalone CPQ, or building a quoting system around how you actually price.
The three terms people conflate
| Term | What it means | Is it confirmed for Salesforce CPQ? |
|---|---|---|
| End of sale | No new customers. Existing customers can continue to renew. | Yes — this is what has happened |
| End of new feature development | No meaningful new capability; patches may continue. Roadmap investment has moved to Revenue Cloud. | Yes, in practice |
| End of life / end of support | The hard deadline: security patches and support tickets stop. | No announced date |
Only the third drives genuine urgency, and it is the one Salesforce has not set. Watch your contract renewal terms; the practical reality is that you are running on a platform its owner has decided not to grow. That matters for your roadmap, not for next quarter's quotes.
Your three paths forward
| Path | Right for you if | Honest cost |
|---|---|---|
| Migrate to Revenue Cloud | You are deeply invested in the Salesforce ecosystem and intend to stay | A re-implementation, not an upgrade — different data model, different automation framework. Commonly 6–18 months plus professional services |
| Move to a standalone CPQ | You want focused quoting without deepening platform dependency | A SaaS migration to DealHub, Conga or similar; still a product you configure and rent per seat |
| Build around your own pricing | Your quoting logic is the thing no box respects | You own the result — code, data and pipeline — and carry the build instead of the licence |
For a side-by-side of every vendor in the category, see Salesforce CPQ alternatives.
What Salesforce wants you to do next
Salesforce's preferred answer is Revenue Cloud, its rebuilt quote-to-cash product. It is more powerful and more deeply integrated with the rest of the stack. It is also a re-implementation: you do not migrate your CPQ configuration, you rebuild it on a different data model, automation framework and admin surface. Complex catalogues, approval hierarchies or multi-currency pricing should plan for a full implementation cycle.
For teams already deep in Salesforce and planning to stay, that may well be right. It is not a default answer, and the timeline and cost are real inputs.
The question worth asking before you commit
What percentage of your quoting complexity is solved by Salesforce CPQ versus created by it?
Some teams find CPQ became the bottleneck — admin tickets to change a pricing tier, a UI reps route around because email is faster. Every rule, catalogue record and approval workflow you rebuild in Revenue Cloud also deepens the platform dependency, and that leverage runs in Salesforce's direction. If the product was already fighting your workflow, a forced re-implementation is a useful moment to reconsider the architecture rather than reproduce it.
When "build" makes more sense than "buy"
The CPQ market assumes you will buy a product and customise it to fit. That is reasonable when your quoting is standard. It breaks down with industry-specific logic — configurable products, multi-tier distributor relationships, subscription mixed with one-time charges, approval hierarchies that map to no template. When heavy customisation is required whichever product you pick, the build-vs-buy maths deserves a fresh look.
Customware is an AI agentic platform where RevOps leads, sales ops directors and founders direct AI agents to build production-grade quoting software they own: a database designed for your products, an interface your reps will use, approval logic that reflects your real workflow. Not a consulting engagement, and not a no-code builder that runs out of runway at complexity. A live support agent inside the software trains your team through the change.
The comparison worth making is between quoting software you license and quoting software you own, or read the migration maths directly in rebuild CPQ vs migrate Salesforce.
Deciding whether to follow Salesforce to Revenue Cloud, switch CPQ vendors, or build around your actual pricing model? Book a build-vs-buy conversation — bring your quoting requirements and you will get an honest read, including when staying put is the right call.
Frequently asked questions
Is Salesforce CPQ end of life?
No. Salesforce CPQ is end-of-sale, which means it is no longer sold to new customers. Salesforce has not publicly announced a firm end-of-life date at this writing, existing orgs keep working, and existing customers can continue to renew. End of sale, end of new feature development, and end of life are three different things and only the last one is a hard deadline.
When is Salesforce CPQ end of life?
There is no announced end-of-life date. The 2029-2030 dates repeated across the market are analyst inference rather than Salesforce policy. What is confirmed is end of sale to new customers and that roadmap investment has moved to Revenue Cloud.
Do I have to migrate to Revenue Cloud?
Not immediately, and not necessarily at all. Revenue Cloud is Salesforce preferred path, but it runs on a different data model and is a re-implementation rather than an upgrade, commonly a 6-18 month project. The three real paths are migrating to Revenue Cloud, moving to a standalone CPQ such as DealHub or Conga, or building a quoting system around your own pricing model.
What happens to my existing Salesforce CPQ org?
It keeps working. End of sale affects new licences, not running instances. The practical consequence is roadmap rather than operations: the product will not receive meaningful new capability, so the question is when to move, not whether it switches off.
Ready to fix this in your business?
Customware lets your team build production-grade software around how you actually work — by directing AI agents, not hiring a dev team or a long consulting engagement. Request early access.