Salesforce CPQ End of Life Migration Guide 2026: Four Paths, One Deadline
Salesforce CPQ's renewal window closes August 2026. Here's an honest breakdown of your four migration paths — ARM, DealHub, Conga, ERP-native — and what to do this month.
TLDR: Salesforce CPQ’s renewal window closes in August 2026. If your contract is up, you no longer have a renewal pathway — you’re in migration-decision mode whether you’re ready or not. The four realistic paths are Agentforce Revenue Management (Salesforce’s own successor), DealHub CPQ, Conga CPQ, and ERP-native (SAP BRIM / Oracle Fusion). ARM is the right long-term destination if you’re Salesforce-committed, but it’s a full reimplementation — not an upgrade — and SI queues are already 9-12 months out. DealHub gets you off CPQ fastest (3-6 months) for subscription-heavy orgs that don’t need deep configure logic. Conga fits if you need CPQ-level rule complexity. ERP-native only makes sense inside a broader ERP overhaul. Don’t panic-buy. But start the audit this week.
Why August 2026 Changes Your Options
Salesforce CPQ has been in end-of-sale mode since March 2025. No new licenses since then. But the August 2026 renewal deadline is a different kind of wall.
When your renewal rights close, your CPQ doesn’t stop working. Salesforce continues maintenance-level support through approximately 2029-2030. The issue is what you lose: negotiating leverage, SI availability, and the ability to start a controlled migration on your timeline. Every quarter that passes after August, the certified CPQ admin pool shrinks (no one is training for a product in sunset), SI queues for ARM implementations extend further, and your org’s CPQ configuration accrues more technical debt on a data model Salesforce is no longer investing in.
The admins asking “do we move to Revenue Management or go third-party?” on r/salesforce right now are getting answers shaped by SI interests. This guide gives you the independent decision framework.
Warning: SI queues for Agentforce Revenue Management implementations are already 9-12 months out at major Salesforce partners (Accenture, Slalom, Deloitte). If ARM is your path, every month you delay on the evaluation is a month added to your go-live date — and a month closer to running unsupported on legacy CPQ schema.
Four Migration Paths at a Glance
| Path | Best For | Timeline | Native Salesforce | Complexity |
|---|---|---|---|---|
| Agentforce Revenue Management | Salesforce-committed orgs, long-term | 6-18 months | ✅ Built-in | Very high |
| DealHub CPQ | Mid-market, subscription model | 3-6 months | ✅ Native connector | Medium |
| Conga CPQ (Revenue Cloud) | Complex CPQ config, enterprise scale | 9-18 months | ✅ Strong integration | High |
| ERP-Native (SAP / Oracle) | Orgs in a broader ERP overhaul | 12-36 months | ❌ No | Very high |
Path A: Agentforce Revenue Management
Salesforce rebranded Revenue Cloud Advanced as Agentforce Revenue Management at Dreamforce 2025. The name signals the strategic positioning: this isn’t just a CPQ replacement, it’s a unified quote-to-cash-to-service-contract platform built natively on Salesforce core objects, with autonomous agents handling quoting, approval routing, billing, and renewals.
What You Actually Get
ARM runs on Salesforce’s core data model. Your CRM data, opportunity records, and contracts live in one place — no sync layers, no API bridges. The agent layer is the new piece: quoting agents can configure products, route discount approvals, and trigger renewal workflows without rep intervention. That’s production-ready today, not a roadmap promise.
For regulated industries: Agentforce 360 received clearance for sensitive DoD data in the Summer ‘26 release. If you’re federal-adjacent or in a highly regulated vertical, that matters.
What Nobody’s Saying Out Loud
But ARM is not an upgrade path. Your CPQ configuration — pricing rules, product bundles, approval chains, custom Apex code, quote document templates — does not migrate. You rebuild from scratch on a different data model with a different admin paradigm.
Complex CPQ orgs typically spend 6 to 18 months on an ARM implementation with a certified SI. If you have more than 200 pricing rules or any significant custom Apex on CPQ objects, plan for the upper end of that range. The audit alone — before a single line of ARM configuration — takes 6 to 8 weeks for large orgs.
Earned insight: In CPQ implementations with 500+ SKUs and layered discount waterfalls, the rule-of-thumb “3x your CPQ rule count and assume that’s your ARM config effort” holds consistently in practice. An org with 300 active pricing rules should budget for 900+ ARM configuration tasks. SI proposals that quote 60 days of discovery for an org this size are underestimating — push back and ask for the discovery scope in writing.
ARM Strengths:
- Unified Salesforce data model — no sync layers or API bridges
- AI-native quoting, renewal, and billing agents in production
- Native billing and contracting in one platform
- Salesforce’s own product investment is here — best long-term support posture
- DoD clearance for regulated-industry orgs
ARM Weaknesses:
- Not an upgrade — full greenfield reimplementation required
- 6-18 month timeline; SI queues already backed up 9-12 months
- High implementation cost (licensing + SI fees that often exceed $500K for enterprise orgs)
- Migration credits must be negotiated before the renewal window closes — not guaranteed after
- Steep learning curve for admins trained on CPQ’s Visualforce-era admin interface
Path B: DealHub CPQ
DealHub built a native Salesforce connector and a configuration model that’s intentionally simpler than Salesforce CPQ’s rules engine. For orgs that need to be off CPQ in 3-6 months without a 12-month SI engagement, DealHub is the most viable option available right now.
Where DealHub Wins
It’s the right tool for subscription and SaaS-model businesses. If your quoting workflow is primarily: configure a recurring product bundle, apply standard discount tiers, get approval, generate a proposal — DealHub handles that faster and with less admin overhead than CPQ ever did.
The DealRoom (DealHub’s interactive buyer-facing proposal layer) is a genuine differentiator. Buyers get a live, collaborative pricing view instead of a static PDF, which matters when your sales cycle involves back-and-forth negotiation. It’s a capability CPQ never had.
Implementation timelines of 3-6 months are realistic for orgs under 300 SKUs without custom Apex. You’re not signing up for a 12-month SI engagement with six-figure discovery fees.
Where DealHub Doesn’t Belong
The problem is complex configure-price-quote logic. If your products require nested bundles with attribute dependencies — hardware plus software plus professional services with conditional pricing at each layer — DealHub’s simplified configuration model will hit its ceiling. CPQ’s rules engine exists because that complexity is real. Don’t assume DealHub handles everything CPQ did.
Tip: Before committing to a DealHub demo, send your top 10 most complex product configurations to their sales team and ask specifically which require custom development versus out-of-the-box configuration. The answer tells you more than any scripted demo will.
DealHub Strengths:
- Fastest path off CPQ — 3-6 months for standard orgs
- Strong Salesforce CRM native connector
- DealRoom for interactive, collaborative buyer proposals
- Lower admin overhead than CPQ’s rules-heavy configuration
- Strong fit for subscription and usage-based revenue models
DealHub Weaknesses:
- Not built for deeply complex CPQ configuration (nested bundles, multi-tier pricing waterfalls)
- No native billing layer — you still need Zuora, Stripe, or similar
- Pricing comparable to CPQ licensing; no Salesforce discount pathway
- Smaller certified SI ecosystem than ARM or Conga
Path C: Conga CPQ
Conga (the company formerly known as Apttus) has been doing enterprise configure-price-quote for over a decade. If your CPQ implementation is genuinely complex — multi-hundred-rule engines, intricate discount waterfall logic, CLM integration, and deep approval chains — Conga is the competitor you need to evaluate seriously.
Where Conga’s Depth Matters
Conga’s configuration depth is its primary advantage. Where DealHub simplified the model and ARM rebuilt it from scratch, Conga preserved and extended CPQ’s rule-engine approach. If your team has deep CPQ expertise and doesn’t want to retrain entirely, Conga maps more cleanly to that institutional knowledge than ARM’s new object model does.
Conga Revenue Cloud also bundles CLM (contract lifecycle management), billing, and CPQ into one platform. If you’re currently running Salesforce CPQ plus Docusign CLM plus Zuora billing as three separate integrations, Conga can consolidate that stack.
The Part That Makes This Hard
Conga implementations are slow and expensive. Plan for SI involvement throughout, and 9-18 months for complex orgs. Implementation quality also varies more by Conga partner than by ARM partner — Salesforce’s own resources can backstop a weaker ARM SI, but there’s no equivalent backstop for Conga. Vet your implementation partner before signing anything.
Conga Strengths:
- Configure-price-quote depth that matches CPQ’s complexity ceiling
- CLM + billing bundled (reduces multi-vendor integration overhead)
- Long enterprise reference list across industries
- Structured partner referral program with certified SIs
Conga Weaknesses:
- 9-18 month timelines for complex orgs — not a fast exit
- Implementation quality varies significantly by SI partner
- Heavier licensing costs than DealHub
- Less Salesforce-native than ARM; integration surface area creates ongoing maintenance
Path D: ERP-Native (SAP BRIM / Oracle Fusion)
If your leadership is already running a broader ERP modernization — upgrading to S/4HANA, consolidating Oracle Fusion, rationalizing your enterprise systems stack — CPQ migration can fold into that program as one workstream.
But don’t pick ERP-native as a standalone CPQ migration strategy. SAP BRIM or Oracle Fusion CPQ running alongside Salesforce CRM as your system of record means you’re permanently maintaining an integration between your CRM and your CPQ. Every opportunity-to-quote flow requires a data bridge. That’s manageable, but it’s indefinite maintenance overhead that ARM, DealHub, and Conga all avoid.
The timeline is also real: 12 to 36 months, significant ERP-side costs, and a complete redesign of your quote-to-cash architecture.
Warning: Some SIs are positioning SAP BRIM as a Salesforce CPQ migration path because the deals are larger. If you’re not already in an ERP overhaul program, this path adds 12-24 months of risk and complexity that has nothing to do with CPQ. Push back and ask your SI to justify the architecture in writing.
Pricing Reality
These are directional market figures as of August 2026. Final numbers require direct vendor quotes — and for ARM specifically, the licensing structure is currently tied to your Salesforce account team negotiation.
| Path | Licensing (annual) | Implementation Fees | Timeline |
|---|---|---|---|
| Agentforce Revenue Management | ~$150-$350/user/year | $300K-$1.5M+ SI fees | 6-18 months |
| DealHub CPQ | ~$100-$200/user/year | $50K-$250K SI fees | 3-6 months |
| Conga CPQ | ~$120-$250/user/year | $200K-$1M+ SI fees | 9-18 months |
| ERP-Native | Bundled with SAP/Oracle contract | $500K-$3M+ | 12-36 months |
The licensing delta across the top three options is relatively small. SI fees are where the real cost difference lives — and where you have the most negotiating leverage if you’re talking to multiple vendors simultaneously.
Tip: If ARM is your likely destination, negotiate migration credits with Salesforce as part of your current renewal conversation now, before the August window fully closes. These credits exist — Salesforce offers them in competitive situations — but the leverage disappears once you’re fully post-renewal and they know you’re captive.
A Five-Question Decision Framework
Answer these before requesting any demos:
1. Are you 80%+ committed to Salesforce long-term? If yes, ARM is the natural destination even at a longer timeline. If you’re also evaluating a CRM migration, ARM loses its core advantage (unified data model) and you should evaluate third-party options more seriously.
2. How complex is your current CPQ configuration? Pull your rule count, custom Apex line count, quote template count, and integration inventory. Under 200 rules with no custom Apex — DealHub is viable. Over 500 rules with heavy custom code — you’re in ARM or Conga territory.
3. Do you need billing, or just quoting? DealHub handles quoting but not billing. If your migration needs to include a billing transition, ARM and Conga both have native billing layers and reduce your integration surface.
4. What’s your realistic deadline? If you need to be off CPQ in under a year, DealHub is the only realistic path for most orgs. ARM and Conga implementations for complex cases simply can’t be compressed below 9-12 months.
5. Do you have an established SI relationship? If you have a certified Salesforce-partner SI that does ARM implementations, your risk is materially lower. If you’re starting fresh, evaluate DealHub and Conga partners alongside the platform — the SI relationship often matters as much as the platform choice.
What to Do This Month
Don’t let urgency create panic decisions. But you need to start moving:
- Audit your CPQ usage now — product catalog size, rule count, custom Apex lines, quote template count, integration inventory. This audit determines which paths are even viable for your org’s complexity level. Block 4-6 hours for this before requesting any demos.
- Export your price books, product catalog, and discount schedules — regardless of which path you choose, you’ll need this data in clean form. Do it while CPQ is fully operational and you have full admin access.
- Get an ARM scoping call from a Salesforce partner — these are free, and the scoping output will tell you concretely whether ARM is a 6-month or 18-month project for your complexity level. This is intelligence, not a commitment.
- Request DealHub and Conga demos — lead with your hard cases — show them your top 10 most complex product configurations. Their response to edge cases tells you more than any standard demo.
- Don’t sign a contract until Q4 at the earliest — you need 8-12 weeks of evaluation before a vendor decision is defensible to your leadership. Urgency is real, but the worst outcome is a rushed decision that locks you into a 12-month implementation you didn’t fully scope.
Bottom Line
The August 2026 deadline is forcing a decision that most Salesforce CPQ orgs have been deferring for 18 months. The four paths are real, the tradeoffs are significant, and choosing wrong means adding 12-24 months to your migration timeline.
If you’re Salesforce-committed long-term, ARM is the right destination. It’s not a fast one — plan for 6 to 18 months, and get your SI scoped before the queue fills further. But it’s the only path that gives you a unified data model, a native AI layer, and a product that Salesforce is actively investing in.
If you need to move faster and your product catalog isn’t deeply complex, DealHub gets you off CPQ in under 6 months. The trade is speed versus configurability depth — that’s a reasonable trade for a lot of orgs that were over-engineered in CPQ to begin with.
For the five-phase migration execution plan covering audit methodology, data migration architecture, contract negotiation tactics, and cutover governance, read our Salesforce CPQ End-of-Sale RevOps Migration Playbook — that guide covers the how of the migration once you’ve made the platform decision this one helps you make.
Start your CPQ audit this week. Pull the rule count, the custom Apex inventory, and the integration list. Four hours of structured discovery will tell you more about which path fits your org than any vendor demo.
Related Articles
Discussion