Moving from Salesforce CPQ to Agentforce Revenue Management: Don't Wait Until the Clock Runs Out

By Elle Fettig, Vice President, Revenue Transformation Practice

If your organization runs on Salesforce CPQ (Configure, Price, Quote), changes are underway. In early 2025, Salesforce officially ended the sale of new CPQ licenses. It's not shutting off tomorrow, but for most companies, the renewal window has already closed, which means it's time to decide what's next and when to act.

Many organizations are planning their move to Salesforce’s next-generation product, Agentforce Revenue Management (ARM), which unifies the entire revenue lifecycle, from product setup and quoting through billing, fulfillment, and revenue recognition.

While CPQ’s architecture worked well enough for straightforward quoting, it was never designed to handle the complexity of modern revenue models. ARM, on the other hand, can support subscriptions, usage-based billing, partner channels, and dynamic pricing – all with less custom code, fewer workarounds, and continuous investment from Salesforce.

Why the CPQ-to-ARM migration can be complex

While the benefits of migrating to ARM are clear, the process can be complex, with implementations often taking many months.

A CPQ-to-ARM migration is not an upgrade. It's a full revenue operations transformation with two distinct workstreams involved. The first is business logic: product rules, pricing configurations, and compatibility settings, all of which must be extracted, reconfigured, and validated in the new system. The second is record data: in-flight quotes, active orders, and invoices that can’t be interrupted mid-cycle. 

Both workstreams require extreme precision because the data in motion is financial.

In addition to the data migration, a migration to ARM typically requires business process modernization, which can be challenging but presents a significant opportunity for optimization.

How Thunder can help accelerate your migration

The complexity of a CPQ-to-ARM migration is real, but it doesn't have to slow you down. Thunder has deep experience on both sides of this transition, with a technical team that knows CPQ's data model inside and out and has built meaningful ARM implementation expertise across high-tech, consumer business services, and manufacturing clients. In fact, we recently completed an ARM upgrade in just six weeks.

We are also very strategic and thoughtful in how we approach these projects. For example, we are not committed to only conducting “big bang” implementations across an entire enterprise. We’ll often migrate a single business unit, region, or partner segment, while enabling systems to run in parallel to reduce business disruption.

We're also developing a proprietary toolkit designed to accelerate the CPQ-to-ARM migration. Built to automate data extraction, transformation, and loading, the toolkit is designed to reduce the manual lift and risk that comes with moving financial records between systems, without sacrificing the precision these migrations demand. Data cleanup occurs in parallel, along with risk flagging, to keep the migration moving smoothly.

Getting the migration right pays off well beyond the project itself. Organizations that approach this as a true transformation, not just a system swap, are better positioned to unlock new revenue channels – from usage-based pricing to partner and customer portals – that CPQ was never built to support.

There’s also an AI angle worth considering. A clean, well-executed migration means your historical data has a unified home in ARM's native architecture. Skip or rush the migration, and you risk fragmented data that limits the return on investment of any AI initiative built on top of it. Upgrading ARM also enables organizations to leverage Agentforce, Salesforce’s suite of autonomous AI agents, which opens a whole new world of possibilities for efficiency gains.

The bottom line: the CPQ clock is already running. Organizations that get ahead of the deadline, with the right partner and the right approach, will be better positioned to capture the full value of ARM, rather than scrambling to migrate under pressure.

‍