CPQ to Revenue Cloud: stay or move
You can stay. Salesforce stopped selling CPQ to new customers, and existing customers keep their licenses, renewals, support, and critical fixes. New features now go into Revenue Cloud, so the decision depends on when your quote process needs them.
You work directly with me, Kiryl Kazlovich, a Solution & Technical Architect who can write code. Based in Grünwald near Munich. More than 12 years on Salesforce, for companies directly and inside Salesforce partner teams.
How I help you decide
What Salesforce says
There is no forced migration and no end-of-life date for CPQ. Salesforce says so on its CPQ end-of-sale page of 10 Jul 2026, checked on 20 Nov 2026.
Your CPQ setup first
I go through your product catalog, price rules, quote templates, and the custom Apex and Flow around your quotes, and list what a move would have to rebuild.
Reasons to stay
Your price rules are stable, the catalog rarely changes, and your team knows CPQ. Then the budget is better spent cleaning up what you have.
Reasons to move
You need features that only Revenue Cloud gets now, or your quote and order logic sits in custom Apex that nobody wants to touch.
Rules your admins can change
In a Revenue Cloud migration I moved quote and order logic from custom Apex into Flow and OmniStudio, where admins can change the rules.
Data that does not map one to one
CPQ objects, custom fields, and price rules have no direct match in Revenue Cloud. I map them and check the numbers after the load.
Tell me about your project
Book a call, or send a few lines about your system and what should change.
A 30-minute call, in English or German.