Since Salesforce put CPQ into end of sale, I’ve spent a lot of time inside CPQ orgs, some well built, most with years of patches layered on top of each other. And the same mistakes come up again and again when teams start planning their move to Revenue Cloud.
None of them are technical in the scary sense. They’re planning mistakes. That’s good news, because planning mistakes are cheap to avoid if you catch them early.
1. Copying CPQ into Revenue Cloud one-to-one
This is the big one. A team exports every price rule, product rule and bundle, then asks their partner to rebuild all of it in Revenue Cloud.
The problem is that most CPQ orgs carry years of logic nobody uses anymore. A discount rule for a promotion that ended in 2021. A bundle for a product line you stopped selling. A workaround someone built because a CPQ feature didn’t exist at the time.
Every one of those costs money to rebuild, test and maintain. Before anything moves, go through your rules and ask one question: when did this last actually fire? If nobody knows, that’s your answer.
2. Buying licenses before you know who actually quotes
Revenue Cloud costs more per user than CPQ. Yet I regularly see teams plan to buy the same number of seats they had on CPQ, without checking who actually uses it.
In a lot of orgs, CPQ licenses are handed out to managers, finance, ops and support “just in case.” A quick query on who created quotes in the last 12 months usually tells a very different story from the license count.
Do this check before your renewal conversation with Salesforce, not after. It’s the easiest money you’ll save in the whole project.
3. Treating it as a config project
CPQ migrations get scoped like admin work: rebuild the catalog, rebuild the pricing, done. Then the team finds the Apex triggers on SBQQ objects. Then the ERP integration that reads CPQ fields. Then the e-signature setup. Then the flows someone built on quote lines.
Revenue Cloud runs on standard objects, so anything that touches SBQQ objects breaks. Every trigger, flow, integration and report needs to be found and planned for.
My rule: before you estimate anything, get a full list of code and integrations that touch CPQ. If your partner gives you a quote without asking for that, be careful.
4. Planning a big-bang cutover
“We’ll switch everything over on one weekend” sounds efficient. In practice, it means your sales team can’t quote properly for weeks while issues get fixed in production.
The safer approach is phases: product catalog and pricing first, then quoting and documents, then contracts and renewals. And before the final cutover, run old and new side by side on real deals and compare the numbers. If a quote comes out different in Revenue Cloud, you want to find that in testing, not from a customer.
This is exactly how we approach a CPQ to Revenue Cloud migration at Tenetizer, because I’ve seen what happens when it’s done in one go.
5. Forgetting about contracts already in flight
This one catches teams late. Your CPQ org has active subscriptions, contracts mid-term and renewals coming up. Revenue Cloud handles subscriptions, amendments and renewals very differently from CPQ.
So what happens to a customer who signed a three-year deal in CPQ last year and wants to upgrade next month? If nobody has planned for that, you’ll be handling amendments manually in spreadsheets.
Map out how active contracts will move, how co-terming will work, and who handles the first renewal cycle after go-live. This part needs as much attention as the pricing rebuild.
The pattern behind all five
Every one of these comes down to the same thing: treating the migration as a copy job instead of a chance to rethink how you quote.
CPQ end of sale isn’t an emergency. Your org still works, and you have a few years before end of life. But that time is only useful if you spend it cleaning up, sizing things properly and planning in phases. Teams that do that end up with a simpler, cheaper setup than the one they started with.
Ayub Ansari is a Salesforce Technical Architect with 13+ years of experience and founder of Tenetizer, a certified Salesforce Consulting Partner that helps SaaS and B2B companies move from Salesforce CPQ to Revenue Cloud.