“Treat RCA as an opportunity to simplify your catalogue and pricing logic—you’ll gain speed, accuracy, and cleaner analytics on day one.”
“End of Sale” (EOS) means Salesforce is no longer selling CPQ to new customers. Existing tenants can continue to use it and renew, but net-new innovation prioritises Revenue Cloud Advanced (RCA). Practically, expect fewer new features, slower fixes, and an accelerating roadmap around RCA for configure-price-quote, contracting, subscriptions, and billing.
Remaining on legacy CPQ isn’t a crisis today—but risks accumulate fast:
Operational drag: limited enhancements lead to more manual workarounds and admin overhead.
Change velocity: slower fixes and no net-new capabilities can stall pricing innovation and new commercial models (usage, bundles, consumption).
Total cost of ownership: rising maintenance and technical debt as integrations and custom rules age out.
Talent & skills: partner and admin communities are shifting focus to RCA, narrowing the expert pool on legacy CPQ.
Come on Hop Hop - who doesn't love an AI generated image of a bunny with flowers. :)
If your roadmap includes dynamic pricing, usage-based selling, or richer quote-to-cash automation, delaying RCA planning can turn small compromises into systemic constraints.
RCA is Salesforce’s strategic successor that unifies product catalogue, pricing, configuration, contracts, subscriptions, billing, and revenue operations on core platform services. Expect tighter data consistency, AI-assisted configuration, headless capabilities for omnichannel quoting, and closer alignment with modern revenue motions (self-serve, partner, sales-assisted).
Step 1 — Business outcomes first: Define the 3–5 commercial capabilities you must enable (e.g., usage pricing, guided selling, new packaging).
Step 2 — Catalogue rationalisation: Consolidate SKUs, attribute models, and option bundles; retire what you don’t need.
Step 3 — Policy & pricing rules: Inventory approvals, discount ladders, contracts/renewals, and usage events; decide what to keep, simplify, or redesign.
Step 4 — Data migration approach: Map products, price books, assets/subscriptions, open quotes, and contracts. Identify historical cut-over vs. coexistence.
Step 5 — Integration plan: Confirm touchpoints (ERP, tax, payments, CLM, entitlement, data warehouse) and event flows.
Step 6 — Change & adoption: Build role-based enablement for Sales Ops, Finance, and Sales; run UAT against real deal scenarios and edge cases.
Many enterprises phase migration by business unit, region, or product line. Coexistence lets you launch new offers on RCA while servicing renewals on CPQ, then retire CPQ in waves. A hard cut-over can be faster but demands pristine data and tighter readiness gates.
Plan for discovery, catalogue clean-up, RCA configuration, integrations, data migration, and enablement. Budget flex depends on complexity (SKU volume, custom pricing logic, contract models). Coordinate with quarterly Salesforce releases so you can leverage new RCA features rather than custom-building them.
“Treat RCA as an opportunity to simplify your catalogue and pricing logic—you’ll gain speed, accuracy, and cleaner analytics on day one.”
“A thoughtful migration beats a fast migration: start with outcomes, then design catalogue, data, and integrations to serve them.”
Is CPQ being switched off? No. EOS means no new sales and reduced forward investment, not a hard stop for existing orgs.
Do we need to move now? Not instantly—but begin planning so you can migrate on your schedule, not when risk forces it.
Will our CPQ skills transfer? Some do, but RCA’s architecture and rule models differ. Plan enablement for Sales Ops, Admins, and Finance.
What’s the fastest path? Start with a pilot scope (product family or region), validate your pricing rules, then expand in waves.
Next step for your business: If you’re weighing options, we can run a 2-week readiness assessment—catalogue health, rule complexity, integration map, and a phased RCA plan.