Salesforce CPQ to Revenue Cloud Advanced: Cost, Timeline and What Actually Drives Them
By the Selectiva team · Last updated October 2026
For many mid-market companies, moving from Salesforce CPQ to Revenue Cloud Advanced takes roughly three to six months, though that range assumes moderate complexity and isn’t a promise. The implementation cost depends far more on your product catalog, your pricing exceptions and your ERP connections than on the software itself, and a short discovery phase is the quickest way to get a number you can actually budget against.
Ask ten consultants what a CPQ migration costs and you’ll hear ten different figures. Part of that is sales posturing. Mostly, though, it’s because no two CPQ orgs look alike once you open them up.
We’ve opened up quite a few. The companies that overspend usually tried to rebuild every old price rule exactly as it was, including rules nobody on the current team could explain.
Is Salesforce CPQ going away?
Not on any announced date. Salesforce has moved CPQ to end of sale, not end of life. Existing customers keep their support and can renew. New customers can’t buy it, and new development goes into Revenue Cloud Advanced.
A quick note on names: Salesforce has used both “Revenue Cloud Advanced” and “Agentforce Revenue Management” in its materials. This article uses Revenue Cloud Advanced throughout.
So there’s no cliff edge. There’s a slow drift instead, where each release adds something to Revenue Cloud Advanced that your CPQ won’t get. We looked at the timing question in more detail in CPQ End-of-Sale Is No Longer a Future Problem.
Should you migrate now or keep optimizing CPQ?
This is the decision most companies are actually facing, and for some of them the right answer is to wait. A well-run CPQ org that fits the business can keep doing its job for a while yet. The question is whether the effort you’d spend patching it would be better spent redesigning it.
| Keep optimizing your current CPQ when | Start planning a migration when |
| Quoting works and sales isn’t complaining | Reps work around the quote tool with spreadsheets or email |
| Your pricing model is stable | You’re adding subscriptions, usage pricing or new bundles |
| Customizations are few and well documented | Only one person (or one past consultant) understands the setup |
| No major ERP or billing change is planned | An ERP, billing or finance project is already on the roadmap |
| Your CPQ renewal is a few years out | A renewal or contract decision is coming up soon |
If you land in the left column, spend a little on cleanup now, such as retiring unused rules and documenting what’s left. That work isn’t wasted, because it makes a future migration cheaper too.
Why can’t you just upgrade CPQ?
Because the two products are built differently. CPQ runs as a managed package with its own objects. Revenue Cloud Advanced sits on Salesforce’s native data model, with a new pricing engine and a different way of defining products.
In practice, your price rules, product rules, bundles and any Apex written around CPQ objects get redesigned rather than copied across. That’s most of the work. It’s also where most of the payoff is, because plenty of CPQ setups still carry logic that made sense in 2018 and hasn’t been questioned since.
What does a CPQ to Revenue Cloud Advanced migration cost?
It helps to separate two costs that often get blended together. Licensing is what you pay Salesforce, and it depends on your edition, user count and contract, so your account executive is the right person to ask. Implementation is what it takes to design, build, migrate and test, and that’s the part this section is about.
Implementation effort comes down to five drivers. Most companies sit somewhere between the two columns below, and the more of your answers fall on the right, the bigger the project.
| Cost driver | Lower complexity | Higher complexity |
| Product catalog | A few hundred clearly defined products | Thousands of near-duplicate SKUs and complex bundles |
| Pricing rules and exceptions | Standard discounts and a short list of exceptions | Hundreds of special deals, regional rules and grandfathered pricing |
| Billing and ERP integration | Quotes handed to finance manually or through one simple connection | Quotes feeding Oracle, NetSuite or SAP for invoicing and revenue recognition |
| Active contracts | Mostly one-time sales, little renewal history | Many live subscriptions, amendments and co-terminated renewals |
| Custom code | Mostly standard configuration | Heavy Apex, custom quote templates and integrations built on CPQ objects |
A few early moves keep the right-hand column under control. Group products by family and attribute before configuration starts. Have sales and finance review the exception list together and decide what to retire. Scope the ERP connection during discovery rather than after the build, and agree how much contract history really needs to move.
The ERP piece is the one we see underestimated most. If everyone assumes quotes will simply flow into finance, a four-month project can easily turn into seven. It’s also why we design the quoting and billing sides together, drawing on our work with Oracle Fusion, NetSuite and integration platforms such as MuleSoft and Oracle Integration Cloud.
How long does the migration take?
Three to six months is a common range for mid-market companies with moderate complexity, counted from the end of discovery to go-live. Simple setups can move faster. Multi-entity businesses with heavy billing and ERP integration usually take longer. We plan the work in four stretches.
Discovery
Inventory every product, price rule, approval and integration in your current CPQ, then decide what stays, what gets simplified and what gets dropped. Of all four stages, this one saves the most money.
Build and integration
Configure the catalog, pricing and approvals in Revenue Cloud Advanced. Build the billing and ERP connection at the same time, not as an afterthought once quoting works.
Migration and testing
Move products, price books and active contracts. Then test renewals, amendments and cancellations as hard as you test new deals, because renewals are where production surprises tend to show up.
Go-live and phase two
Launch with a defined support window. Once the core is stable, plan the next round, such as guided selling or AI features.
How do you know it paid off?
A migration pays off when a business process gets better, not just because the software is newer. So start from the problems your teams feel today, and measure each one before you begin.
| Business problem | What to measure | What actually improves it |
| Slow quotes | Time from request to sent quote | A simpler catalog and guided configuration |
| Pricing errors | Share of quotes corrected after sending | Fewer, clearer pricing rules |
| Approval delays | Average approval cycle time | Approval paths redesigned around real risk thresholds |
| Broken order handoffs | Days from signature to order and invoice | A designed connection to billing and ERP |
| Maintenance effort | Admin hours per pricing or product change | Standard features replacing custom code |
If those numbers move, the business case makes itself. If you can’t name the problems in the left column, that’s a sign the migration may be able to wait.
Working with Selectiva on CPQ and Revenue Cloud
Selectiva is a Salesforce Crest Partner that implements Sales Cloud, Salesforce CPQ and Revenue Cloud Advanced. We also implement Oracle E-Business Suite, Oracle Fusion and NetSuite, so we design the quoting side and the billing side together. That handoff is where a lot of migrations go wrong. You can see the kind of quoting problem we work on in our case study on building a centralized quote estimator.
Not sure whether to migrate now or optimize first? Our CPQ Migration Readiness Assessment reviews your products, pricing rules, approvals, contracts and integrations, shows what’s driving your migration effort, and gives you a clear recommendation and a phased plan before you commit to anything. Ask us about the assessment.
Frequently asked questions
Is Salesforce CPQ being discontinued?
Salesforce CPQ is in end of sale, not end of life. Current customers keep support and can renew, but Salesforce no longer sells CPQ to new customers and is focusing new development on Revenue Cloud Advanced.
Do we have to migrate off CPQ right away?
There’s no published deadline. Many companies keep optimizing CPQ while it fits the business, then plan the move around a renewal, a pricing change or an ERP project, when they’d be redesigning quoting anyway.
How much does it cost to move from CPQ to Revenue Cloud Advanced?
Implementation cost depends mainly on catalog complexity, pricing exceptions, billing and ERP integration, live contracts and custom code. Licensing is a separate cost that depends on your Salesforce edition, users and contract. A short discovery phase is the most reliable way to estimate both.
How long does a Revenue Cloud Advanced implementation take?
Three to six months is a common range for mid-market companies with moderate complexity. Simple setups can be faster, and multi-entity businesses with heavy ERP integration usually take longer.
Can CPQ price rules be reused in Revenue Cloud Advanced?
They can’t be copied over directly, because Revenue Cloud Advanced uses a different data model and pricing engine. Rules are redesigned, and many companies retire a large share of them along the way.
Is Revenue Cloud Advanced the same as Agentforce Revenue Management?
Salesforce has used both names in its materials for its current revenue management platform. This article uses Revenue Cloud Advanced.
