Salesforce CPQ Is End of Sale.
The Window Is Open ,
But Not Forever.

Salesforce CPQ entered End-of-Sale status in March 2025. No new licenses are being issued and no further product innovation will take place. The strategic direction is unambiguous: Salesforce's entire revenue platform investment has moved to Agentforce Revenue Management.

⚠️ Risks of Staying on Legacy CPQ
  • ✗No new features or innovation , Salesforce has permanently halted all CPQ product development
  • ✗Structurally locked out of Agentforce AI integration , a permanent competitive disadvantage
  • ✗Escalating technical debt from undocumented customisations, zombie pricing rules, and legacy Apex scripts
  • ✗Governor limit conflicts that grow worse as org complexity and transaction volumes increase
  • ✗Inability to support subscription, usage-based, or hybrid pricing models without significant custom dev
  • ✗Growing security and compliance exposure as the managed package platform ages
  • ✗Renewal window expected to close around August 2026 , leaving no room for a last-minute migration
✅ What You Gain with ARM
  • ✓Native platform architecture eliminates managed package limitations, version conflicts, and data sync delays
  • ✓Constraint-based CML configuration engine replaces brittle rule chains with a server-side solver
  • ✓Unified data model across quoting, contracts, billing, orders, and revenue recognition
  • ✓Full Agentforce AI integration , agents quote, price, renew, and audit billing autonomously
  • ✓Subscription, usage-based, milestone, and hybrid pricing supported out of the box
  • ✓Context Service bridges structured CRM data with unstructured signals for intelligent agent decisions
  • ✓Attribute-based catalog management reduces SKU count by up to 80%

Our Proven 5-Phase
Migration Framework

1

Discovery & Assessment

Audit all CPQ configurations, pricing rules, approval workflows, integrations, and technical debt. Surface undocumented customisations and zombie rules before architecture begins.

2

Revenue Architecture Design

Redesign for ARM's constraint-based logic. Define catalog structure, pricing procedures, and recognition rules from first principles , not copied from CPQ.

3

Data Preparation & Mapping

Cleanse the catalog, eliminate duplicate SKUs, and create field-level mapping from CPQ objects to ARM entities. Validate data integrity before migration begins.

4

Phased Build & Testing

Configure ARM modules incrementally in sandbox. Run full sandbox migrations, UAT across all teams, and regression testing before any production deployment.

5

Rollout & Optimisation

Deploy via bridge strategy , new deals go live in ARM immediately, existing contracts transition at renewal. Monitor KPIs and optimise continuously post-launch.

Do's and Avoid's

✓ DO , Treat this as a re-architecture, not a technical lift-and-shift

✗ AVOID , Do not recreate CPQ rules directly in ARM , they do not mirror legacy logic

✓ DO , Clean and slim the product catalog before migration begins

✗ AVOID , Do not attempt a big-bang cutover. Use a phased bridge approach

✓ DO , Strengthen your RCA fundamentals before layering on agents

✗ AVOID , Do not skip the Context Service design step , agents need situational awareness

✓ DO , Partner with a certified ARM implementation specialist

✗ AVOID , Do not rely on old CPQ data structures for ARM object mapping , ARM uses a fundamentally different model

Start Your Migration Journey

Our certified ARM specialists are ready to assess your CPQ environment and design your migration architecture.