Salesforce CPQ End of Life: Your Migration Options
Salesforce CPQ is end-of-sale, not switched off, and the difference is the whole point. Salesforce has stopped selling CPQ to new customers and is steering new buyers toward its Revenue Cloud platform, but existing customers keep their product and their support, and Salesforce has not published a firm end-of-life date. This is a forced decision, not a forced destination: migrating to Revenue Cloud is one honest path, staying put for a defined runway is another, and rethinking your quoting stack entirely is a third. This guide lays out the options plainly, without the fear-selling the topic usually attracts.
I implement CPQ for a living, across Salesforce CPQ and its Apttus and Conga heritage, and I have no license to sell you, which is the only reason to trust a calm answer on a subject vendors like to make loud. Here is what is actually happening and what your real choices are.
What is actually happening to Salesforce CPQ?
In plain terms, Salesforce has moved Salesforce CPQ to end-of-sale and is directing new customers to its Revenue Cloud platform instead. End-of-sale means the product is no longer sold to new buyers; it does not mean the product you already run stops working, and it does not mean support has ended for existing customers. Salesforce itself draws that distinction deliberately, and it is worth holding onto, because most of the anxiety around this topic comes from collapsing end-of-sale into end-of-life when they are not the same thing.
What Salesforce has not done, at least as far as its published documentation commits to, is announce a firm date on which Salesforce CPQ reaches end-of-life. You will see specific years quoted around the industry; those are partner projections, not Salesforce commitments, and I am deliberately not repeating a date I cannot verify against Salesforce's own documentation. The responsible summary is this: the direction of travel is clear, the destination Salesforce is pointing at is Revenue Cloud, and the timeline is something to plan for sensibly rather than to panic about. Confirm the current status on Salesforce's documentation before you commit to any date, because this is precisely the kind of detail that changes.
Do you have to migrate right now?
No, and anyone telling you otherwise is selling urgency. Because CPQ is end-of-sale rather than end-of-support, existing customers have runway: the product keeps running and keeps being supported for now. What end-of-sale does change is the trajectory. A product that is no longer sold to new customers will, over time, receive less investment than the platform Salesforce is actively growing, so the honest framing is that you are on a path with a slope, not a cliff.
That means the right question is not "how fast can we get off CPQ" but "when does it make sense for us to move, and on what terms." For some teams the answer is soon, because they were going to rework their quoting anyway. For others it is later, because CPQ is doing its job and there is no value in rushing a complex migration ahead of need. Both are defensible. What is not defensible is being scared into a rushed program by a countdown that Salesforce itself has not actually set.
Your options, compared
There are four honest options, and the right one depends on where you want your quoting to live for the next several years, not on avoiding any particular vendor.
| Option | Effort | Risk | Best fit | One-line verdict |
|---|---|---|---|---|
| Stay on CPQ for a defined runway | Low | Rises gradually over time | You need breathing room, not a decision this quarter | Fine as a bridge, not as a forever plan |
| Migrate to Revenue Cloud | High | Manageable if planned properly | You are committed to Salesforce for the long term | The default path, and a good one, but not the only one |
| Move to another CPQ product | High | New-vendor learning curve | CPQ has been your bottleneck regardless | Worth it only if you were leaving anyway |
| Build custom quote logic | High | You own it end to end | Your quoting is unusual enough that no packaged CPQ ever fit | Right when the platform was always the wrong shape |
The table hides one honest truth worth saying out loud: for most existing Salesforce customers, Revenue Cloud is the sensible default, because staying inside the platform you already run preserves the most and fights the least. The other options are not worse; they are for teams whose situation genuinely points elsewhere. The mistake is treating the default as the only choice, or treating it as unthinkable.
What a Revenue Cloud migration actually involves
A Revenue Cloud migration is a platform move, not an upgrade, and the sooner a team internalizes that, the better it goes. The single biggest reason is the data model: Revenue Cloud represents products, pricing, quotes, and contracts differently from Salesforce CPQ, so the work is not lifting your configuration across intact but mapping your current objects and rules onto a new structure. Every pricing rule, product bundle, discount schedule, and approval flow has to be understood, decided on, and rebuilt or retired.
That is where the effort really lives, and it is mostly config-rebuild reality rather than data transfer. Your historical quotes and active contracts can be migrated with planning, but the deep work is the logic: reproducing the behavior your sales team depends on, in a system that expresses it differently, and using the move as a chance to shed the accumulated complexity you no longer need. Teams that treat migration as an opportunity to simplify come out with a cleaner system; teams that try to copy every historical quirk into the new platform pay for the migration twice. This is a category-level description on purpose, because the specifics depend entirely on how customized your CPQ has become.
When this is the moment to rethink CPQ entirely
A forced decision is an expensive thing to waste, and for some teams the honest answer is to use it. If your CPQ has been a source of friction, if your quoting is genuinely unusual, or if you have been quietly wondering whether the packaged approach ever fit, then the moment you have to touch the system anyway is the right moment to ask the bigger question rather than to default your way through it. Rethinking does not automatically mean leaving Salesforce; it means deciding deliberately where your quoting logic should live.
If you want to weigh the field properly, our CPQ software comparison looks across the options, what CPQ is covers the fundamentals if you are re-examining them, and CPQ implementation cost is honest about what any of these moves costs to do well. Our CPQ solution work and a Lightning-first CPQ we rebuilt for real adoption show how we approach it in practice. The point is not to talk you out of Revenue Cloud; it is to make sure that if you are going to spend a migration's worth of effort, you spend it on the destination you actually want.
How to plan it in one afternoon
You can get to a clear-headed plan quickly. Start by writing down where you want your quoting to live in three years, inside Salesforce or not, packaged or custom. Then inventory what you have: your pricing rules, product structures, approval flows, and the integrations that feed and consume quotes. That inventory is the single most useful artifact in this entire decision, because it tells you how big any move really is and where the complexity you can retire is hiding.
With those two things, a direction and an inventory, the choice usually becomes obvious: stay for a defined runway, migrate to Revenue Cloud, or make the deliberate case for something else. If you want that pressure-tested by people who have shipped CPQ across platforms and have nothing to sell you but the work, our Salesforce development team can help you scope it, and you can talk to us for a calm, honest read on your specific situation.
Salesforce, Salesforce CPQ, and Revenue Cloud are trademarks of Salesforce, Inc. This article is independent commentary for informational purposes; product names are used only to identify the products discussed.
