Salesforce CPQ in 2026: Stay, Optimize or Move to Revenue Cloud Advanced?
Salesforce CPQ went end of sale in March 2025. Existing customers are not forced off it, but the clock is running. Here is how to decide what to do next.
Salesforce CPQ is no longer sold to new customers. If you run it today, you have a decision to make, but probably not a migration to start tomorrow. The worst outcome is not staying or moving. It is moving in a panic and copying every mistake into a new platform.
By Waseem Ahmad, Sofyrus Technologies · Published September 30, 2026 · Updated November 6, 2026
Quick answer
Salesforce CPQ went end of sale in March 2025, but existing customers can keep using and renewing it. Stay and optimize if CPQ works and your revenue model is stable. Plan a phased migration to Revenue Cloud Advanced if you need subscriptions, usage-based pricing, better performance at scale or AI-assisted quoting. Either way, clean your catalog and rules now: it speeds quoting today and cuts migration cost later.
Key takeaways
- Revenue Cloud Advanced is built on standard platform objects, not the CPQ managed package, so moving is a re-implementation, not an upgrade.
- Partners report a wave of migration demand building through late 2026 and into 2027, which will make experienced implementation capacity scarcer.
- Clean the catalog and rules first. Every dead SKU and duplicate rule you remove is one you do not have to migrate.
- Pilot one product line end to end before migrating data in waves.
What actually changed
Three facts matter:
- End of sale, not end of life. Since March 2025, Salesforce CPQ is not sold to new customers. Existing customers can continue to use and renew it. New investment is going elsewhere.
- Revenue Cloud Advanced (RCA) is the successor. It evolved from what was called Revenue Lifecycle Management and is built natively on standard Salesforce objects rather than as a managed package.
- There is no upgrade button. Products, bundles, pricing, rules, templates, approvals and integrations are modeled differently. You redesign and migrate.
The practical consequence: the decision is strategic, not technical. It deserves a business case, not a reflex.
First principles: what is CPQ for?
Strip it back and a quoting system does three jobs:
- Configure: make sure what the rep sells can actually be built and delivered.
- Price: apply the right list prices, discounts and contract terms, consistently.
- Quote: produce a document the customer can sign, fast, and hand the order downstream cleanly.
If your current CPQ does those three jobs well enough and your business model is not changing, staying is a legitimate choice. If any of the three is broken, or your model is shifting to subscriptions or usage, the case for moving gets strong.
Option 1: Stay and optimize CPQ
Staying makes sense if CPQ works, your catalog is stable and no major new revenue models are coming. Use the time well:
- Clean the product catalog. Retire dead SKUs, unused bundles and obsolete price books. Smaller catalogs quote faster and migrate cheaper.
- Simplify price and product rules. Many orgs accumulate overlapping rules that slow quote calculation and contradict each other.
- Fix approvals. If reps wait days for discount sign-off, the problem is the approval matrix, not the platform.
- Fix quote templates so documents are accurate, branded and require no manual editing.
- Automate regression testing. CPQ breaks quietly when a rule changes. Automated tests for your top quote scenarios pay for themselves at every release.
Option 2: Migrate to Revenue Cloud Advanced
Plan a migration if any of these apply:
- You are adding subscriptions, usage-based pricing or complex billing that CPQ handles poorly.
- Quote performance is a real problem at your catalog size.
- You want the AI-assisted quoting Salesforce is building on the new platform.
- Your CPQ was heavily customized and is due for a redesign anyway.
How to plan it
- Assess. Inventory products, bundles, price rules, product rules, templates, approvals and integrations. Mark which are actually used. In most orgs a large share is not.
- Redesign, do not copy. RCA models products and pricing differently. Use the move to simplify, not to recreate every historical exception.
- Pilot one product line end to end, including configuration, pricing, approvals, quote document and order handoff to ERP.
- Migrate data in waves: active products and price books first, then open quotes, then installed base and assets.
- Run in parallel where needed, and cut over by product line or region rather than in one big bang.
- Stabilize before adding AI. Let teams settle on the new platform before layering AI-assisted quoting on top.
| Phase | What happens | Typical duration |
|---|---|---|
| Assessment | Inventory, usage analysis, business case | 3–6 weeks |
| Design | New product and pricing model | 4–8 weeks |
| Pilot | One product line live end to end | 8–12 weeks |
| Waves | Remaining product lines and data | Depends on catalog size |
Simple orgs can move in a few months. Complex manufacturers with large configurable catalogs often plan a phased program over 6 to 18 months.
Option 3: Look beyond Salesforce
Some companies use the moment to evaluate other CPQ platforms. That can make sense if Salesforce is not your system of record for revenue, or your quoting needs are unusual. For Salesforce-first sales teams, staying in the ecosystem usually keeps integration cost and change management lower.
The timing question
Waiting has a cost too. Partners report that migration demand is building through late 2026 and into 2027. As more companies move at once, experienced implementation capacity gets scarcer and more expensive. Starting the assessment now does not commit you to migrating. It gives you the facts to decide on your terms rather than under pressure.
Lessons from manufacturing CPQ projects
Configurable products like vehicles, equipment and their accessories stress CPQ more than most industries. From our CPQ implementation and e-commerce portal work for Club Car in the USA:
- Model configuration rules with the people who build the product, not only sales operations. Engineering knows which combinations actually work.
- Connect quoting to the dealer or customer portal, so configuration rules are identical online and in the sales team's quotes. Two rule sets will drift apart.
- Test every major configuration path before each release. Configuration bugs reach customers as wrong prices or unbuildable orders.
- Treat pricing data as a product. Someone must own price books, effective dates and regional variations.
Building the business case
Whether you stay or move, leadership will want numbers. A credible CPQ business case covers four things:
- Quote cycle time: how long from opportunity to sent quote today, and the target
- Pricing accuracy: discount leakage and quotes reworked because of errors
- Rep productivity: hours per week spent fighting the quoting tool
- Run cost: licenses, admin effort, release testing and custom code maintenance
Measure the current state honestly before proposing anything. A migration justified by vague promises of "modernization" is the first to be cut when budgets tighten. One justified by faster quotes and less discount leakage usually survives.
Change management is half the project
Sales reps do not care which platform they quote on. They care whether quoting is faster than last quarter. Involve a few respected reps in design and pilot testing, train by real scenarios rather than feature tours, and keep the old quote documents looking familiar where possible. Adoption problems kill more CPQ projects than technical ones.
Common mistakes
- Lifting and shifting every rule into the new platform, including the ones nobody uses.
- No usage analysis, so the scope is inflated from day one.
- Big-bang cutover across all product lines at once.
- Adding AI during the migration, which multiplies change for users.
- No regression tests, so every release is a risk.
Frequently asked questions
Is Salesforce CPQ being discontinued?
It went end of sale in March 2025. It is no longer sold to new customers, but existing customers can keep using and renewing it. New investment is going into Revenue Cloud Advanced.
Is moving from Salesforce CPQ to Revenue Cloud Advanced an upgrade?
No. Revenue Cloud Advanced is built on different, standard platform objects, so moving is a re-implementation: products, pricing rules, quote templates, approvals and integrations all need to be redesigned and migrated.
How long does a CPQ to Revenue Cloud Advanced migration take?
It depends on catalog and rule complexity. Simple orgs can move in a few months; complex manufacturers with large configurable catalogs often plan a phased program over 6 to 18 months.
Should we migrate now or wait?
Start the assessment now and decide based on your revenue model and CPQ health. Waiting until late 2026 or 2027 risks competing for scarce implementation capacity.
What should we do first, whether we stay or migrate?
Clean the catalog, simplify rules and approvals, and add regression tests. These improve quoting today and reduce migration cost later.
How Sofyrus helps
We implement, optimize and test Salesforce CPQ and quoting systems, and build the e-commerce portals around them. See our automotive and manufacturing software services, or ask about a dedicated Salesforce team through our managed IT services.
Not sure whether to stay or migrate? Book a CPQ health check and get a written stay-or-move recommendation.
Sources
