Salesforce CPQ Is Winding Down. Should You Move to Agentforce Revenue Management Now? Posted by
Greg ParashisIn early 2025, Salesforce announced the end of sale for CPQ licenses. Existing customers still get support, but the roadmap is clear. All new investment is going into CPQ’s successor, Agentforce Revenue Management (ARM). If you’re running CPQ today, the question isn’t really whether you’ll eventually move to ARM. It’s whether you move on your own timeline or wait until CPQ’s limitations start costing you deals.
ARM is a bigger product than CPQ ever was
ARM isn’t a new version of CPQ with a fresh coat of paint. It extends into contract lifecycle management, order fulfillment, and revenue orchestration, covering the full revenue process in a single product. Because it’s built natively on the Salesforce platform, you’re no longer working within the constraints of a managed package. ARM also exposes headless APIs, so it’s straightforward to call ARM processes from external systems rather than being boxed into the Salesforce UI.
The CPQ pain points ARM was built to fix
Anyone who has administered CPQ for a while will recognize these problems. Salesforce addressed each one directly in ARM’s design.
Quote line scale. CPQ quotes could bog down or hit limits well before a deal got complicated. ARM quotes support up to 1,000 lines, which removes the need to split large deals across multiple quotes or opportunities. A context service layer sits between the pricing engine and the underlying data objects, handling that volume while keeping the quoting interface responsive.
Product Selling Models. In CPQ, selling the same product both one-time and on a payment schedule usually meant creating duplicate product records. ARM lets a single product support multiple selling models, giving sales reps flexibility without the administrative overhead of maintaining duplicates.
Buying options showing OneTime and TermDefined Annual pricing for the same product.
Custom Pricing Procedures. CPQ’s pricing waterfall was fixed and often difficult to troubleshoot when something priced incorrectly. ARM ships a standard pricing procedure out of the box, but also lets you build your own using a flow-style interface. You can add, remove, or reorder pricing elements and simulate the logic against a sample record before it goes live.
Attribute Inheritance. Shared attributes are now managed in one place instead of being repeated across products. Adding or updating a product is faster, and there’s less ongoing administrative overhead to keep everything consistent. You can also see at a glance which attributes are inherited versus overridden at the product level.
Product attributes page showing inherited attributes and an overridden inherited attribute.
What’s genuinely new for CPQ customers
Two capabilities in ARM don’t have a real equivalent in CPQ, and they’re worth paying attention to on their own.
Contract Lifecycle Management (CLM). CLM connects directly to the quoting process and handles the creation, negotiation, and storage of legal documents. Sales teams can generate branded proposals and contracts with the correct legal language already in place based on what’s being sold. Built-in review and approval steps keep deals moving without the usual back-and-forth over redlines and versions.
Order Orchestration. This manages complex order processes from fulfillment through billing. A visual design canvas breaks a commercial order down into the technical fulfillment orders that downstream systems need to execute on. Real-time visibility into dependencies reduces order failures, and tasks like compensation, revenue recognition, and delivery kick off automatically as the order progresses.
Order orchestration canvas showing a fulfillment flow from shipping through invoice email.
The case for moving sooner rather than later
CPQ is a maturing product that has seen little meaningful development over the past five or more years, and that isn’t going to change now that Salesforce has shifted its investment to ARM. The gap between what CPQ can do and what modern revenue operations demand will only widen from here.
For businesses still running Salesforce CPQ, migrating to Revenue Cloud should be a near-term priority, not a someday project. Moving now puts you on a platform with active development behind it and a growing ecosystem built around it, rather than one that’s effectively in maintenance mode.
If you’re weighing what a CPQ-to-ARM migration would actually involve for your org, that’s a conversation worth having before the decision gets made for you by an unsupported feature or a deal you can’t configure. Our Agentforce Revenue Management consulting services can help you plan that move on your own timeline.
CloudMasonry is a Salesforce Select Partner helping organizations design, optimize, and scale their Salesforce ecosystems across Sales Cloud, Service Cloud, Revenue Cloud, Data Cloud, and Agentforce.
Greg ParashisIn early 2025, Salesforce announced the end of sale for CPQ licenses. Existing customers still get support, but the roadmap is clear. All new investment is going into CPQ’s successor, Agentforce Revenue Management (ARM). If you’re running CPQ today, the question isn’t really whether you’ll eventually move to ARM. It’s whether you move on your own timeline or wait until CPQ’s limitations start costing you deals.
ARM is a bigger product than CPQ ever was
ARM isn’t a new version of CPQ with a fresh coat of paint. It extends into contract lifecycle management, order fulfillment, and revenue orchestration, covering the full revenue process in a single product. Because it’s built natively on the Salesforce platform, you’re no longer working within the constraints of a managed package. ARM also exposes headless APIs, so it’s straightforward to call ARM processes from external systems rather than being boxed into the Salesforce UI.
The CPQ pain points ARM was built to fix
Anyone who has administered CPQ for a while will recognize these problems. Salesforce addressed each one directly in ARM’s design.
Quote line scale. CPQ quotes could bog down or hit limits well before a deal got complicated. ARM quotes support up to 1,000 lines, which removes the need to split large deals across multiple quotes or opportunities. A context service layer sits between the pricing engine and the underlying data objects, handling that volume while keeping the quoting interface responsive.
Product Selling Models. In CPQ, selling the same product both one-time and on a payment schedule usually meant creating duplicate product records. ARM lets a single product support multiple selling models, giving sales reps flexibility without the administrative overhead of maintaining duplicates.
Buying options showing OneTime and TermDefined Annual pricing for the same product.
Custom Pricing Procedures. CPQ’s pricing waterfall was fixed and often difficult to troubleshoot when something priced incorrectly. ARM ships a standard pricing procedure out of the box, but also lets you build your own using a flow-style interface. You can add, remove, or reorder pricing elements and simulate the logic against a sample record before it goes live.
Attribute Inheritance. Shared attributes are now managed in one place instead of being repeated across products. Adding or updating a product is faster, and there’s less ongoing administrative overhead to keep everything consistent. You can also see at a glance which attributes are inherited versus overridden at the product level.
Product attributes page showing inherited attributes and an overridden inherited attribute.
What’s genuinely new for CPQ customers
Two capabilities in ARM don’t have a real equivalent in CPQ, and they’re worth paying attention to on their own.
Contract Lifecycle Management (CLM). CLM connects directly to the quoting process and handles the creation, negotiation, and storage of legal documents. Sales teams can generate branded proposals and contracts with the correct legal language already in place based on what’s being sold. Built-in review and approval steps keep deals moving without the usual back-and-forth over redlines and versions.
Order Orchestration. This manages complex order processes from fulfillment through billing. A visual design canvas breaks a commercial order down into the technical fulfillment orders that downstream systems need to execute on. Real-time visibility into dependencies reduces order failures, and tasks like compensation, revenue recognition, and delivery kick off automatically as the order progresses.
Order orchestration canvas showing a fulfillment flow from shipping through invoice email.
The case for moving sooner rather than later
CPQ is a maturing product that has seen little meaningful development over the past five or more years, and that isn’t going to change now that Salesforce has shifted its investment to ARM. The gap between what CPQ can do and what modern revenue operations demand will only widen from here.
For businesses still running Salesforce CPQ, migrating to Revenue Cloud should be a near-term priority, not a someday project. Moving now puts you on a platform with active development behind it and a growing ecosystem built around it, rather than one that’s effectively in maintenance mode.
If you’re weighing what a CPQ-to-ARM migration would actually involve for your org, that’s a conversation worth having before the decision gets made for you by an unsupported feature or a deal you can’t configure. Our Agentforce Revenue Management consulting services can help you plan that move on your own timeline.
CloudMasonry is a Salesforce Select Partner helping organizations design, optimize, and scale their Salesforce ecosystems across Sales Cloud, Service Cloud, Revenue Cloud, Data Cloud, and Agentforce.