Navigating the Future of Salesforce CPQ: Product End of Sale (Not End of Life)

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 — but Salesforce is no longer selling new Salesforce CPQ licenses to new customers. Salesforce's investment in quote-to-cash or revenue lifecycle management solutions has shifted to Revenue Cloud Advanced (RCA), part of the Agentforce Revenue Management suite.

This article explains what end of sale actually means for existing Salesforce CPQ customers, how RCA compares, and what you should be thinking about for your quote-to-cash tech stack going forward.

Salesforce CPQ is end of sale, not end of life. These are meaningfully different — and the distinction matters for how you plan your next move.

• End of sale means Salesforce is no longer selling new Salesforce CPQ licenses to new customers. Existing customers keep their licenses, add new users and can continue to renew.
• End of life means a product is no longer supported or maintained. That has not happened with Salesforce CPQ.

Salesforce has shifted its strategic investment and innovation toward the Agentforce Revenue Management product suite — its modern revenue platform for pricing, quoting, contracting, orders, assets, billing, AI agents, and headless revenue workflows.

Within that suite, Revenue Cloud Advanced (RCA) built API First and Composable is the successor to Salesforce CPQ. It supports enterprise product catalog, pricing, quoting, constraint-based config rules, contracting, order management, asset lifecycle management, amendments, and renewals, and can expose those workflows through Salesforce screens, APIs, automation, Agentforce, Slack, partner portals, ecommerce, self-service, and other digital experiences. Approximately 15% of RCA customers are companies who have migrated from Salesforce CPQ.

Revenue Cloud Billing is a separate but complementary product in the Agentforce Revenue Management product suite. Revenue Cloud Billing handles usage rating, invoicing, payments, collections, and financial operations, and is often adopted with Revenue Cloud Advanced to support a complete quote-to-cash process. For the purpose of this article, we will be discussing Revenue Cloud Advanced as the successor to Salesforce CPQ.

Salesforce CPQ is moving into a maintenance phase: existing customers continue to receive support and critical fixes, but new product innovation is focused on Revenue Cloud Advanced (and Revenue Cloud Billing).

There is no forced migration from Salesforce CPQ to Agentforce Revenue Management. Existing CPQ customers do not need to immediately move. But the end-of-sale announcement is an opportunity to rethink your long-term quote-to-cash strategy.

The world has changed since many companies first implemented Salesforce CPQ. Businesses are introducing new revenue models, selling across more channels, moving revenue workflows beyond the traditional CRM interface, and determining how AI should participate in pricing, quoting, contracting, and billing.

For many organizations, this is not about rushing into a migration. It is about using this moment to assess what the business will require in the years ahead. That includes reviewing the current Salesforce CPQ implementation, simplifying product catalogs and pricing logic, evaluating contracting and billing needs, and determining whether the long-term strategy requires Agentforce Revenue Management.

The bottom line: Salesforce CPQ remains a stable, supported solution for existing customers. Revenue Cloud Advanced (for quoting and revenue lifecycle) and Revenue Cloud Billing (for billing and collections) — together under the Agentforce Revenue Management suite — are the strategic path forward for companies that want to modernize their full quote-to-cash operations on the Salesforce platform.

Salesforce CPQ and Revenue Cloud Advanced both help companies configure products, price deals, generate quotes, and move revenue forward. But RCA is not simply CPQ with a new name. They are built on different architectures—one designed primarily for seller-led quoting, and the other for selling across channels, selling via different revenue models and scaling revenue with AI.

The biggest shift is architectural. Salesforce CPQ was built as a managed package designed primarily around seller-led quoting. Over time, many customers added custom scripts, price rules, approval logic, integrations, and workarounds to support new products and processes. That can make Salesforce CPQ powerful, but also harder to adapt as pricing models, sales channels, and customer journeys evolve.

Revenue Cloud Advanced is built natively on the Salesforce platform as a connected and composable revenue engine. It brings together product catalog, pricing, quotes, contracts, orders and assets giving teams and AI agents the context needed to act across the revenue lifecycle.

That architecture also provides more flexibility in how revenue processes are designed. Transactions do not have to follow a fixed opportunity-to-quote-to-order sequence. A company might create a quote without an opportunity, generate an order directly from an ecommerce or in-product purchase, or design a workflow around the way its customers actually buy.

Revenue Cloud Advanced also supports Salesforce’s Headless 360 direction by exposing governed revenue capabilities through APIs, automation, and agent-ready workflows. The Salesforce interface is no longer the only place work can happen. The value sits in the shared data, pricing logic, workflows, controls, and context underneath.

As a result, the same governed capabilities can support sellers in Salesforce, customers in self-service experiences, partners in portals, buyers in ecommerce or in-product journeys, employees in Slack, and AI agents acting on their behalf. When revenue data and processes are connected, AI isn't simply layered on top of disconnected systems. It can reason across customer, product, pricing, contract, order, asset, usage, and billing context‌ — ‌and execute within the rules the business has defined.

The shift from Salesforce CPQ to Revenue Cloud Advanced (RCA) isn't just a product upgrade — it's a move from quote automation to a fully connected, AI-ready revenue platform. Approximately 15% of RCA customers today are companies who have migrated from Salesforce CPQ.

RCA makes the revenue process faster, more flexible, and easier to act on. Reps can configure, quote, and transact from wherever work is happening — whether that is Salesforce, Slack, a partner portal, or another seller-facing experience.

The value isn't just a better UI. It's the flexible revenue foundation underneath. RCA brings product catalog, pricing, quoting, approvals, contracts, orders, and billing logic together on one governed platform, so teams can support more deal structures, pricing models, sales channels, and revenue motions without adding more disconnected steps.

