Salesforce CPQ Sunset: Status, Timeline, and What It Means

Salesforce CPQ has reached end of sale, not end of life. Since March 2025, Salesforce has no longer sold it to new customers, though existing customers can still renew, add users, and receive support.

Salesforce has not announced an end-of-life date. For teams tracking the Salesforce CPQ sunset, that distinction is important. The Salesforce CPQ end of sale is an end of sale phase, not a CPQ end of support. 

Salesforce has published no fixed life date for the product. The eventual transition is toward Salesforce Revenue Cloud (formerly Agentforce Revenue Management), but the timing for existing organizations remains flexible.

To simply say: 

• End of sale, not end of life: Salesforce stopped selling CPQ to new customers in March 2025
• No announced end-of-life date: Salesforce has not published an end-of-support or shutdown date.
• Existing customers remain supported: Customers can renew, add users, and continue receiving support and critical fixes, with no forced migration.
• New feature development has stopped: Net-new investment is now focused on Revenue Cloud.
• Revenue Cloud is the named replacement: Salesforce positions Revenue Cloud as the successor to CPQ.
• The 2029–2030 sunset is not official: That timeline is analyst speculation, not a Salesforce commitment.

For existing CPQ customers, this means current CPQ licenses, current contracts, and the ability to renew licenses or add users remain intact.

Salesforce CPQ remains a supported solution for existing customers even though new feature development and major product investment have moved elsewhere.‍

Is Salesforce CPQ end of life?

No. Salesforce CPQ is not end of life. It is end of sale, which is different.

"End of sale" means Salesforce no longer sells new CPQ licenses to new customers. "End of life" would mean Salesforce announces a date to stop supporting the product and eventually shuts it down. That has not happened, and Salesforce has not announced such a date.

If you already run Salesforce CPQ, it continues to work, your contract remains active, and support continues.

The confusion makes sense. "End of sale" and "end of life" sound similar, and much of the content that ranks for this question muddles the two in ways that create urgency. The primary source draws a clear distinction, so getting it right matters before you make any plans.

Existing customers can continue operating the CPQ managed package on the Salesforce platform, and ongoing support can include critical maintenance and bug fixes even though net-new CPQ features are no longer the focus.

What is the difference between end of sale and end of life?

End of sale means new customers can no longer buy the product; end of life means the product itself has been discontinued. Salesforce CPQ has reached the former, not the latter.

Understanding these Salesforce phases matters because an end-of-sale announcement changes product strategy without necessarily changing the day-to-day availability of the software for current users.

What "end of sale" means

As of March 2025, Salesforce no longer offered Salesforce CPQ to new customers or developed new features for the product. New investment shifted to Revenue Cloud. That change did not cut off customers already using CPQ. They kept their licenses and support, and could still add users or renew when their terms ended.

As Salesforce shifts investment toward Revenue Cloud, the original managed package remains available to organizations that already own it.

What has changed, however,  is feature development: new capabilities and major updates are directed toward the newer revenue lifecycle architecture rather than Salesforce CPQ.

What "end of life" means

End of life marks the point when a vendor stops supporting a product and prepares to retire it.
Typically, the vendor publishes a timeline that includes the final support date, the last date for fixes, and often a deadline by which customers must migrate.

Salesforce has published no such timeline for CPQ. There is no end-of-support date, shutdown date, or mandatory migration deadline.

Until Salesforce announces one, treating CPQ as though it has a fixed expiration means planning around a date that does not exist.

We hope that this distinction allows operations teams, sales leaders, and IT teams to base their planning on actual business requirements rather than an assumed deadline.

Is Salesforce CPQ being discontinued?

Not for current customers. Salesforce no longer sells CPQ to new customers or develops new features for it. Still, calling it "discontinued" goes too far if your organization already uses the product.

The practical takeaway is fairly simple. A new company cannot buy Salesforce CPQ today; instead, it is directed to Revenue Cloud. Existing CPQ customers remain on a supported, maintained product, and no deadline has been set for them.

There will not be a sudden shut-off notice. The roadmap has shifted, though: new capabilities are being developed in Revenue Cloud rather than CPQ. That gives you a reason to plan a move on your own schedule, not to scramble.

For organizations with an existing CRM estate built around Salesforce CRM, Sales Cloud, custom automation, and other Salesforce products, this is therefore more of a technology-roadmap decision than an immediate shutdown event.

Notably, teams can assess the tech stack, business needs, and migration complexity before deciding when an eventual transition makes sense.

What is the Salesforce CPQ timeline?

The only firm date is March 2025, when the end-of-sale process begins. Salesforce has not announced an end-of-life date. The 2029 to 2030 window you may have seen is analyst speculation, not a commitment from Salesforce.

That last point matters. The 2029 to 2030 figure appears so often that it can begin to seem official, but it is not. The number comes up in vendor blogs and analyst commentary, including sources that are trying to sell a replacement product; none of them speaks for Salesforce.

Salesforce has not committed to an end-of-life date. Existing contracts remain in force according to their terms, and if Salesforce establishes a timeline later, customers would expect to be notified well before any cutoff.

So the honest timeline is short:

• March 2025: Salesforce CPQ reaches end of sale. It is no longer available for purchase by new customers, and no additional features will be developed
• 2026 and beyond: Existing customers continue to receive full support, including renewals, added users, and critical fixes
• End of life: Salesforce has not announced it, and no date has been published

Plan around that reality-not a cliff that has not been scheduled.
For CPQ customers, this means the Salesforce CPQ sunset should be treated as a strategic planning milestone.

It gives teams time to evaluate alternative platforms, third party platforms, and Salesforce's own successor based on market changes, cost, architecture, and future business needs.

