Salesforce CPQ Is Officially End-of-Sale

Salesforce CPQ Is End-of-Sale: What It Means and What to Do Next

The Situation

In December 2023, Salesforce announced that Salesforce CPQ would reach end-of-sale status effective March 2025. If you've been using CPQ, you've likely received communications about this shift. The reaction from the market has been mixed—some users view it as a natural evolution, others as an abrupt disruption. The reality sits somewhere between.

This page cuts through the uncertainty. We'll walk through what happened, why it happened, what your options are, and how to evaluate them without letting urgency drive bad decisions.

What Actually Happened

Salesforce's CPQ product isn't disappearing. Instead, Salesforce has consolidated its quote-to-cash strategy around Revenue Cloud Advanced, their newer platform built on modern architecture. Revenue Cloud Advanced includes CPQ functionality—quote generation, approval workflows, e-signature integration, and reporting—but packaged differently.

Existing CPQ licenses get extended support through March 2027 at no extra cost. That's not a short runway; it's about 24 months to plan and execute a migration if you choose to move.

Why the shift? Salesforce wants to centralize investment in a single platform rather than maintain parallel products. Revenue Cloud Advanced is more cloud-native and has different licensing. This isn't personal; it's standard consolidation in enterprise software.

The Timeline You Need to Know

Key Dates

Extended support means Salesforce will fix critical bugs and maintain platform compatibility through March 2027. After that, you're on your own—Salesforce won't patch vulnerabilities or ensure compatibility with new Salesforce platform updates.

What This Means for Your Organization

Your CPQ instance continues to work after March 2025. Nothing stops working on that date. The question is support and future-proofing.

If you stay on CPQ:

• You have a stable, known system through March 2027.
• Salesforce will fix critical bugs and maintain backward compatibility with platform updates until extended support ends.
• New features won't come. CPQ is in maintenance mode.
• After March 2027, you assume all risk. Salesforce won't guarantee compatibility if you upgrade Salesforce core or ecosystem tools.
• Eventually, you'll migrate. The only question is timing.

If you migrate to Revenue Cloud Advanced:

• You stay on Salesforce's modern path. RCA will receive feature investment.
• Quote workflows move to a new interface. Training required.
• Existing customizations may require rework. Salesforce offers migration tools; complexity depends on your setup.
• Pricing shifts from per-user to cloud-based. Budget impact varies.

If you switch to a third-party alternative:

• You evaluate a new vendor's roadmap, support quality, and ecosystem fit.
• You keep your Salesforce org and use the third-party tool for quote-to-cash workflows.
• Integration is key. How deeply does the tool connect to your data?
• Some alternatives include Kugamon, Conga, Model N, and others. Each has different strengths.

Your Three Paths Forward

Path 1: Stay on CPQ Until Extended Support Ends (March 2027)

This works if you're comfortable with a known deadline and your processes are stable. You have two years to evaluate options without pressure, to improve your CPQ processes, or to prepare for migration.

Risks: You'll eventually need to migrate anyway. Waiting until the last year creates urgency and limits options. Longer you stay, larger the potential gap between CPQ and whatever replaces it.

Best for: Organizations with stable quote workflows, low customization, or budget constraints now.

Path 2: Migrate to Revenue Cloud Advanced

Salesforce's native path. You stay within the Salesforce ecosystem, and the company invests in RCA's future.

Considerations: RCA is modern but different. If you've heavily customized CPQ, migration is non-trivial. Pricing is cloud-based, so budget impact must be calculated. Migration tooling from Salesforce exists but requires time and expertise.

Best for: Organizations already on modern Salesforce with straightforward CPQ setups, or those committed to Salesforce long-term.

Path 3: Switch to an Alternative (Kugamon, Conga, Model N, etc.)

You maintain your Salesforce org and use a specialized CPQ tool built for the Salesforce ecosystem. This approach often preserves your customizations and Salesforce data model.

Considerations: You're adding a vendor relationship. Integration must be solid. Evaluate support quality, roadmap alignment with your needs, and total cost of ownership against RCA and CPQ.

Best for: Organizations wanting to stay on Salesforce, keep existing customizations, or seeking a best-of-breed CPQ with stronger subscription management or configure-price-quote features.

Migration Options Comparison

What to Evaluate in a Replacement

If you're moving away from CPQ, here's what matters:

1. Quote Workflow Alignment

Does the tool match how you quote? Dynamic pricing, approval routing, e-signature, document generation, version control? Test with your actual workflows, not defaults.

2. Salesforce Integration Depth

How tightly does it connect to your Salesforce data? Can it read account hierarchies, sync pricing, auto-update records? Loose integration creates manual work.

3. Customization Without Code

CPQ lets you customize pricing rules, approval logic, and fields without heavy code. Does the replacement? How steep is the learning curve?

4. Subscription & Recurring Revenue

If you manage subscriptions, renewals, or usage-based billing, ensure the tool handles that. Many CPQ replacements don't. Kugamon and Model N do; RCA's subscription capabilities are newer.

5. Reporting & Analytics

