Salesforce CPQ End of Sale: What It Actually Means for You

Your CPQ isn't switching off. But the clock has started, and how you use the next few years matters.

By Ayub Ansari, Salesforce Technical Architect at Tenetizer

Since the announcement, we've had the same conversation with a lot of CPQ admins and RevOps leads. Some think they have to migrate this quarter. Others think they can ignore it for five years. Neither is right. Here's what end of sale really means, and how to decide when to move.

What "end of sale" means

End of sale is a sales decision, not a technical one. Salesforce has stopped selling CPQ (the product many people still call Steelbrick or SBQQ) to new customers. For you as an existing customer:

• Your org keeps working. Quotes, price rules, bundles and renewals run exactly as they do today.
• You can renew. Your CPQ licenses can be renewed under your existing contract.
• No new features. Salesforce's product investment has moved to Revenue Cloud. CPQ gets maintenance, not innovation.

One thing worth checking: if you're planning to grow your sales team, ask your Salesforce account executive how adding CPQ seats will work under your contract. Don't assume it'll be simple.

End of sale vs end of life

These two get mixed up constantly, and the difference is the whole story.

So you're not in an emergency. You're in the planning window. That window is the most valuable time you'll have, because it's the only period where you control the timing.

What you'll miss by staying on CPQ

Staying on CPQ is safe for now, but the gap will keep growing. The newer capabilities Salesforce is building, like AI-assisted quoting with Agentforce, usage-based pricing and tighter billing, are going into Revenue Cloud, not CPQ. The longer you stay, the further your quoting process drifts from where Salesforce is heading.

There's a quieter cost too. Admins and developers with deep CPQ knowledge will get harder to find as the market moves on, and partners who know CPQ well will get busier as end of life gets closer.

Why this isn't a simple upgrade

This is the part most teams don't realise until they start. Salesforce CPQ runs as a managed package with its own custom objects. Revenue Cloud is built on standard platform objects. There's no button that moves one to the other.

In practice, that means your pricing logic, bundles, product rules, quote templates and renewal setup all get rebuilt. Any Apex, flows or integrations that touch CPQ objects need rework too. It's closer to a reimplementation than an upgrade, which is exactly why rushing it is a bad idea.

Here's our honest take: don't think of this as a migration. Think of it as the one chance you'll get to delete half your pricing logic. Most CPQ orgs we audit have years of rules, bundles and workarounds that nobody remembers adding. Copying all of that into Revenue Cloud is the most expensive mistake you can make. Rebuilding only what your sales team actually uses is where the real savings are.

So when should you migrate?

There's no single right answer, but three things usually decide it.

1. Your Salesforce renewal date

Your renewal is your best moment to make a decision about licenses. Plan the migration so you know what you need before that conversation, not after you've signed another term.

2. How much you've customised

A fairly standard CPQ setup can move in a few months. If you have heavy price rules, custom code on SBQQ objects, complex bundles or multiple integrations, give yourself much more runway.

3. What's changing in your business

If you're launching new pricing models, adding usage-based billing or planning to use AI in your sales process, it makes little sense to build that on CPQ and then rebuild it later.

A good rule of thumb: if you're heavily customised or your renewal is within 12 to 18 months, start planning now. If your setup is simple and your renewal is far off, you have time, but use it to clean up rather than wait.

Check your own org in 10 minutes

You don't need a consultant to get a first sense of how big your migration is. Open the Developer Console (Query Editor tab) or Workbench as an admin, and run these queries. They're read-only, so they won't change anything.

SELECT COUNT() FROM UserPackageLicense
WHERE PackageLicense.NamespacePrefix = 'SBQQ'

SELECT COUNT_DISTINCT(CreatedById) FROM SBQQ__Quote__c
WHERE CreatedDate = LAST_N_DAYS:365

SELECT COUNT() FROM SBQQ__PriceRule__c WHERE SBQQ__Active__c = true

SELECT COUNT() FROM SBQQ__ProductRule__c WHERE SBQQ__Active__c = true

SELECT COUNT_DISTINCT(SBQQ__ConfiguredSKU__c) FROM SBQQ__ProductOption__c

SELECT COUNT() FROM SBQQ__DiscountSchedule__c

SELECT COUNT() FROM SBQQ__QuoteTemplate__c

SELECT Name FROM SBQQ__CustomScript__c

SELECT Name, TableEnumOrId FROM ApexTrigger
WHERE NamespacePrefix = null AND Status = 'Active'

What your numbers mean

This is a rough guide based on the CPQ orgs we've worked on, not a quote. Your integrations, data volume and renewal setup also matter.

What we found in a real CPQ audit

What to do this quarter

Even if you're not migrating soon, these steps cost little and make the eventual move much easier:

• Take inventory. Run the queries above and write down the numbers. Add your approvals and any integrations that touch CPQ.
• Clean up your catalog. Retire products and rules nobody uses. Everything you delete now is something you don't pay to rebuild.
• Check who actually quotes. Many orgs have CPQ licenses assigned to people who never build a quote. That matters when you size Revenue Cloud licenses.
• Stop building new complexity. Before adding a big new CPQ customisation, ask whether it's worth building twice.
• Get a clear estimate. Know roughly how big your migration is before you talk licenses with Salesforce.

Common questions