What replaces Salesforce CPQ?

Revenue Cloud is the named replacement. Salesforce is directing new customers there instead of CPQ, and that is where it is putting net-new revenue lifecycle innovation.

The terminology has shifted often enough to confuse just about anyone. Here's a quick guide to the terms you're likely to encounter:

• Salesforce CPQ: The managed-package quote-to-cash product, now end of sale. It was sometimes sold with CPQ+.
• Revenue Cloud: Salesforce's current API-first revenue lifecycle product line, formerly sold as Agentforce Revenue Management, and the successor intended for new development. Salesforce positions it as the replacement for CPQ.
• Revenue Lifecycle Management: The category term used to describe Revenue Cloud's work across quoting, contracting, billing, and revenue.

In that sense, Salesforce Revenue Cloud represent a broader move toward a modern revenue platform.

The scope extends beyond traditional CPQ into areas such as subscription management, contract management, revenue management, billing and revenue recognition, and revenue recognition across the wider customer lifecycle.

Newer architecture is also intended to support evolving revenue models, including usage based pricing, usage based billing, recurring subscriptions, and hybrid models.

Those capabilities matter to revenue operations teams managing increasingly varied pricing models and commercial structures.

Moving from Salesforce CPQ to Revenue Cloud means migrating data, not performing an in-place upgrade. Because the two systems are built differently, products, price rules, bundles, and quotes must be moved and reconfigured instead of simply switched on.

Revenue Cloud is the default path, though it is not the sole option. For some teams, the end-of-sale milestone is also a reason to assess third-party CPQ tools.

What fits best depends on your requirements, rather than the label on the box. See Revenue Cloud for a closer look at its successor, or compare CPQ and Revenue Cloud side by side.

For teams considering modern CPQ solutions, that assessment can include how well each option supports existing sales processes, helps sales teams generate quotes, manages complicated pricing logic, handles product catalogs, and allows reps to price deals efficiently.

The right CPQ solutions should also align with the organization's desired deal velocity, governance model, and broader commercial architecture.

A move to modern CPQ can also create opportunities for greater control, lower technical overhead, or lower costs, but those benefits depend on implementation quality and actual business requirements.

Note: The platform with the strongest feature list is not automatically the one that gives a company the greatest competitive edge.

For organizations staying heavily invested in Salesforce, seamless Salesforce integration and seamless integration with the existing Salesforce platform may also influence the decision.

Such considerations become particularly important where Salesforce CPQ is connected to Sales Cloud, existing CRM processes, downstream finance systems, and other complex integrations.

What should existing Salesforce CPQ customers do now?

Nothing urgent, and certainly nothing out of panic. Since no deadline requires immediate action, the sensible approach is to plan carefully instead of reacting to a date that has yet to be set.

Here's a sensible order of operations:

1. Start by confirming your contract and support terms. Check the renewal date and review what the agreement actually covers; that gives you a clear picture of where you stand instead of leaving you to guess from a blog post.
2. Then take stock of your CPQ configuration and data. Record the products, pricing rules, discount schedules, product bundles, quote templates, and the automations connected to them. Teams often underestimate how much logic is embedded in their CPQ org.
3. Choose a destination when the time is right. Assess Revenue Cloud-and, if it suits your situation, any third-party option-against your actual requirements.
4. Set the migration schedule yourself. With no imposed deadline, you can time the move around your business, release calendar, and tolerance for risk rather than rushing it.

The key point to absorb now is that the deadline isn't the hardest part. The migration is. That assessment should include more than visible CPQ configuration. Custom development, integrations, dependencies, and accumulated technical debt can have as much effect on migration effort as the number of products or quotes in the org.

Organizations should also identify integration issues and complex integrations early rather than discovering them during cutover.

The same applies to functional requirements. Different organizations use CPQ in different ways, so your business needs should drive the destination architecture rather than a generic replacement checklist.

Why migrating CPQ data safely is the real challenge

When you move away from CPQ, the calendar is not the main risk. The hard part is transferring CPQ data while preserving the links among products, pricing rules, and quotes; testing the new setup with realistic data without exposing customer information; and having a clean rollback plan if a release fails. This remains true whether you choose Revenue Cloud or a third-party CPQ.

CPQ data can break remarkably easily during transit. Products, price rules, product bundles, quotes, contracts, and orders depend on references to one another; when those links do not survive the move, quotes can be wrong in ways that are difficult to trace. That is how migrations fail quietly-not when the switch is flipped, but weeks afterward, when a pricing edge case returns an incorrect number.

Three things keep a CPQ migration honest, and they have nothing to do with the destination:

1. Preserve data relationships: Move the data without breaking dependencies or referential integrity. Flosum Data Migrator is designed to migrate CPQ data while keeping those relationships intact.
2. Test with production-like data: Use masked sandbox data that reflects real production volume and structure without exposing PII.
3. Plan for rollback: Treat cutover as a controlled deployment with release management and a clear rollback path if the release fails.

Flosum provides the safety layer beneath the migration rather than serving as a quoting or pricing product. It does not replace CPQ or Revenue Cloud. Instead, it helps prevent the move from breaking your data, regardless of which destination you select.

Not forgetting that this is also why insufficient testing is one of the biggest practical risks in a Salesforce CPQ migration. Pricing rules and embedded pricing logic can behave differently after reconfiguration, particularly where product catalogs, custom code, contract data, or external billing systems are involved.

A migration should therefore validate not only whether records moved but whether the new system supports the same commercial outcomes. That includes testing how sales teams generate quotes, how pricing models are applied, how contracts flow downstream, and how revenue operations processes behave after deployment.

Frequently asked questions

See how Flosum de-risks a CPQ data migration. Book a demo.