Salesforce CPQ Is End-of-Sale: A Migration Checklist for Mid-Market RevOps Teams

Salesforce put CPQ into End of Sale on March 27, 2025. No new licenses. No new customers. Your renewals and seat adds still work, and support is still active. The part that isn't published anywhere is the one that matters most: Salesforce has not issued an official End-of-Support date. Partner commentary points to 2029 or later based on Salesforce's historical EoS-to-EoL cadence, but no authoritative timeline exists today.

If you are running mid-market RevOps on legacy CPQ, you're stuck between two bad moves. Rush a full rebuild onto Revenue Cloud Advanced while the product is still filling feature gaps, or stay put on a platform already showing signs of maintenance-mode neglect. There is a third path, and it's the one this checklist is built around: plan your migration in 2026, but do not cut over in 2026. Use the year for catalog hygiene, cohort design, sandbox parallel-run, and executive sponsorship. Aim for a 2027 cutover, ending when your longest active CPQ contract renews. That is the honest mid-market position.

What "End of Sale" Actually Means for You

End of Sale is not End of Life. If you have CPQ today, you keep it. You can renew your contract, add seats, and file support tickets. The product stays on the Winter '26 managed package and receives maintenance through the standard policy (versions more than two releases behind GA lose support, per Salesforce Help article 000380904). That policy has been in place since November 1, 2020 and hasn't changed.

What you lose is the forward roadmap. Salesforce is investing in Revenue Cloud Advanced, not legacy CPQ. The Spring '26 release (GA February 23, 2026) rebranded Revenue Cloud as the Agentforce Revenue Management Agent. That's not just marketing. Agentforce agents run on Salesforce's core-native object model (Quote, Order, Contract), which legacy CPQ sits outside of. If you stay on CPQ indefinitely, you are architecturally locked out of Agentforce. That is the piece most "wait and see" plans miss.

So the real question isn't "can we keep running CPQ?" It's "how long can we run CPQ before the opportunity cost of the Agentforce lockout, plus the risk of late-stage migration panic, outweighs the cost and disruption of migrating now?"

The working answer for most mid-market teams: 2026 is a planning year, 2027 is the cutover year, and your sunset date is whenever your longest active CPQ contract renews. That frames the rest of this checklist.

The 2026 Reality Check: Why Big-Bang Migration Breaks

Before the checklist, understand why the default "pick a cutover date and rebuild" approach is failing in practice.

CPQ runs as a managed package on custom objects. Revenue Cloud Advanced runs core-native on standard objects. Price Rules, Product Rules, Quote Calculator Plugins, and bundle hierarchies don't port. They get rebuilt as RCA Pricing Procedures (server-side pricing logic), Constraints (configuration rules), and Business Rules Engine definitions (the approval and validation layer). Public write-ups from CPQ Integrations, Bluvium, and Aquiva Labs describe early RCA projects running materially over plan on both timeline and budget, with third-party tools filling PDF template and quote-link gaps that RCA hasn't closed yet.

The vendor checklists don't tell you this, but practitioner analysis does: "migration will clean up our data" is wishful thinking. It doesn't. Bad SKU hygiene, duplicate products, and zombie Price Rules in CPQ carry straight into RCA and break renewals and amendments on first use. Much of the industry commentary on CPQ program history suggests a high proportion of implementations never reached full adoption in the first place. The same governance and data failures that stalled those projects will stall RCA projects too. The platform isn't the cause.

The approach that is actually working is parallel-run by cohort. New quotes start in RCA on day one. Legacy contracts stay on CPQ until natural renewal. You migrate one cohort at a time, tied to renewal cycles, over 18 to 24 months. This inverts the vendor-checklist assumption that migration needs a cutover date.

The Migration Checklist

Section 1: Catalog and Data Hygiene (Do This First)

This is the real migration blocker, not architecture. Do it before anyone writes a single line of RCA configuration.

• Inventory your active SKUs. Pull every product record where IsActive is true. Cross-reference against quotes written in the last 18 months. Every product with zero quote activity is a candidate for deprecation.
• Identify zombie Price Rules. Export all Price Rules. Tag the ones that haven't fired in 12 months. These are dead logic. They'll confuse your RCA pricing procedure design if you carry them forward.
• Audit duplicate and near-duplicate products. Mid-market catalogs tend to accumulate variants created for one-off deals. Consolidate these into attribute-based configurations before migration. RCA's attribute-based pricing works cleanly on clean catalogs and breaks on catalogs with duplicate intent.
• Map Quote Calculator Plugins. Document every custom QCP script, what it does, and which rules depend on it. RCA moves pricing logic server-side through the Business Rules Engine. QCPs won't port. They get redesigned, not translated.
• Flag your bundle hierarchies. RCA supports up to 5 nested bundle levels as of Spring '26. If your catalog has deeper nesting, you need to flatten it now.
• Reconcile your discount approval rules. List every approval threshold, regional exception, and escalation path. Discount leakage is the number one margin issue post-cutover if approval logic isn't re-authored with the same strictness.

If you skip this section, the rest of the checklist won't save you. The real reason so many Salesforce projects stall is the same reason CPQ migrations fail: disconnected data that nobody cleaned up before the new system went live.

