Salesforce CPQ End of Sale: The RevOps Migration Playbook
Salesforce CPQ (SteelBrick) is end of sale. Here is the complete RevOps migration playbook: how to evaluate alternatives, avoid lock-in mistakes, and execute a zero-downtime transition.
TLDR: Salesforce CPQ — the product formerly known as SteelBrick — has reached end of sale, meaning no new licenses are being sold and Salesforce is formally steering customers toward Agentforce Revenue Management (the successor product). Existing customers are not being forced off immediately, but the support runway is finite, partner implementation capacity is draining fast, and the migration wave is already creating a 6-to-12-month backlog at major SIs. If your org runs Salesforce CPQ today, the decision is not whether to migrate but when. This guide gives RevOps directors and IT procurement leads a practical decision framework: how to assess your current state, which platform pathways actually make sense, the three vendor-lock-in traps to avoid, and how to structure a migration that does not break your quote-to-cash pipeline mid-quarter.
Why This Migration Can’t Wait
If your org runs Salesforce CPQ today, you’re working against a shrinking clock. SI queues at Accenture, Deloitte, and Slalom are already 9-12 months out for enterprise projects, migration credits are time-boxed, and every quarter you delay is a quarter of leverage you’re giving back to Salesforce. The product team has been redeployed onto Agentforce Revenue Management, which means no new AI features, no new integration hooks, and no net-new pricing model support for CPQ+ going forward.
The end-of-sale announcement is not a distant warning — it’s the operating reality now. Salesforce isn’t selling new CPQ licenses. Support continues on a diminishing schedule, and the pool of certified CPQ administrators willing to maintain a sunset product shrinks every quarter.
The urgency is compounded by timing. According to Salesforce’s own partner ecosystem data, over 60% of existing CPQ customers are classified as mid-migration or migration-planned by the end of fiscal year 2027. That means organizations starting their evaluation today are booking project starts in Q1 2027 at the earliest for complex implementations.
The RevOps leaders who move first will get better SI talent, better negotiating leverage with Salesforce on licensing credits, and more runway to run parallel environments before hard cutover. The ones who wait will face forced migrations on compressed timelines with reduced vendor support.
This playbook covers the five phases every migration needs: audit, platform selection, contract negotiation, data migration architecture, and cutover governance.
Your Current State: The CPQ Audit Checklist
Before you can choose a migration path, you need an honest picture of what you have. Most organizations underestimate CPQ complexity because the visible surface — reps clicking “Generate Quote” — looks simple. The complexity lives in the rules engine underneath. Don’t let the clean UI fool you.
| Audit Dimension | What to Capture | Migration Complexity Signal |
|---|---|---|
| Product catalog size | SKU count, attribute count, bundles/components ratio | >500 SKUs or >30% bundles = high complexity |
| Pricing rule count | Price rules, product rules, lookup objects | >200 rules = extended migration timeline |
| Approval chain depth | Approval stages, conditional branches, user groups | >5 tiers or dynamic routing = custom build required |
| Custom Apex / LWC | Lines of custom code against CPQ objects | Any custom Apex = dedicated migration engineer needed |
| Quote document templates | Template count, template variations per segment | >10 templates = document rebuild project |
| Integrations | ERP, billing (Zuora, Stripe, NetSuite), CLM tools | Each integration = separate workstream |
| Quote volume (monthly) | Peak quotes/month, quote line count distribution | >10,000 lines/month = performance testing required |
| Revenue recognition rules | VSOE, SSP, multi-element arrangements | Any RevRec customization = finance sign-off required |
Run this audit before you issue a single RFP. The output will determine whether you are a 4-month migration or an 18-month program.
Earned insight: The most common surprise in a CPQ audit is the ratio of live price rules to documented price rules. In enterprise accounts I have reviewed, roughly 40% of active price rules have no corresponding business owner or documentation. Someone built them three implementation cycles ago, they still fire, and nobody can explain why. Those undocumented rules become migration blockers: you cannot migrate what you cannot understand. Schedule a minimum two-week discovery sprint before you commit to any migration vendor timeline.
The Four Migration Pathways
Once you have an audit baseline, there are four realistic paths. The right choice depends on your Salesforce product footprint, pricing model complexity, and tolerance for platform lock-in.
Pathway 1: Agentforce Revenue Management (Salesforce Native)
What it is: Salesforce’s own successor product. Formerly Revenue Cloud, now rebranded under the Agentforce umbrella. Built on a new data model (distinct from the CPQ+ managed package), with native AI quoting through Agentforce agents, attribute-based pricing, and tight Data Cloud integration.
Who it fits: Organizations that are all-in on Salesforce, have straightforward subscription or usage-based pricing, and want to minimize the number of vendors in their quote-to-cash stack.
What it costs: Agentforce Revenue Management licensing starts at approximately $150/user/month (Growth tier) and scales to $300+/user/month for enterprise feature sets. Expect implementation costs of $200K–$800K for complex migrations, plus 12–18 months of post-go-live stabilization for enterprise accounts.
Lock-in risk: Maximum. You’ll be running your revenue engine on a Salesforce-proprietary data model. Contract flexibility is entirely dependent on your negotiating position at renewal. For orgs with >$1M annual Salesforce spend, that negotiation typically goes well. For smaller accounts, the leverage asymmetry is significant.
What Works
Agentforce Revenue Management offers the tightest possible integration between quoting and your Salesforce CRM. Quote generation via Agentforce agents delivers a real throughput gain for high-volume, standardized deals: reps can describe deal parameters in natural language and get a compliant quote in under 30 seconds. The new attribute-based pricing engine also handles consumption and usage models far more natively than legacy CPQ+ did.
Where It Struggles
The migration from CPQ+ to ARM isn’t a one-click upgrade. The data models are fundamentally different. Products, pricing, and configuration data must be rebuilt, not migrated. Customers who assumed this was an “upgrade path” have been blindsided by the rebuild requirement. Salesforce has migration tooling, but independent assessments rate it as adequate for simple catalogs and insufficient for complex ones.
Agentforce Revenue Management Strengths:
- Native Salesforce platform — no integration maintenance overhead
- AI-native quoting via Agentforce agents (the clearest differentiator for high-volume orgs with complex product catalogs)
- Consumption-based billing models handled natively
- Single vendor for CRM + quoting + billing = simpler support
Agentforce Revenue Management Weaknesses:
- Full data model rebuild required (not a migration — a reimplementation)
- SI backlog means 9-12 month lead times for enterprise projects
- Licensing cost increase of 30-60% over legacy CPQ+ for most orgs
- Vendor lock-in is maximum — no neutral data portability layer
Pathway 2: DealHub
What it is: A Salesforce-integrated CPQ built as a managed package with its own configuration, pricing, and proposal layer. DealHub runs on Salesforce data but maintains its own product catalog and rules engine outside the core Salesforce data model.
Who it fits: Sales-led organizations with 50–500 SKUs, growing product complexity, and teams that value buyer experience (interactive proposals, DealRoom) as much as back-office compliance.
What it costs: $35–$60/user/month for CPQ (volume-discounted). Implementation typically $75K–$250K. Total three-year TCO is often 20–35% lower than Agentforce Revenue Management for mid-market accounts.
Lock-in risk: Moderate. DealHub stores configuration in its own data layer, but the underlying Salesforce CRM data remains portable. Switching from DealHub to another CPQ is painful but not catastrophic.
Pathway 3: Conga CPQ
What it is: The rebranded Apttus CPQ, now part of the Conga Revenue Lifecycle suite. Purpose-built for complex pricing — manufacturing BOMs, services bundling, attribute-driven configurations with hundreds of constraint rules.
Who it fits: Manufacturing, professional services, or telecom organizations whose product hierarchies involve hundreds of constraint rules, multi-tiered channel pricing, or high-SKU environments that have exhausted what DealHub or ARM can handle.
What it costs: Enterprise pricing is negotiated, typically $50–$90/user/month, with implementation costs that frequently exceed $500K for full deployments. High-complexity manufacturing accounts have reported $1M+ implementation spends.
Lock-in risk: Moderate to high. Conga’s data model is proprietary, but the company has improved data portability standards post-2023. Revenue is mature, but Conga has had acquisition and ownership turbulence — factor this into your business continuity assessment.
Pathway 4: Specialist CPQ (Subskribe, Maxio, or Custom)
What it is: A growing category of purpose-built usage-based or consumption billing platforms that include light CPQ capability. Subskribe is Salesforce-native and targets usage-first pricing models. Maxio (formerly SaaSOptics) is strong on financial operations and subscription analytics.
Who it fits: SaaS organizations whose primary complexity is consumption-based pricing, metered billing, and revenue recognition — not product configuration. If your “CPQ” problem is really a billing-and-metrics problem wearing a CPQ costume, this pathway unlocks significant simplification.
What it costs: Maxio starts around $500/month for smaller accounts; Subskribe is enterprise-priced from $40–$75/user/month. Implementation is typically much lighter — 8-16 weeks for mid-market.
Lock-in risk: Lower. Both platforms have modern APIs and export-friendly data models.
The Three Vendor Lock-In Traps to Avoid
Every CPQ migration creates some lock-in. That’s unavoidable. What is avoidable are the three specific contractual and architectural decisions that amplify lock-in to a business-risk level.
Trap 1: Embedding pricing logic in the CPQ’s proprietary rules engine without documentation.
Price rules and product rules built inside a CPQ’s native engine using its proprietary syntax aren’t portable. They exist only as configurations inside that vendor’s system. If you build 400 price rules over five years and never document the business logic behind them in a format-neutral way, you’ll have to recreate them from scratch on your next migration. The cost isn’t just engineering time — it’s the institutional knowledge of why each rule exists, which is often impossible to reconstruct.
The fix: Maintain a business-logic registry in your own systems (a simple spreadsheet or Confluence page works). For each rule: what business condition it addresses, who owns it, what the fallback behavior should be if the rule is removed. This adds maybe 20 minutes per rule at creation time and will save you 200+ hours per migration. Worth it.
Trap 2: Signing a multi-year CPQ contract before the AI roadmap is clear.
The CPQ market is moving fast enough that any 5-year bet is a real gamble. Vendors that are behind on agentic quoting today may close the gap in 12 months with an acquisition or a major release. Vendors that are ahead today may lose their advantage if they’re acquired and their roadmap deprioritized. Signing a 5-year CPQ contract in 2026 is risky because the product you commit to today will look substantially different by 2028.
The fix: Negotiate 3-year maximum terms with 18-month review clauses. Include specific language about platform continuity in the event of an acquisition. Require escrow for critical configuration data. Salesforce will push for 5-year commits tied to discount incentives — the discount is real, but so is the risk.
Warning: Salesforce’s standard migration credits for CPQ-to-ARM transitions are contingent on signing an Agentforce Revenue Management agreement of at least 3 years. These credits are often presented as a “migration assist” benefit, but they structurally lock you into ARM before you have completed your migration assessment. Accept the credits only after you have confirmed ARM is the right fit for your org.
Trap 3: Migrating quote templates at the last minute.
Quote document templates — the PDFs, branded proposals, and order forms your CPQ generates — are almost always underscoped in migration plans. Teams treat them as a formatting exercise. They’re not. Template logic often embeds pricing display rules, conditional legal language, and approval-state-dependent content that’s deeply coupled to the underlying CPQ’s data model.
The fix: Allocate a dedicated template migration workstream starting in Phase 1, not Phase 3. Run a template audit alongside your rules audit. Assume every template with conditional sections will require a full rebuild.
The Migration Architecture: Four Phases
A successful CPQ migration follows a specific sequence. Compressed timelines that try to skip phases are the primary cause of go-live failures. Don’t let budget pressure collapse Phase 3.
| Phase | Duration | Key Activities | Exit Criteria |
|---|---|---|---|
| Phase 1: Foundation | 6-10 weeks | Product catalog audit, pricing logic registry, integration mapping, SI selection | Signed SI contract, documented business logic, approved budget |
| Phase 2: Build | 12-24 weeks | Platform configuration, product data load, pricing rule build, approval chain setup | UAT-ready environment, >95% rule parity with production |
| Phase 3: Parallel Run | 4-8 weeks | Shadow quoting (both systems run simultaneously), output comparison, rep training | <2% quote variance between legacy and new system |
| Phase 4: Cutover | 2-4 weeks | Phased ramp by deal segment, legacy system archived, hypercare period | 100% of new quotes on new system, zero P1 incidents for 2 weeks |
The parallel run (Phase 3) is the phase most organizations want to skip to save budget. Don’t skip it. Running both systems simultaneously on real deals gives you empirical proof that your pricing is correct, your approval chains are routing properly, and your reps know the new system well enough to use it without IT holding their hand. A compressed parallel run of two weeks is better than none, but four weeks is the minimum for any account with more than 200 quotes per month.
Tip: Structure your phased cutover by deal segment, not by rep or territory. Start with new logo deals (lowest risk — no legacy quote history to reconcile), then expansion deals, then renewal deals (highest risk — reconciling amendment history against your new data model). This sequence gives your team confidence and your SI a controlled error surface.
Pricing Reality: What Migration Actually Costs
The headline license cost comparison understates what you’ll actually spend. Here’s the complete TCO picture for a mid-enterprise account (200 sales reps, $50M ARR, 1,500 quotes/month):
| Cost Category | CPQ+ (Stay) | Agentforce Revenue Management | DealHub | Conga CPQ |
|---|---|---|---|---|
| Annual license | ~$180K | ~$360K | ~$150K | ~$200K |
| Implementation (one-time) | N/A (sunk) | $400-800K | $100-250K | $250-500K |
| Admin/maintenance (annual) | $80K | $100K | $60K | $90K |
| Integration maintenance (annual) | $30K | $40K | $25K | $35K |
| Year 1 total | $290K | $1.2-1.5M | $335-460K | $575-825K |
| 3-year total | $870K | $1.9-2.5M | $735-960K | $1.15-1.5M |
The CPQ+ “stay” option is cheaper in the short term, but only if you assume zero incremental cost for a degrading product. In practice, staying on a sunset platform means increasing admin burden (harder to hire for a declining ecosystem), growing security risk (no new security patches for deprecated features), and eventual forced migration on a compressed timeline with fewer qualified SIs available.
The DealHub pathway offers the most favorable 3-year TCO for organizations that don’t have extreme pricing complexity. Agentforce Revenue Management is only cost-competitive if your account qualifies for significant Salesforce migration credits or if you’re consolidating multiple vendors under a unified Salesforce contract.
Who Should Migrate Now vs. Later
Migrate now (start evaluation in Q3 2026) if:
- You are on a CPQ+ version that is more than 2 years old with significant custom Apex
- Your product catalog has grown beyond what it was designed for at go-live
- Your Salesforce contract renewal is within 18 months (optimal leverage window)
- You are adding consumption-based or usage-based pricing models
- You have active integration with a billing platform that is also evolving (Zuora, Stripe)
Can wait (start evaluation in Q1-Q2 2027) if:
- You are on a recent CPQ+ version with minimal customization
- Your pricing model is stable and simple (subscription + one-time, <200 SKUs)
- Your Salesforce contract has more than 24 months remaining
- Your SI relationship is strong and they can support you through a planned transition
Don’t wait past Q4 2027 regardless of situation. Salesforce has indicated support commitments, but SI availability and Salesforce’s own implementation resources will be heavily allocated to the migration wave. Organizations that start late will face constrained talent markets and potentially less favorable Salesforce commercial terms.
Bottom Line
Salesforce CPQ’s end of sale isn’t a theoretical future event — it’s the operating reality of the market today. System integrators are booking out, migration credits are time-limited, and the organizations that move first will do so with better resources, better leverage, and more time.
The single biggest mistake RevOps leaders make in this situation is conflating “migration” with “upgrade.” Agentforce Revenue Management isn’t an upgrade to CPQ+. It’s a reimplementation on a new data model. That distinction changes the resource planning, the timeline, and the business risk profile entirely.
But the second-biggest mistake is treating platform selection as the first step. It’s not. The first step is the audit. Until you know exactly what your pricing logic looks like, how many customizations you’re running, and which integrations are live, you can’t make an accurate assessment of which platform will minimize your migration cost and future lock-in risk.
The audit comes first. Everything else follows from it.
This month: pull one engineer and one RevOps analyst for two weeks to run the audit checklist above. Count your price rules, identify every custom Apex object, and map every live integration. That output — your actual complexity baseline — is what you need before you talk to a single vendor or SI. Assign a business owner to your pricing logic registry before you issue a single RFP. Once you have that baseline, run your shortlist through a proof of concept using your actual top 10 most complex deal scenarios before signing anything.
Rating: Agentforce Revenue Management: 3.8/5 for orgs with significant Salesforce footprint and clean product catalogs. DealHub: 4.2/5 for mid-market Salesforce-native orgs that want faster deployment and lower TCO. Conga CPQ: 3.9/5 for manufacturing and services orgs with true configuration complexity.
Related Articles
- Salesforce CPQ vs DealHub vs Conga CPQ: Which Fits Your Revenue Model?
- AI-Powered Pricing Optimization in CPQ: What Actually Works
- Agentforce Coworker: Hands-On Look at Salesforce’s New AI Teammate
- Salesforce Connections 2026: Agentforce Marketing Rebrand Explained
- How to Calculate ROI for Enterprise AI Investments
Discussion