It also makes AI more useful in the selling process. Agents can automate the repetitive work that slows reps down, while augmenting the moments where judgment matters — like offering recommendations, pricing exceptions, renewal actions, and deal risk. That gives sellers more time to build relationships, shape the deal, and close with confidence.

The result is more selling capacity, faster execution, and a revenue process that is easier to navigate — with the flexibility to sell in more ways and the control, consistency, and auditability the business needs.

RCA replaces the legacy CPQ patterns that make change hard — custom scripts, complex price rules, disconnected data, manual reconciliation, and years of accumulated workarounds — with a more declarative, platform-native model.

That means teams can move faster without sacrificing control. They can manage complex agreements, subscriptions, amendments, renewals, pricing changes, and asset transfers on the same trusted Salesforce foundation, instead of stitching together spreadsheets, custom logic, and downstream fixes.

It also gives operations teams clearer visibility across the entire customer lifecycle. Every product sold becomes a dynamic, trackable asset, so teams can see what a customer owns, what they have consumed, what's coming up for renewal, and what needs action — without jumping between systems.

The result is a revenue process that is easier to implement, govern, adapt, and scale. Admins spend less time maintaining fragile workarounds, and operations teams spend less time cleaning up mistakes — giving them more capacity to drive growth, improve efficiency, and build rigor for scale.

The value of RCA shows up in two ways. First, it creates a governed foundation for agents to take action across the revenue process. Because RCA is built natively on the Salesforce platform and aligned to Salesforce's Headless 360 direction, revenue capabilities can be exposed through business process APIs and invocable actions that agents can call directly.

Second, it changes how quickly teams can build, deploy , and adapt revenue processes over time. When pricing, quoting, approvals, and renewals are configured rather than coded — built on a governed, API-accessible foundation — implementation teams, developers, and coding agents all have a cleaner surface to work from. Logic is reusable and consistent across channels, not buried in custom scripts or locked inside a single UI. That makes it meaningfully faster to change a pricing rule, update an approval policy, or extend a process to a new channel — without starting from scratch.

That is a major difference from CPQ’s managed package architecture. CPQ was not designed with a headless or agentic model in mind. Core revenue logic — pricing, quoting, amendments, renewals, and approvals — is often tied to package objects, UI-driven flows, custom scripts, CPQ logic, and implementation-specific workarounds rather than exposed as governed, agent-callable services.

Without that foundation, getting an agent to take meaningful action in CPQ would require custom Apex or bespoke integration work for each step, which is difficult to scale, hard to govern, and not the same as a native, supported agent-ready architecture.

RCA makes both parts native: agents can execute revenue work across channels, and teams can use AI builders and coding agents to deploy, configure, and evolve revenue processes faster.

There is no forced migration. Existing CPQ customers can continue using CPQ under their current contracts, renew licenses, and receive support. Salesforce has been clear: CPQ is not being switched off.

That said, staying on CPQ comes with tradeoffs. CPQ will not receive new features or innovations. As your business requirements evolve — more revenue models, more channels, more complex asset management — CPQ's limitations will become more apparent.

And customers are drawing their own conclusions: 15% of RCA customers today migrated from CPQ managed package. They didn't move because they had to — they moved because the gap between what CPQ could support and what their business needed had become too wide, and they wanted to future-proof their revenue operations for AI and agents before that gap became a blocker.

The right time to migrate depends on your business complexity, your current CPQ configuration, and your tolerance for that growing gap. The risk of waiting isn't immediate. Start with an assessment of your current implementation and identify where CPQ is holding you back before deciding on timing and approach.

The good news: you don't have to figure this out alone. Salesforce has a growing ecosystem of certified partners with deep CPQ-to-RCA migration experience, plus purpose-built tooling designed to accelerate the transition and reduce risk. Whether you're looking for guided migration support or hands-on technical help, there are resources built specifically for this .

Salesforce has evaluated and works with a growing ecosystem of partner-built migration tools designed to accelerate the transition. Forsys provides RevRamp, an AI-powered platform that automates data transformation and schema mapping from CPQ to ARM. IdeaHelix offers purpose-built automation tools that cover the full migration lifecycle, from an estimator that sizes effort and surface risk, to automated conversion of catalog, pricing, quotes, contracts, and assets into ARM format. Prodly offers a migration automation tool, which analyzes your existing CPQ setup, maps products, pricing, rules, and bundles into ARM, and supports ongoing DevOps for ARM post-migration. These tools reduce manual effort and risk, but work best when paired with a certified Salesforce partner who brings deep CPQ-to-ARM transformation expertise.

Moving from Salesforce CPQ to RCA is more than replacing a quoting tool, but it does not have to mean redesigning everything at once. It is an opportunity to improve the areas that create the most friction and prepare revenue processes for evolving pricing models, digital channels, and AI-assisted work.

A thoughtful transition can help teams simplify what they carry forward—such as unnecessary product complexity, outdated pricing rules, custom scripts, manual approvals, and integrations that are difficult to maintain.

It is also a useful time to consider where AI can add value. Which quoting tasks could agents assist with? Where could AI recommend products, pricing, or renewal actions? Which approvals could be automated, and where should people remain in control?

RCA provides a more native, governed foundation for these improvements. With structured data, declarative logic, APIs, and automation, teams can make revenue processes easier to adapt, extend across channels, and support with Agentforce over time.

Start by identifying where CPQ creates the most friction today—slow quotes, manual approvals, pricing exceptions, catalog complexity, billing handoffs, or limited support for new revenue models. Those priorities can guide a practical migration plan and help teams decide what to preserve, simplify, or improve.