You need visibility into quote-to-cash cycle time, win rates, approval bottlenecks, and revenue impact. Is the tool's reporting intuitive, or does everything require custom dashboards?

6. Contract Lifecycle Management

Quoting is one step. What about contract generation, amendment tracking, e-signature, and archival? Does the tool own that, or do you integrate Docusign or similar?

7. Vendor Stability & Roadmap

Is the vendor investing in the product? Check recent releases, user community activity, and leadership statements. A tool on life support isn't worth migrating to.

8. Migration Support

How much does the vendor help you move data, train users, and validate the new system? This is often underestimated and critical to success.

Feature Parity Checklist

How to Plan Your Migration

Phase 1: Assess (Months 1–2)

Audit your current CPQ setup. How many custom pricing rules, workflows, approval paths, and integrations do you have? What's working well, and what's been a headache? This informs what you need from a replacement.

Interview stakeholders: sales operations, finance, legal, IT. Each group has different priorities.

Phase 2: Evaluate (Months 2–3)

Run demos with your top 2–3 candidates. Use real quote scenarios, not defaults. Ask vendors about migration support, timeline, and training.

Calculate total cost of ownership: software, implementation, training, and post-go-live support.

Phase 3: Decide (Month 4)

Pick your path: RCA, a third-party alternative, or stay on CPQ longer. Document the rationale for stakeholder buy-in.

Phase 4: Plan (Months 4–6)

If migrating, work with the vendor to build a detailed migration plan. Data mapping, testing cycles, cutover strategy, rollback plan.

Designate a project lead. This matters.

Phase 5: Execute (Months 6–12)

Stand up the new system. Run parallel testing. Train users. Validate data integrity.

Plan for cutover during a low-volume period. Have a support plan post-go-live.

Frequently Asked Questions

Q: Can I run CPQ and my new system in parallel during migration?

Sometimes, but it's messy. Quote data gets out of sync quickly. Plan for a cutover date rather than a long overlap. Most teams switch systems and maintain read-only access to CPQ data for 30–90 days as a safety net.

Q: Will I lose historical quote data when I migrate?

No. Historical quote records stay in Salesforce or get archived. The new system starts fresh with ongoing quotes. Some teams export CPQ history as read-only records for audit purposes.

Q: What happens to my approvers and custom workflows?

These need to be rebuilt in the new system. It's not automatic. This is often the longest part of migration. Talk to the vendor about how they handle complex approval logic.

Q: Will Salesforce force us to upgrade to RCA if we stay on CPQ?

No. Salesforce won't auto-upgrade your org. You choose when and how to move. That said, staying on CPQ after extended support ends (March 2027) does add risk.

Q: Can we negotiate extended support beyond March 2027?

Unlikely. Salesforce's timeline is firm. If staying on CPQ longer is critical, you should plan migration now so you're not scrambling near the deadline.

Q: How much will migration cost?

Typically $50K–$300K depending on complexity, team size, and vendor. Budget for software, implementation labor, training, and contingency. Ask vendors for reference customers and real project costs, not templates.

Q: Should we build a custom solution instead of buying a CPQ tool?

Rarely. Custom quoting logic is harder to maintain than it looks. Approval workflows, pricing rules, and tax calculations create ongoing technical debt. Unless you have specific, unusual needs, a vendor solution is lower risk and faster to deploy.

Q: What if we merge with another company on a different CPQ system?

CPQ consolidation after M&A is painful. If that's in your future, factor it into your replacement decision. Some tools integrate multiple instances better than others.

Q: Can we test a new CPQ system in a sandbox first?

Yes. Most vendors allow a sandbox or trial environment. Use it to validate workflows, integrations, and data mapping before committing to production implementation.

What Kugamon Offers

Kugamon is a Salesforce-native CPQ and subscription management platform built for organizations managing complex quotes, subscriptions, and revenue recognition. We've served over 500 companies since 2009 and hold a 4.9-star rating on the Salesforce AppExchange.

If you're evaluating alternatives, here's what we do well:

• Subscription management is built in. Most CPQ tools treat subscriptions as an add-on; we've integrated it from the ground up.
• Revenue recognition is native. If you manage complex deals with deferred revenue, ASC 606 compliance, or usage-based billing, it's handled.
• Salesforce-native. Your data stays in Salesforce. You're not syncing between systems constantly.
• Configurable without code. Pricing rules, approval workflows, and quote logic can be configured using a UI, not Apex.
• Migration support. We've moved customers off CPQ, Conga, and custom systems. We know the pain points.

We're not the only option, and we don't pretend to be. If you need a Salesforce-native tool with strong subscription capabilities, we're worth a conversation.

Next Steps

Here's what to do this week:

• Audit your CPQ setup. How complex is it? What's working, and what's not?
• Talk to your team. Sales, finance, and legal need input. Don't decide in a vacuum.
• Review the timeline above. Plan your migration before March 2027 pressure hits.
• Run a demo or proof-of-concept with your top 1–2 candidates.
• Set a decision date. Don't let this drag on indefinitely.

Evaluating your options? Visit transition.kugamon.com for a side-by-side comparison of every CPQ migration path.