Author: Ethan Garonzik, CEO & Founder of Vendori

“We already use Salesforce. How much work could moving to its newer CPQ really be?”

It’s a reasonable question. Your customer records are there. Your sales team works there. You’ve already invested time and money getting Salesforce CPQ to support the way you sell.

But the work behind your quotes goes well beyond the CRM. There’s the pricing rule someone built for a customer three years ago. The approval that routes differently for multiyear deals. The renewal spreadsheet Finance still checks because nobody fully trusts the system.

When you evaluate Revenue Cloud Advanced, you need to understand what happens to all of it.

Moving from Salesforce CPQ to Revenue Cloud Advanced is an architecture decision, not a version upgrade. Salesforce’s migration guidance describes changes to the way products, pricing, contracts, orders, and customer assets work together. For RevOps, that means evaluating how the business will operate before committing to the move.

Do existing Salesforce CPQ customers have to migrate?

No. Salesforce says there is no forced migration. Salesforce CPQ is end of sale, not end of life. Existing customers can continue using it, renew licenses, add users, and receive support under their applicable terms. Salesforce has not announced an end-of-life date, although new product investment has shifted toward its newer revenue platform.

That gives you time to make a business decision.

If quoting works reliably and maintenance is manageable, there may be no immediate reason to move. If every pricing change turns into a project or renewals require hours of manual work, you have a stronger reason to evaluate your options.

Our Salesforce CPQ status guide explains the product’s current status in more detail.

What changes when moving from Salesforce CPQ to Revenue Cloud?

The way you organize products and calculate prices

Your catalog probably contains a mix of deliberate choices and things that were convenient to build at the time.

Maybe the same product has separate entries for annual and multiyear agreements. Maybe a bundle exists for one large customer. Maybe nobody remembers why two nearly identical pricing rules run in a particular order.

RCA gives you a different framework for organizing products and defining how they are sold. Salesforce documents product classifications and selling models, including ways to separate the customer-facing catalog from fulfillment requirements. CPQ also supports configuration attributes, so a useful comparison needs to go beyond checking whether both products have a feature.

Pricing changes too. Salesforce CPQ uses price rules and other pricing tools, sometimes supplemented by custom calculation scripts. Revenue Management uses pricing procedures made up of defined calculation steps. Your existing pricing behavior needs to be understood and expressed in that framework.

For the evaluation, bring a real deal: increasing seat counts across three years, a negotiated discount, and a renewal provision Sales promised the customer.

Ask the team to build it. Then change the start date or add another product. You want to see the right answer, understand how the system reached it, and know who can safely change the logic later.

What happens after the customer signs

An accurate first quote is only part of the job.

Six months later, the customer adds licenses. At renewal, they remove an add-on but keep a negotiated rate on the original subscription. Finance needs the updated billing information, and Customer Success needs to know what the customer now owns.

Salesforce’s newer platform emphasizes asset lifecycle management, including amendments, renewals, and cancellations. Its migration guidance addresses moving subscriptions into the Customer Asset Lifecycle Management model.

The practical test is whether your existing agreements remain usable throughout those changes. Can the team find the right terms, calculate the adjustment, and pass accurate information downstream without rebuilding the deal in a spreadsheet?

Run the same scenario through RCA and any alternative you evaluate. It will tell you more than a polished demonstration of a brand-new sale.

The reports and connections around CPQ

Staying in Salesforce doesn’t guarantee that everything connected to CPQ keeps working unchanged.

Salesforce says integrations that reference CPQ custom objects must be remapped to Revenue Management’s standard objects. Reports and automations that depend on those objects also need attention.

That could affect the report Finance uses every Friday, the fields your billing system reads, or the dashboard that tells Customer Success which renewals are coming up.

Before approving the project, ask for a clear explanation of what changes outside the quoting screen. Include those changes in the estimate rather than discovering them during testing.

Be equally specific about billing. Revenue Cloud Advanced includes certain billing capabilities, while others require Revenue Cloud Billing. Ask vendors to distinguish what they demonstrated from what your proposed licenses include.

How difficult is a Salesforce CPQ migration?

There is no single answer. The effort depends on your configuration, data, integrations, available expertise, and how much you want to change. Salesforce identifies those factors in its migration guidance.

