Salesforce CPQ End of Sale: What It Means and What to Do Next

01What Salesforce CPQ End of Sale Means

In March 2025, Salesforce stopped selling new Salesforce CPQ licenses. If you already run CPQ, nothing was shut off, and your implementation keeps working exactly as it did before. What changed is who Salesforce will sell CPQ to going forward: nobody who isn't already a customer.

Salesforce's own framing of this is worth quoting directly, because a lot of the content written about this event blurs a distinction that matters: “Salesforce CPQ is end of sale, not end of life. These are meaningfully different.”

02End of Sale vs. End of Life

End of sale means Salesforce will not sell new CPQ licenses to companies that don't already have them. It does not mean the product stops working, stops being supported, or has a scheduled shutdown date. It is a sales-channel decision, not a product-retirement decision.

End of life would mean Salesforce sets a date after which the product is no longer supported at all, and existing customers would eventually have to leave whether they wanted to or not. Salesforce has explicitly said this is not that, and as of this writing has not published an end-of-life date for CPQ. Some partner content speculates about a future end-of-life year; treat that as speculation, not as a Salesforce commitment, because Salesforce itself has not stated one.

What Salesforce has said, more precisely, is that CPQ is now in a maintenance phase: existing functionality stays supported, but new feature development is going toward Salesforce's successor product line, not toward CPQ itself. That's a narrower claim than “CPQ will never be touched again,” and it's the one actually worth planning around.

03What This Actually Changes

If you already run Salesforce CPQ

You keep your license, you can add seats, and you can renew, subject to your existing Salesforce agreement. Salesforce continues to support what you already have. What you shouldn't expect going forward is significant new CPQ-specific capability. Salesforce is directing new product investment toward its successor revenue-management architecture rather than Salesforce CPQ.

If you're evaluating a quoting system for the first time

Salesforce will point you toward its current successor architecture, which you may see referred to as Revenue Cloud Advanced or, under Salesforce's Agentforce Revenue Management branding introduced in 2025, by that name instead. These aren't necessarily precise, one-to-one renames of a single product in strict sequence; treat them as labels Salesforce and its partners have used for largely the same successor direction, and confirm the current term with your Salesforce contact before you assume you're reading about the same thing across two different articles.

04Why This Is Worth Planning Around, Even Without a Deadline

There's no forced migration and no published end-of-life date, so it's fair to ask why you'd do anything right now. The honest answer is that your quoting process is probably more load-bearing than “which software runs it.”

A working CPQ implementation typically encodes your product catalog and configuration rules, your pricing and discount logic, approval chains, quote templates and contract language, and integrations into your CRM, ERP, and billing systems. None of that disappears because Salesforce stopped selling new CPQ licenses, but all of it is exactly what has to be re-mapped if you ever do move off CPQ. Doing that mapping now, on your own schedule and without a deadline forcing rushed decisions, is a fundamentally different exercise than doing it later under pressure because a business need finally outgrew what CPQ can still do.

05Inventory Your Current CPQ Dependencies

Before deciding anything, it helps to have an honest answer to what's actually built on top of CPQ today. The categories that matter most:

• Product catalog, bundles, and configuration/compatibility rules: what can be sold together, and under what constraints
• Pricing tables, discount tiers, and approval thresholds: who can approve what, and at what discount level it triggers
• Quote templates and any contract-generation logic tied to specific products or terms
• Custom Apex, Flows, or managed-package dependencies built specifically for CPQ
• Integrations: CRM workflows, ERP, billing, e-signature, tax calculation
• Renewal and amendment logic, if any part of your business sells subscriptions

If that list is short, your options are genuinely open, and a decision here is closer to a straightforward software choice. If it's long, meaning years of accumulated pricing rules, approval logic, and integration touchpoints, that tells you something equally useful: the real cost of any future migration lives in the reimplementation of that logic, not in the price of a new license.

06Your Paths Forward

Continue on Salesforce CPQ for now. Reasonable if your implementation is stable, well-understood, and you're not currently blocked on any capability Salesforce has stopped building for CPQ. There is currently no announced deadline forcing an immediate decision.

Plan a migration to Salesforce's successor architecture. Reasonable if you're already committed to the Salesforce platform long-term, want continued native feature investment in your quoting stack, and are willing to treat the move as a real reimplementation project rather than a quick swap.

Evaluate a different CPQ architecture entirely. Reasonable if CPQ's limitations were already a real, specific problem independent of this announcement, and the End of Sale news is simply the trigger that finally makes a larger change worth doing.

None of these is automatically correct, and none of them requires an immediate answer. The right one depends on how much is built on top of your current implementation, how urgently you actually need capability CPQ isn't getting anymore, and how tied your broader tech stack already is to the Salesforce platform.

07What Migration Planning Actually Requires

If you're leaning toward migrating, the real work is dependency mapping, not a license swap. A CPQ migration is closer to a re-architecture of how your business quotes and prices than an upgrade: your product catalog, pricing logic, approval chains, and every integration that touches CPQ today each need a deliberate plan for the target system, not just a data export from one system into another.

That's a large enough topic to deserve its own treatment. We cover what a real migration process actually involves, auditing the current environment, mapping products and pricing logic, reimplementing custom code, testing real quoting scenarios, and cutting over without disrupting live quoting, in a companion article once you've completed the dependency inventory above.

08What to Do Next

There's no clock forcing a decision here, which is exactly why it's worth using the time well: build the dependency inventory above while there's no deadline pressure, and use it to decide which of the three paths actually fits your business. That inventory is also the single most useful artifact you can hand to anyone, internal or external, who ends up scoping the next step.