Skip to content

Blog / Architecture and integration

Salesforce CPQ end of sale: your four options in 2026

Salesforce CPQ is end of sale, not end of life. What that means, and the four options: stay, move to Revenue Cloud Advanced, switch vendor, or build.

The short answer. Salesforce CPQ is end of sale, not end of life. End of sale means Salesforce no longer sells new Salesforce CPQ licenses to new customers. It does not mean CPQ is switched off. Salesforce’s own page says existing customers keep their licenses, can renew and add users, and continue to receive support and critical fixes, that there is no forced migration to Revenue Cloud, and that it has not announced an end-of-life date. What you lose by staying is new features, because Salesforce is putting its investment into Revenue Cloud Advanced. You have four options: stay, move to Revenue Cloud Advanced, switch to another CPQ vendor, or build your own CPQ app.

What end of sale means, and what it does not

Take a company with 40 sellers on Salesforce CPQ, three years of price rules, and a quarterly renewal. On the day end of sale applied, what changed for that company? Nothing in the product. Quotes still price, approvals still route, and the contract renews as usual.

Salesforce’s end-of-life page, dated July 10, 2026, defines the term plainly: “End of sale means Salesforce is no longer selling new Salesforce CPQ licenses to new customers.” The same page answers the question people search for. It says CPQ has not reached end of life, calls it “a stable, supported solution for existing customers,” and says “there is no forced migration from Salesforce CPQ to Revenue Cloud.”

Here is the short list of what is and is not true.

  • True: existing customers keep their licenses, can buy more users and renew.
  • True: support and critical fixes continue.
  • True: CPQ is in a maintenance phase and will not receive new features or innovations.
  • Not announced: any end-of-life date. Be careful with articles that name one. Salesforce has not published a date, so any year you see quoted is a guess.
  • Not required: moving right now.

So the useful question is not “when do we have to leave?” It is “what does staying cost us over the next three years, compared with each way out?” The rest of this post sets out the four ways.

Option 1: Stay on Salesforce CPQ for now

You keep what works, and you plan the exit on your own schedule.

Best for: teams whose CPQ setup is stable, whose pricing rarely changes, and who have no near-term plan to change how they sell. It also suits teams in the middle of a big Salesforce change, such as a new org or a billing project, where a CPQ move on top would add risk.

Trade-offs:

  • No new features. The product you have today is the product you will have.
  • The gap widens. Salesforce says new features and innovation go to Revenue Cloud, not CPQ.
  • Your CPQ setup stays as it is while the rest of your Salesforce org moves on, so changes get harder to fit around it.
  • Nothing forces the decision, so it is easy to drift. Set a review date, for example at your next renewal, and use the inventory below to keep the option of leaving cheap.

Option 2: Move to Revenue Cloud Advanced

Salesforce’s page names Revenue Cloud Advanced (RCA) as the successor to Salesforce CPQ, built API first and composable. Its Revenue Cloud product page, read November 14, 2026, describes one platform that unifies pricing, quoting, contracting, and billing on a single data model, with a configurable pricing engine, a Constraint Builder for product rules, and approval workflows started from an opportunity. Salesforce’s earlier name for this line was Revenue Lifecycle Management, so older partner material uses that term.

Salesforce says about 15% of RCA customers are companies that migrated from CPQ. That is Salesforce’s own figure, so read it as a sign that the path is used, not as a measure of how it went.

Best for: companies committed to Salesforce as the system of record for revenue, with complex pricing, bundling or amendments that they want to keep inside one vendor. If you also want Salesforce’s billing in the same data model, this is the option built for that.

Trade-offs:

  • It is a migration, not an upgrade. The data model differs from CPQ, so price rules, product rules and templates are rebuilt, not copied. Salesforce publishes an article on the differences, and partners sell migration tools. Plan for a project with an owner and a budget.
  • You are still renting. Licensing stays per user, so the bill grows with your sales headcount. Salesforce lists Revenue Cloud Growth at $150 and Advanced at $200 per user per month, billed annually, as a paid add-on to Sales Cloud. Get your own price in writing.
  • Integrations to your ERP and billing system need rework against the new objects.

Option 3: Switch to another CPQ vendor

Dedicated CPQ vendors sell the same job without the Salesforce data model. You pick a product, migrate the rules, and connect it to your CRM and ERP.

Best for: teams that want a finished product, a vendor responsible for it, and a faster rollout than a custom build. It is also the right call if you run more than one CRM, or you want pricing and deal-desk tooling that is not tied to a single suite.

Trade-offs:

  • You rebuild your rules in someone else’s configuration model, and you inherit its limits.
  • Check how each vendor prices, by seat, by package or by usage, and compare total cost over three years, not the first-year quote.
  • Another system needs a sync to your CRM and your ERP, and that integration is yours to keep working.

We compare the main vendors, with sources, in DealHub alternatives. To put numbers on the spend, see what CPQ costs to buy and to build.

Option 4: Build your own CPQ and run it on Tray Helix

This is the option most teams have not priced, because until recently building a quoting tool meant a year of engineering. An AI assistant changes the effort. A RevOps lead can describe the price book, the discount rules and the quote document, and have a working first version quickly, then connect it to Salesforce and the ERP. Tray Helix is where that app runs: it deploys the app to a managed runtime and runs it with sign-in, access control and a registry that names an owner, with SSO and an audit trail on Helix Enterprise Edition. There are no per-user fees, which matters most for a tool every seller uses. You can start on the Tray AI Orchestration Platform for $50 a month with Tray Helix Builder Edition, plus usage.

