Salesforce CPQ is at end of sale. Now what?

The short answer: Salesforce CPQ reached end of sale in March 2025, which means Salesforce stopped selling it to new customers. It isn’t switched off. Salesforce says existing customers can keep using it, add users, renew and get support, and that it hasn’t announced an end-of-life date. New feature work goes to Revenue Cloud. Your choices are stay, move to Revenue Cloud, or move to something lighter.

The message arrives at 8:10 on a Tuesday. It’s a forwarded headline from your VP of sales, and the only text is a question mark. You know what it’s about. Your CPQ took two years to settle, it prices products that no catalog page describes properly, and the person who wrote half of its rules left in the spring.

Nothing is broken today. But “what’s the plan?” is a fair question, and “I’ll look into it” only works once.

What does end of sale mean for Salesforce CPQ?

It means you can’t buy new Salesforce CPQ licenses as a new customer, and Salesforce isn’t building new features for it. Salesforce’s own end-of-sale page calls it “end of sale, not end of life” and says it’s in a maintenance phase: supported, but no longer receiving new feature development.

That page is dated July 10, 2026. The text we could read doesn’t state the month, so March 2025 is the date as widely reported, not something we confirmed on Salesforce’s page. The substance matters more than the date, and it’s consistent across what we could read.

What does end of sale not mean?

It doesn’t mean your quotes stop working, your contract ends or you have to migrate. According to Salesforce’s page, existing customers can continue using CPQ, buy additional users, renew licenses and receive support. It states that CPQ “is not being switched off” and that “there is no forced migration from Salesforce CPQ to Revenue Cloud.”

You may come across blog posts that quote a shutdown date in 2027. Salesforce’s page says it has not announced an end-of-life date for CPQ. Where a blog and Salesforce disagree, go with Salesforce, and look at your own contract for the dates and terms that apply to you. That part is between you and your account team, and it’s not something this post can settle.

What end of sale does mean, in practice, is that the product’s future is smaller than its past. Salesforce’s Winter ’27 announcement puts its new quoting work (self-service quoting for buyers, quoting for partners, renewal quotes for account executives) into Revenue Management, not CPQ. If your plan depended on CPQ gaining a feature, that plan is now a workaround.

What is Revenue Cloud, and is it CPQ with a new name?

No. Salesforce calls Revenue Cloud Advanced the successor to CPQ, but it’s a different product on a different data model. Salesforce’s end-of-sale page says CPQ-specific objects, custom fields, pricing rules and scripts don’t map directly, so a migration is structured work rather than an upgrade.

The naming is also a moving target. Secondary sources describe the same line of products as Revenue Lifecycle Management, then Revenue Cloud, then Agentforce Revenue Management from late 2025, and then Revenue Cloud again from September 14, 2026, as reported by a CPQ vendor’s reference page. Salesforce’s Winter ’27 announcement uses “Agentforce Revenue Management”. Search Salesforce Help under both names, and check the current name before you put it in a slide.

Salesforce’s page also says a typical migration runs 3 to 6 months from discovery to go-live and that complex implementations take longer. Other sources put it higher. Treat all of those as inputs, and let your own inventory set the real number.

What are your options, and when does each one fit?

You have three, and “stay for now” is a legitimate answer.

Stay on CPQ. It fits if your pricing is stable and the setup works. The downside is quiet: no new features, and a growing gap between the product and what your reps will expect. Use the time to tidy, not to ignore it. Retiring dead price rules now makes every later option easier.

Move to Revenue Cloud. It fits if you have complex products, bundles and subscriptions, and a long Salesforce roadmap. Expect a redesign of your quoting logic rather than a lift and shift. As reported by a vendor reference page, Salesforce has announced a migration assistant for the CPQ managed package with a December 2026 target. We couldn’t confirm that from Salesforce, so ask your account team where it stands.

Move to something lighter. It fits if your catalog is simple and the bundle logic is mostly historical. Salesforce’s standard quotes, price books, approvals built in Flow, and a document generated from the record can cover a lot. A simpler setup is easier to run, and it’s also something you have to maintain yourself, so be honest about who will do that.

Two parts of quoting often don’t need a full CPQ. Purser generates quote and contract documents from a record, and Sistership clones a deal for renewal with rules. For the cloning side, here’s how to clone a record with its related records.

What should you inventory before deciding?

Write down what the system really does, with usage next to each item, before you pick a target. Most migrations go wrong because nobody recorded what the old one did.

Start with this list:

  1. Products and bundles, and which were quoted in the last 12 months.
  2. Price rules, product rules and discount schedules, and which ones still change a quote.
  3. Custom scripts and calculator plugins, who wrote them and whether anyone can read them.
  4. Quote templates and documents, including the one finance edits by hand.
  5. Approvals, with the real approvers.
  6. Amendments, renewals and contracted prices, because these are where simple replacements often fall short.
  7. Integrations to billing, ERP and anything that reads quote data.

Mark each item keep, simplify or retire. Retire is the easiest call to carry out, and it’s usually the biggest column.

What to do Monday:

1. Export your price rules and product rules, and note which have a real effect on a recent quote.

2. Count your quote templates and find the owner of each.

3. Ask two reps what they work around in CPQ today. Write the answers down verbatim.

4. Find your renewal date and put “CPQ decision” on the calendar three months before it.

Where we come in

The CPQ Exit Plan, by GTM Cloud, is a fixed-scope service of about three to six weeks. We inventory what your setup really does, design the target and write a migration plan you can hand to any builder. It isn’t the migration itself, it isn’t licensing advice, and sometimes the answer is to stay. If a plan is what you lack, see the CPQ Exit Plan.

Questions people ask

Is Salesforce CPQ end of life?

No. Salesforce’s page says CPQ is end of sale, not end of life, and that it hasn’t announced an end-of-life date. Existing customers can keep using it, renew and get support. Salesforce describes a maintenance phase without new feature development. Check Salesforce’s announcements and your contract for anything that applies to your agreement.

Do I have to move to Revenue Cloud?

No. Salesforce states there is no forced migration from CPQ to Revenue Cloud. It is the named successor, and new quoting work is landing there, so it’s worth deciding on purpose rather than at renewal. Staying, moving to Revenue Cloud, or moving to something lighter are all defensible, depending on how complex your pricing is.

How long does a CPQ migration take?

Salesforce’s page says a typical migration runs 3 to 6 months from discovery to go-live, and longer for complex setups. Other sources estimate more, and we haven’t seen a figure we can verify as general. How many custom rules and scripts you carry decides most of it, which is why the inventory comes first.

Sources