In early 2026, Salesforce did something that went largely unremarked across most CRM teams: it renamed Revenue Cloud. The product is now called Agentforce Revenue Management. The Spring ’26 release notes carry it as the new official name, and the feature set has been substantially updated to match, with AI agents woven through quoting, billing, and order orchestration in ways that were not possible under the previous architecture.
Most organisations saw it as a branding exercise. It is not. When Salesforce moves something inside the Agentforce umbrella, that decision signals where future investment will go. It also signals, indirectly, what is being deprioritised: the older, Steelbrick-derived architecture that the majority of companies still refer to as “Salesforce CPQ.”
For revenue operations leaders, sales operations teams, and CRM administrators who carry responsibility for a quote-to-cash process built on that older product, this is worth paying close attention to. Not because migration is urgent tomorrow, but because the direction of the platform has become explicit in a way it was not a year ago.
What is Agentforce Revenue Management, and why does the name change matter?
Agentforce Revenue Management is Salesforce’s native quote-to-cash platform, covering configure-price-quote (CPQ), contract management, billing automation, order orchestration, and now agentic AI across the full revenue lifecycle. It was previously called Revenue Cloud, and before that the product was known as Salesforce CPQ following the acquisition of Steelbrick in 2015. Each name change has reflected a genuine architectural shift, not merely a repositioning exercise.
The Agentforce prefix carries practical significance. It confirms the product is being built on Salesforce’s AI agent framework, which means new capabilities will be structured around autonomous agents rather than conventional workflow automation. The Spring ’26 release already introduced product recommendation agents during quoting and conversational AI assistants for billing queries. Those capabilities did not exist in the prior version, and they will not be backported to the old CPQ product.
For organisations evaluating whether to stay on their current CPQ configuration or invest in the new platform, the name change is a directional signal worth treating as information rather than noise. Salesforce has a consistent record of concentrating engineering effort on the products it names as strategic. Revenue Cloud earned that designation in 2021. Agentforce Revenue Management earns it in 2026 at a meaningfully higher level of commitment.
The architectural gap that legacy CPQ never fully closed
To understand why the rebrand matters in practical terms, it helps to understand what Salesforce CPQ actually was architecturally. When Salesforce acquired Steelbrick, it inherited a product designed to run alongside Sales Cloud rather than inside it. The core objects, the pricing engine, and the quoting logic sat largely outside the native Salesforce data model. That design made CPQ powerful for its time, but it also made the product brittle over time: customisations accumulated quickly, upgrades became risky, and the gap between what the CPQ recorded about a deal and what lived in the rest of the Salesforce org was a persistent source of data inconsistency.
Agentforce Revenue Management was rebuilt on native Salesforce architecture from the ground up. The product catalog, pricing logic, and billing objects are part of the same data model as Sales Cloud, Service Cloud, and the rest of the platform. That is a fundamental difference, not an incremental one, and it is the reason why the feature velocity on the new platform is significantly faster than anything available on the old CPQ.
It also means that moving from old CPQ to the new platform is not an upgrade in any conventional sense. It is a migration, with all the complexity and planning that word implies. Recognising that gap early, before a contract renewal or a commercial model change forces the decision, is what gives revenue and CRM teams meaningful options rather than reactive ones.
What Spring ’26 actually delivered: features worth understanding
The Spring ’26 release for Agentforce Revenue Management was substantial enough to merit a closer look beyond the headline rebrand. A new Promotions Engine allows pricing designers to create eligibility-based discount rules that apply automatically during transactions, a meaningful step for organisations that have historically managed discount exceptions manually within individual quotes. The enhanced pricing logic now supports multi-level discount formulas with up to five levels of nesting, as well as conditional expressions, without requiring custom Apex code to implement them.
For operations teams handling contract amendments, the platform now processes future-dated changes without requiring cancellation and recreation of the existing order, which removes one of the most time-consuming manual workarounds in the legacy product. Billing capabilities were extended with order-item-level billing, flexible frequency settings, and rule-based payment automation, which collectively reduce the manual close-and-collect effort for organisations running recurring revenue models.
None of these capabilities are available to organisations on the old CPQ architecture, and they will not be. Salesforce is building the new platform at a pace that makes replication through customisation of the old product increasingly impractical. The feature gap between the two widens with every release cycle, which is precisely the dynamic that makes deferring the migration question progressively more costly the longer it runs.
Why CPQ migrations are more complex than most project plans assume
The most consistent underestimate in any CPQ migration project is the scope of what the existing configuration actually contains. In organisations that have been running Salesforce CPQ for more than two years, the product catalog is rarely clean. Products have been deactivated rather than removed. Pricing rules have been layered on top of one another as workarounds for commercial edge cases. Price books reflect historical deals that no longer represent current commercial models. The CPQ configuration accumulates the sediment of every compromise made under time pressure across multiple sales cycles.
Migrating to Agentforce Revenue Management requires rationalising that sediment before rebuilding on the new architecture. This is not a technology problem in the first instance. It is a commercial process problem, and it requires sales operations, finance, and commercial leadership to agree on what the current product and pricing model actually is. That alignment is frequently harder than it sounds, because the CPQ has often quietly drifted away from the canonical commercial model without anyone formally acknowledging the gap.
Organisations that navigate CPQ migrations successfully tend to do two things differently from those that struggle. They treat the data and catalog cleanup as a first-class workstream rather than an assumption buried in implementation planning. And they involve commercial stakeholders from the beginning rather than presenting a solution to them at user acceptance testing, which is the most expensive point at which to discover misalignment.
When does migrating to Agentforce Revenue Management make commercial sense?
Not every organisation running Salesforce CPQ needs to migrate in 2026. The right answer depends on the nature of the revenue model, the maturity of the existing implementation, and the commercial roadmap for the next two to three years.
Migration tends to have a clear business case for organisations that have moved, or are actively moving, toward subscription or usage-based pricing. The billing and contract management capabilities in Agentforce Revenue Management are specifically designed for recurring revenue models and will reduce meaningful manual effort where those models are central to the business. Similarly, multi-entity organisations managing complex discount hierarchies or multi-currency billing scenarios will find the native architecture substantially easier to maintain than an equivalent configuration built on top of the old CPQ objects.
For manufacturing and industrial companies using CPQ primarily for complex product configuration with standard pricing models, the calculus is different. Salesforce’s Industries CPQ (formerly built on the Vlocity platform) remains the appropriate choice for deep product configurators in those sectors, and the migration question looks materially different there than it does in a SaaS or professional services context. Getting that distinction right before committing to a roadmap matters considerably for both budget and timeline accuracy.
What tends to make migration genuinely urgent is the combination of an upcoming contract renewal and a commercial model that has already outgrown the existing configuration. Renewals are a natural forcing function: they coincide with commercial model reviews and provide budget justification for the data cleanup work that any migration requires. Organisations that surface the issue proactively ahead of a renewal cycle typically have more options than those who wait until the platform change becomes unavoidable.
The data quality problem that sits underneath every revenue AI initiative
The timing of this platform shift is instructive because it coincides with a measurable change in how sales and revenue teams are approaching AI. Salesforce’s State of Sales report for 2026 found that 87 percent of sales organisations are now using some form of AI, and that 51 percent of sales leaders using AI identify disconnected systems as their primary obstacle. Those two findings together describe precisely the problem that Agentforce Revenue Management is positioned to solve, and precisely the problem that a poorly maintained CPQ implementation creates.
AI agents in a revenue context are only as reliable as the data they can access and reason over. A product catalog containing inactive records, a price book with inconsistent discount logic, or billing data that does not reconcile with opportunity records in the CRM will produce unreliable agent outputs regardless of how sophisticated the underlying model is. The capability announcements from Salesforce are genuine, but the limiting constraint is almost never the platform. It is the data foundation beneath it.
This is the harder question the Agentforce Revenue Management rebrand raises, and it receives considerably less coverage than the feature announcements. The new platform can do substantially more than its predecessor. Whether any given organisation can make practical use of that capability depends on whether the revenue data is in a state that supports it. For most organisations that have been running CPQ for several years without a formal data quality programme, that is an honest question worth examining before making platform investment decisions.
The Sirocco perspective
We work with organisations across the full Salesforce Revenue Cloud and CPQ landscape, and the pattern we see most consistently is one of deferred decisions. Teams recognise that their CPQ configuration has become unwieldy. They know the platform direction has changed. And they are waiting, either for a forcing function or for a clearer case to act. The Spring ’26 rebrand to Agentforce Revenue Management is about as clear a directional signal as Salesforce has offered in recent years.
That does not mean migrating immediately, but it does mean being deliberate rather than passive about the choice to wait. An organisation that understands the gap between its current CPQ state and the new platform, and has a credible plan for bridging it, is in a very different position from one that has simply deferred the question. The difference tends to show up in cost and in timeline when the decision eventually becomes unavoidable.
If your organisation is evaluating its Revenue Cloud position, considering a CPQ refresh, or trying to understand what the Agentforce Revenue Management migration involves for your specific configuration and commercial model, we are happy to help you think it through. Schedule a consultation with the Sirocco team and we can start with an honest assessment of where you are and what the realistic path forward looks like.
Get in Touch
Evaluating your Salesforce CPQ position or planning a move to Agentforce Revenue Management? Our team works with organisations at every stage of that journey.