The Helix guide to how to build a CPQ tool sets out the four parts: a price book that is the only source of list prices, a quote builder, pricing rules with an approval path, and a quote document generated from the approved version. It includes the prompts to build each one. A companion guide covers the deal desk discount approval flow. The argument for doing this is in why to build your own CPQ.

Best for: companies with a clear pricing model that fits in a price book and a set of discount rules, a RevOps or deal-desk team that knows those rules, and someone willing to own the app. It suits teams that are tired of paying per seat for a tool whose real logic is a few dozen rules.

Trade-offs:

  • You own it. Someone has to keep the price book current, change rules and answer when a quote looks wrong. If no one can own it, do not build it.
  • It is not a fit for everything. Deep manufacturing configurators, very large catalogs with complex bundling rules, and products that need a visual configurator are better served by a dedicated product.
  • You build the integrations you need. Tray’s integration side connects the app to Salesforce, NetSuite and the rest, from quote to order to a CPQ to ERP sync. That is real work to set up, and it is the same work any option needs.
  • Check the real cost of running it. Helix’s honest cost-of-running argument covers what the line items are.

For a company of about 2,000 people, the Helix savings calculator models about 75% saved at that size across the apps you replace. It is a model, not a quote for CPQ, so run it with your own numbers.

How to decide

Answer these in order. The first “yes” usually points to your option.

  1. Is your CPQ working and your pricing stable? Stay for now, and set a review date.
  2. Do you need Salesforce to own pricing, quoting, contracting and billing in one data model? Look hard at Revenue Cloud Advanced.
  3. Is your product configuration deep, visual or tied to manufacturing rules? Look at a dedicated CPQ vendor.
  4. Can your pricing be written down as a price book plus discount rules, and is there a named owner? Price the build.
  5. Is the per-seat bill the main reason you are looking? Compare the three-year cost of options 2, 3 and 4 side by side.
  6. Do you have a quarter-end freeze or a big deal in flight? Do not start a migration inside it, whichever option you choose.

If two options tie, pick the one that is easiest to reverse. Staying is the easiest, and a build that runs beside CPQ for one product line is next.

What to inventory before any move

This list is the same for all four options, and doing it first often changes the answer. Many teams find that half their rules are dead.

  • Price rules. Every rule that changes a price, with the condition, the formula and the last time it fired.
  • Product rules. Bundles, options, dependencies and exclusions, and who maintains them.
  • Approval rules. Thresholds, approvers, escalation paths and what happens when an approver is away.
  • Quote templates. Every document sent to customers, by region and language, and who edits them.
  • Integrations to ERP and billing. What passes to NetSuite, SAP or your billing system, in which direction, how often, and what happens when it fails. A product that exists in CPQ but not in the ERP is a common cause of failed orders, as the post on quote to order explains.
  • Contracts and amendments in flight. Quotes, renewals and co-termed subscriptions that cannot be interrupted.
  • Reports that depend on CPQ fields. Finance and sales both have a few.

Allow for the order-to-cash side as well. The order-to-cash process is where a bad quote becomes a bad invoice, so test it end to end in whichever option you choose.

Sources

Read November 14, 2026.

  • Salesforce, Salesforce CPQ end-of-life page, dated July 10, 2026. Definition of end of sale, support commitments, no forced migration, no announced end-of-life date, Revenue Cloud Advanced as successor, and the 15% migration figure.
  • Salesforce, Revenue Cloud, undated page. Description of unified pricing, quoting, contracting and billing, the pricing engine, Constraint Builder and approvals.
  • Tray Helix, How to build a CPQ tool and What it costs to replace a SaaS app.
  • Tray Helix, SaaS savings calculator.
  • Partner migration tools named on Salesforce’s page: Forsys RevRamp, IdeaHelix and Prodly. We have not reviewed them.

Frequently asked questions

Is Salesforce CPQ end of life?

+

No. Salesforce CPQ is end of sale, not end of life. Salesforce's own page says it has not announced an end-of-life date, that existing customers keep support and critical fixes, and that there is no forced migration. What stopped is sales of new CPQ licenses to new customers, and new feature development.

What does Salesforce CPQ end of sale mean?

+

It means Salesforce no longer sells new Salesforce CPQ licenses to new customers. Existing customers can keep using CPQ, renew, add users and get support. CPQ is in a maintenance phase, so new features and innovation go to Revenue Cloud Advanced.

Do I have to move to Revenue Cloud Advanced?

+

No. Salesforce says there is no forced migration from Salesforce CPQ to Revenue Cloud and that existing customers do not need to move immediately. Moving is a choice you make when the cost of staying, mostly the missing new features, outweighs the cost of the migration.

What are the alternatives to Salesforce CPQ?

+

There are four realistic paths: stay on Salesforce CPQ for now, move to Revenue Cloud Advanced, switch to another CPQ vendor such as DealHub, or build your own CPQ app and run it on a platform like Tray Helix. Which fits depends on how complex your pricing is and who would own the tool.

What should I inventory before leaving Salesforce CPQ?

+

List your price rules, product rules, approval rules, quote templates, and every integration to your ERP and billing system. Add the quotes and contracts in flight. These decide how long any move takes, whichever option you pick.

Weighing a CPQ move? Price the build before you sign

Tray Helix runs the CPQ app your team builds with AI, with no per-user fees, and SSO and an audit trail on Helix Enterprise Edition. Tray connects it to Salesforce and your ERP.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.

Read the case for building your own CPQ