Salesforce CPQ to
Agentforce Revenue Management:
A Migration Guide

Salesforce CPQ reached end of sale in March 2025, and every CPQ customer now faces the same planning question: when and how to move to its successor, Agentforce Revenue Management. This guide lays out how CloudMasonry structures these migrations, what maps cleanly, what does not, and the decisions that determine whether the project takes weeks or quarters.

Why is this a migration and not an upgrade?

Salesforce CPQ is a managed package with its own objects and a rules engine that customers spent years configuring. ARM is built natively on core platform objects with an API-first design and a declarative pricing engine. There is no converter that turns one into the other, and honestly, you would not want one: most mature CPQ orgs carry years of accumulated workarounds, and copying them forward would recreate today’s problems on a new platform. The migration is the opportunity to rebuild the revenue process the way it should work.

Salesforce CPQ vs Agentforce Revenue Management at a glance

The five phases of a CPQ-to-ARM migration

1. Assessment

Inventory what exists: the product catalog and bundle structures, every price rule and product rule, quote templates, approval chains, custom scripts, and integrations (ERP, e-signature, document generation). The output is a map of what carries forward conceptually, what gets redesigned, and what gets retired. This phase is where the project timeline actually gets determined, and skipping it is the single most common cause of migration overruns.

2. Catalog and pricing redesign

ARM’s Product Catalog Management and pricing procedures work differently from CPQ’s product and price rules, which is a feature: pricing logic that took dozens of interlocking CPQ rules often collapses into a few maintainable pricing procedures. Design the target state on paper before building, with sales, finance, and operations signing off on the catalog structure and discounting policy.

3. Build and integrate

Configure the catalog, pricing, quoting flows, and contract and order handling in a sandbox, and rebuild integrations against ARM’s APIs. Teams coming from CPQ usually find the API-first architecture opens options they did not have before, such as headless quoting for portals and partner channels.

4. Parallel validation

Before anyone cuts over, run the two systems side by side against real scenarios: take a representative set of actual quotes and verify ARM produces the same products, prices, and totals that CPQ did (or intentionally different ones, where you fixed policy). Quote parity testing is tedious and completely non-negotiable; it is what makes the finance team comfortable signing off.

5. Cutover and hypercare

Move new business to ARM (usually by team or segment rather than all at once), keep CPQ read-only for historical reference, and staff a hypercare period where the delivery team resolves issues in hours rather than sprint cycles. In-flight quotes and renewals need explicit handling rules, decided in advance rather than discovered at cutover.

What does not map one to one?

• Price rules and product rules. Rebuilt as pricing procedures and constraint rules; expect consolidation rather than translation.
• Quote document templates. Regenerated in the new tooling rather than imported.
• Custom scripts and plugins. CPQ’s JavaScript quote calculator plugins have no direct equivalent; their logic moves into pricing procedures, Flows, or Apex.
• Historical quotes and contracts. Typically stay in place for reference rather than being converted; active contracts and renewable assets are the data that genuinely migrates.

How long does it take, and who should be involved?

In our delivery experience, most CPQ-to-ARM migrations run anywhere from six weeks to six months: the short end for focused catalogs with straightforward pricing, the long end for enterprise deployments with heavy customization and multiple integrations. The team that makes it work is cross-functional by necessity: sales operations for the catalog and process, finance for pricing policy and billing, IT for integrations, and an implementation partner that has seen both architectures. CloudMasonry’s revenue platform practice runs these assessments and migrations; the background on why the clock is ticking is in our CPQ end-of-sale guide, and our team can scope your situation honestly, including telling you if waiting is the right call.