Is legacy Salesforce CPQ really "dead"? What "End of Sale" means for your revenue architecture

Is legacy Salesforce CPQ really "dead"? What "End of Sale" means for your revenue architecture

When a sales representative opens a quote and the calculation suddenly takes ten seconds longer than usual, it seems like a minor issue.
When an amendment gets stuck due to complex pricing logic, it becomes a serious issue.
And when every release requires additional regression testing, you realize that stability is under pressure.

In March 2025, legacy Salesforce CPQ—the managed package that many organizations have been using for years—officially reached its end of sale. That sounds drastic. However, it doesn’t mean your CPQ will stop working tomorrow.

It means something else: your architectural approach needs to be reevaluated.

This article explains what "End of Sale" actually means, where the risks arise over time, and how to manage them in a structured way.

What does "End of Sale" actually mean?

"End of Sale" means:

New customers can no longer purchase the legacy Salesforce CPQ.
Existing customers can continue to use their implementation.
Essential support remains available.
The strategic product focus is shifting.

So this isn't an End of Life. Your CPQ will continue to function.

What is changing is the direction of development. Innovation is slowing down. New platform capabilities are being integrated into more modern revenue solutions rather than into the older managed package.

That gap is growing without us even noticing.

Why Salesforce is taking this approach

Legacy Salesforce CPQ was built as a managed package on top of the Salesforce platform. That model worked well for years for complex pricing configurations and quoting processes.

But revenue processes have changed. Subscriptions, usage-based pricing, contract changes, and billing integrations have become more closely intertwined. Organizations don’t want a standalone quoting engine; they want a cohesive data model that spans the entire revenue lifecycle.

That is why Salesforce is now positioning Agentforce Revenue Management and Revenue Lifecycle Management (RLM) as the strategic path forward. Not as a standalone CPQ replacement, but as a broader architecture for quoting, contracting, fulfillment, billing, and renewal.

That’s not a judgment on your current implementation.
It’s a long-term platform choice.

Why remaining passive increases the risk

The biggest mistake is thinking that nothing will change.

At first, you won't notice much. Quotes will continue to be processed. Pricing rules will continue to run. Integrations will continue to sync.

Over time, you'll start to notice subtle signs:

• Quote calculations become more complex during peak periods.
  
• Pricing rules are increasing in number and becoming more interdependent.
  
• Flows and triggers are piling up.
  
• Every release requires more regression testing.
  
• Knowledge of the old model is becoming increasingly scarce.

This doesn’t happen suddenly, but gradually. Technical debt builds up without you immediately noticing it. The result: even small changes require more and more analysis and validation.

That takes time and computing power, every single time.

Why migration isn't a simple upgrade

Many executives think: we'll just upgrade to something new.

That's rarely how it works.

Modern revenue lifecycle management solutions use a different data model and different assumptions about how revenue flows through your organization. Quotation logic, approval processes, amendments, and renewals often need to be redesigned.

That's not a toggle.
That's a reimplementation.

If you act too soon, you run the risk that your processes aren’t fully mature yet. If you wait too long, the complexity will continue to grow. The right timing is determined by architectural health, not by market rumors.

How to Properly Analyze Your Current CPQ Risk

Before you talk about replacement, you need to take measurements.

A thorough Salesforce audit looks not only at configuration, but also at usage patterns:

• How quickly are quote calculations processed?
  
• How many pricing rules are currently active, and how interdependent are they?
  
• Which flows, triggers, or API integrations are triggered during a transaction?
  
• Where do delays occur in approval processes?
  
• How consistent is your data model across sales, finance, and billing?

This analysis reveals where complexity has built up.

At CaseNine, we always start with the diagnostic phase. Not to migrate immediately, but to identify where stabilization is needed. Without that step, every architectural decision remains based on assumptions.

And assumptions rarely help in the long run.

Stabilize before transforming

A common mistake is to jump right into a transition project.

In virtually every organization, stabilization is the first step:

• Remove unnecessary configuration.
  
• Simplify pricing logic.
  
• Clarify the approval process for trails.
  
• Improve data consistency.
  
• Streamline integrations.

That may seem less dramatic than a full-scale migration, but it reduces risk immediately. Plus, it makes your current system easier to understand. Once you understand how your business logic actually works, you’ll be better equipped to determine what’s future-proof.

Structure over speed.
Clarity over change.

What does this mean for RevOps?

RevOps is not an organizational trend, but an architectural discipline.

Without clear data ownership, lifecycle definitions, and governance, any revenue solution can quickly become overly complex. This applies just as much to legacy Salesforce CPQ as it does to Agent Force Revenue Management.

If automation continues to grow unchecked, reliability will decline.
When validations pile up, response times increase.
When integrations aren’t clearly defined, synchronization errors follow.

So RevOps isn't about tools, but about consistency in design and decision-making.

Practical guidelines for decision-making

Don't panic. "End of Sale" is just a notification, not an emergency.

First, assess how your current architecture behaves.
Separate stabilization from transformation.
Evaluate migration based on measurable risks.
View your revenue platform as infrastructure, not as a standalone application.

Following this order helps you avoid making impulsive decisions.

In summary

Legacy Salesforce CPQ isn't going away tomorrow.
But the strategic focus is shifting.

Those who remain passive will find complexity growing unnoticed.
Those who analyze and stabilize first maintain control.

Revenue architecture isn't about speed, but about long-term coherence and scalability.

Yannick van Eldik

Co-founder

Yannick van Eldik is a co-founder of CaseNine. Moreover, Yannick is closely involved in both sales and content projects. He helps organizations to optimally set up Salesforce solutions, but also acts as a discussion partner for strategic issues.