Moving from Salesforce CPQ to Agentforce Revenue Management (ARM)? The Real Challenge Is Your Data

Salesforce is moving everyone from CPQ to Agentforce Revenue Management (ARM). There isn't an official end-of-life date for CPQ yet, but Salesforce has already marked it "end of sale" for new customers. The message is clear. CPQ's end of life is coming, whether that's next year or two years from now. If you're on CPQ today, there's a high chance you'll be moving to ARM eventually.

Let's talk about what actually keeps people up at night. The data.

The alphabet soup that is Salesforce product names 

If terms like RLM, RCA, and ARM make your head spin, you're not alone. Here's what each one means.

Salesforce CPQ (CPQ) The original product built from the SteelBrick acquisition, which Salesforce turned into its CPQ product. It runs as an add-on package on top of Salesforce. It's now "end of sale," but still active for existing customers.

Revenue Lifecycle Management (RLM) A new quoting tool Salesforce built directly on its core platform, with a brand-new pricing engine. This is why moving your data today is a real transformation, not a simple move.

Revenue Cloud Advanced (RCA) The rebranded, renamed version of RLM.

Agentforce Revenue Management (ARM) The current, official name. Everything since RLM has really been the same product renamed. Most people still call it RCA, but ARM is the name Salesforce uses now.
‍

For this article, we'll use ARM as the name going forward.

Moving CPQ data into ARM is a data transformation, not a data migration

When people hear "data migration," they picture moving data from one system into another. That's not what's happening here.

You're staying in the same Salesforce org. Your data is already sitting there. You just need to transform it from CPQ's data structure into ARM's data structure.

CPQ runs on its own object structure and its own licenses. Once you lose those licenses (whether that happens tomorrow or two years from now) you lose access to those records. That risk is what's pushing many teams to move from CPQ to ARM now.

Can I just use a custom object instead of migrating my CPQ data?

You could build a custom object that doesn't need a license and mimic the old structure. Totally doable. So why go through the work of a real transformation?

Two words. Amendments and renewals.

Here's an example. Say you sold a deal in CPQ, and now the customer wants to add one more unit. That's an upsell, and to price it correctly, you need to know what you originally charged for that product. Then you can sell the new unit at the same price. A custom object that just mimics your old data won't carry that price history over. A real data transformation will.

Where the transformation gets hard

Think of CPQ and ARM as a Venn diagram. The overlap is one specific object, order products.

An order product record represents that exact transaction for that exact product.

An order product record represents one exact transaction for one exact product. Think of it like a receipt from a grocery store. The store can sell that same product again, and you can buy it again, but that particular receipt is tied to that one specific transaction.

Both systems create order product records, but CPQ doesn't use that record downstream. ARM does.

This creates a second problem. There's a field on the order product called Product Selling Model, or Product Selling Model Options, that ARM needs in order to "assetize" the deal.

Assetizing is ARM's term for building all the downstream records, contracts, orders, assets, asset actions, and more.

The Product Selling Model field defines how the product is sold, One-Time, Term-Defined, or Evergreen.
‍

Here’s the catch. The Product Selling Model field can ONLY be populated upon record creation.
‍

When CPQ created that order product two years ago, it left the field blank, because CPQ never needed it. CPQ doesn't reference the order product record downstream, so there was never a reason to fill it in.

Now ARM needs that field populated, but the field can only be set on creation, and that record was created years ago. Even a system admin with full permissions can't edit it. It's locked.
‍

ARM relies on that field to build everything it needs to manage a deal. If the field is blank, ARM can't set up your old CPQ deals for amendments or renewals. Your data is sitting right there in your org, and you can't do anything with it.
‍

There's also a set of related records tied to this process that most teams don't know exist. They have to be created in a specific order. Create them out of order, and the process breaks.

How do you get actionable CPQ data into Agentforce Revenue Management?

You can't press a button in ARM and turn your CPQ history into ARM's downstream records. ARM's native assetization process doesn't reach back into your existing CPQ data.

So we rebuilt that assetization process with Apex. It reads your CPQ data, outputs ARM data in the correct order, and populates the locked fields automatically. 

The result is actionable CPQ data inside ARM. Data you can run amendments and renewals against, priced correctly, without losing your history.

If the data is what's holding you back

Most teams we talk to already know CPQ is heading toward end of life. Their hesitation isn't whether to move to ARM. It's the data transformation, and the price tag they assume comes with it.

If you're on CPQ, eyeing ARM, and the data is what's holding you back, that's exactly the problem we solve. You already have your CPQ data. We can transform it into actionable ARM data, ready for your amendments and renewals.

Want to talk through what yours would look like? Get in touch.

‍