Importantly, moving to RCA does not automatically mean redesigning everything. Salesforce documents approaches ranging from migration with minimal redesign to selective changes and broader rebuilding. The choice affects both the work required and the capabilities you can use afterward.

When someone gives you a timeline, ask what it includes. Preserving an existing catalog is a different project from simplifying it. Moving active agreements is different from transforming years of historical transactions. Testing new quotes alone is different from validating amendments, renewals, and billing handoffs.

Our Salesforce CPQ Migration Checklist covers the detailed planning. At this stage, you need enough clarity to compare options and understand the commitment each requires.

Who will make changes after go-live?

This is one of the most useful questions to ask during a CPQ evaluation: “Show us how our team would make this change after your implementation team leaves.”

Choose something ordinary. Add a package. Change a discount threshold. Introduce a customer-specific price. Update a renewal policy while preserving existing agreements.

Then establish who does the work, what needs testing, and when technical support becomes necessary.

Apply this test to every platform, including Vendori. “Native,” “declarative,” and “no-code” describe an approach; your team still needs to see what maintaining it involves.

Use the same discipline when comparing costs. Include licenses, additional products, implementation, internal time, training, and ongoing support. An attractive subscription price can tell you very little about the effort required to keep deals moving.

When Revenue Cloud Advanced may be the right fit

RCA deserves serious consideration when your company wants to manage more of its revenue operations within Salesforce and has a clear business reason for the broader scope.

For example, you may want shared product and pricing management across sales channels, more coordinated order and fulfillment processes, or deeper management of customer assets in Salesforce.

In our view, the strongest fit combines those needs with the budget, expertise, and ownership to support the platform. The decision should connect its capabilities to work your business actually needs to do.

When another CPQ may make more sense

A different CPQ deserves a look when your priorities are easier pricing changes, less administrative work, and quoting processes your team can manage with its available resources.

You may plan to retain Salesforce as your CRM and keep the billing system that already works for Finance. You may need stronger subscription workflows without expanding the project into a broader replacement of revenue systems.

Vendori is a no-code CPQ platform for SaaS, AI, and B2B technology teams, with Salesforce and HubSpot integrations. It is an option to evaluate when business ownership of products, pricing, and quoting is a priority. Ask it to handle the same difficult deals and routine changes you use to test RCA.

Our Salesforce CPQ alternatives guide can help you build a shortlist. For more on the operational frustrations that prompt an evaluation, read Why Companies Are Leaving Salesforce CPQ.

Before you choose, agree on these five things

You don’t need every implementation detail settled to choose a direction. You do need agreement across Sales, RevOps, Finance, and IT on:

1. The improvement you’re buying. Be specific about delays, manual work, maintenance costs, or capabilities the business needs.

2. The scope of the change. Is this a CPQ replacement or a broader revenue systems project?

3. The deals it must handle. Validate your difficult scenarios through amendments, renewals, and downstream handoffs.

4. The people who will run it. Identify who owns routine changes and where outside help is needed.

5. The full cost and expected return. Include implementation and ongoing work alongside licensing.

Salesforce CPQ, RCA, and other CPQ platforms should be evaluated against those answers. Familiarity with the vendor is useful, but it can’t make the decision for you.

Frequently asked questions

What is Salesforce Revenue Cloud?

Revenue Cloud is the name Salesforce has used for its newer revenue management offering, now also marketed as Agentforce Revenue Management. It covers areas such as products, pricing, quoting, contracts, orders, and customer assets. Available features depend on the products and licenses purchased.

Is Revenue Cloud Advanced replacing Salesforce CPQ?

Salesforce positions RCA as CPQ’s successor, but existing CPQ customers are not required to migrate immediately. They can continue using the supported product while evaluating their options.

Is Revenue Cloud Advanced a direct upgrade?

No. Moving to RCA involves a different architecture and requires evaluating data, configuration, and connected processes. The extent of redesign depends on the migration approach.

Should we evaluate alternatives before migrating?

Yes. Comparing options helps you determine whether RCA’s scope and maintenance requirements fit your business. Include remaining on your current implementation for now as a valid option if it continues to meet your needs.

Ready to work through your next move?

Use the Salesforce CPQ Migration Checklist to assess what your products, pricing, data, and customer workflows will require.

If you’re still comparing platforms, download the CPQ RFP Toolkit to give each vendor the same requirements and make their answers easier to compare.