Section 2: Platform Decision (Don't Default to RCA)

Revenue Cloud Advanced is the Salesforce-native path, but it isn't the only option, and for some mid-market profiles it isn't the right one.

• Price out RCA honestly. Public list pricing places Revenue Cloud Advanced materially above the legacy CPQ + Billing bundle on a per-user basis, with add-ons layered on top of Sales Cloud licenses you already pay for. Get current list pricing from your AE in writing, then run the three-year total cost against what you pay today before committing.
• Audit RCA feature parity against your current workflows. Specifically: PDF template generation, quote-link experiences, buyer acceptance tracking, complex ramp pricing, multi-currency edge cases. Any gaps mean third-party spend or custom build. Budget for both.
• Evaluate non-Salesforce alternatives seriously. DealHub, Conga, Apparound, and PandaDoc all integrate with Salesforce without requiring a full platform swap. For teams with simpler quote-to-cash patterns, an external CPQ on Sales Cloud can be a cleaner answer than RCA. The trade-off is integration depth. Weigh it honestly.
• Treat bridge-and-wrap approaches as a stall, not a strategy. Wrapping legacy CPQ with AI agents or microservices is a real pattern that buys time. The evidence base is mostly partner-marketed. Use only if timing forces it.
• Rule out building your own. For teams under 50 users with very simple catalogs, a lightweight in-house quoting tool on Salesforce core objects is technically viable. In practice, the maintenance cost outruns the savings inside 24 months. Skip it.

Section 3: Execution Plan (Parallel-Run by Cohort)

Once you've picked your destination platform, the execution pattern that works is cohort-based, not big-bang.

• Stand up RCA in a full sandbox. Not a scratch org. A sandbox with a representative product catalog subset (start with your top-revenue products and your most complex bundle, not a fixed percentage), realistic price book entries, and at least sales rep, sales ops, and approver personas configured.
• Define your cohort segmentation. Split your active customer base into migration cohorts by contract size band. Top-20 accounts in one cohort, mid-band in another, long-tail in a third. Size-banded cohorts let a mid-market RevOps team sequence migrations in meaningful groups without requiring quarter-by-quarter volume.
• Start all net-new quotes in RCA on day one. From the moment your sandbox is validated and production RCA is configured, no new quote goes into legacy CPQ. This is the forcing function that prevents a third year of parallel debt.
• Run renewals on legacy CPQ until cutover date. Don't migrate mid-contract. The risk of renewal and amendment logic breaking on partially-populated records is the number one cause of revenue leakage during these migrations.
• Build a reconciliation dashboard. During the parallel window, you will have quotes in two systems. You need a single pipeline view. This is often overlooked until month three, when forecasting breaks. Build it on day one.
• Let your longest active contract set the sunset date. The last CPQ contract on legacy is the one that determines when you turn the lights off. If your longest contract renews in Q2 2027, your CPQ sunset is Q2 2027, period.

Section 4: Governance and Sponsorship (The Part That Actually Decides Adoption)

The history of CPQ implementations is not kind. Industry commentary consistently flags full adoption as the exception rather than the rule. The factor that correlates most strongly with projects that do reach adoption isn't technical. It's executive sponsorship. Projects with an engaged, attending sponsor land. Projects without one drift.

• Name a single executive sponsor. This is a CRO, COO, or CFO level decision, not a "Salesforce admin's project." If you can't name the executive today, pause migration planning until you can.
• Establish a weekly steering cadence. Weekly during active cutover phases. Biweekly during catalog hygiene. Monthly during planning. Sponsor attendance is mandatory.
• Document decisions, not features. Your migration documentation should capture why you chose your bundle structure, approval thresholds, and pricing logic, not just what they are. Features can be rebuilt. Decisions can't be reconstructed.
• Budget explicitly for change management. Sales rep training, approver education, and process documentation. Budget 15–20% of implementation cost for this. Teams that skip it reach go-live technically and fail to reach adoption for 18 months.
• Define what "done" means before you start. Percentage of quotes in RCA, average quote cycle time, discount-leakage rate below a specific threshold. Without success criteria, the project never ends.

What To Do This Quarter

Three things, in order:

1. Pull your product, Price Rule, and quote activity data. Run the catalog hygiene audit from Section 1. This is work you'd need to do for any migration target and it's pure value regardless of which platform you land on.
2. Build a decision paper comparing RCA, one external CPQ alternative, and a bridge approach. Include three-year TCO, feature-gap list, and timeline estimates. Present it to your executive sponsor.
3. Stand up a Revenue Cloud Advanced sandbox with a small, representative catalog subset. Your top-selling product, one complex bundle, and one discount scenario is enough to start. Don't commit to the platform. Do commit to learning it hands-on before you decide.

Start with catalog hygiene. Decide on your destination by end of Q3. Build your cohort plan in Q4. That is a 2026 that sets up a successful 2027 cutover, and it is what "plan, don't cut over" looks like in practice.

If you want a second opinion on your specific catalog complexity, cohort design, or platform decision, book a systems audit. No pitch, no urgency. Just a clear read on where you are and what your migration actually looks like from here.

Related articles

Salesforce Spring '26: Einstein Conversation Insights Goes Native - What Changes for Your Sales Reporting

Spring '26 moves Einstein Conversation Insights to standard Salesforce objects. Here's what changes for your reporting, automation, and competitive intelligence.

Read Article →

SimplePerm vs. Manual Migration: Why Free Tools Beat Spreadsheets

We have seen teams spend three months on what should take an afternoon. Here is an honest comparison of the paths available for Salesforce permission set migration.

Read Article →