01
No forced migration, no new features either
You choose the date, but the capability gap widens every release.
Salesforce CPQ is end of sale. New quoting, pricing and billing investment now lands in Revenue Cloud, and every quarter on the legacy package widens the gap. We plan and deliver the move, and build Revenue Cloud Advanced greenfield for teams starting clean.
Book a Revenue Cloud Assessment See the Telecom DemoEnd of sale is not end of life. Your licences keep working and no shutdown date has been announced. What changed is where the investment goes.
Feature development on the legacy managed package has stopped, and new quoting capability for buyers, partners and renewals now ships in Revenue Cloud instead. Salesforce has also put a CPQ migration assistant on its roadmap, which tells you where the ecosystem is heading.
The honest part most partners skip: this is a re-implementation, not an upgrade. Legacy CPQ lives in a managed package with its own object model. Revenue Cloud Advanced is built on the Salesforce core platform, API-first, and your pricing rules, bundles and approvals have to be redesigned rather than copied across. Salesforce puts a typical migration at three to six months from discovery to go-live. That makes it a planning decision, not a fire drill, and planning it badly is where the cost shows up.
You choose the date, but the capability gap widens every release.
Rules, bundles, approvals and discount structures are redesigned on a different model.
Quoting, pricing and billing run on the platform, open to any channel or self-service front end.
Agentic revenue capability is being built on the core object model, not on the legacy package.
Six capability areas, each one a place where RCA projects usually go wrong.
Attribute-driven products, bundles, eligibility and compatibility rules modelled on the core catalogue, so your commercial team can launch an offer without a release.
Price books, adjustments, tiered and volume pricing, usage rates and time-bound promotions. Pricing procedures built to be read and changed by admins, not reverse-engineered by developers.
Transaction Line Editor, guided flows, approval matrices and document generation. Legacy quote logic is rebuilt as native pricing procedures rather than ported.
Mid-term changes, upgrades, downgrades, suspensions and co-terminated renewals, with proration that holds up under audit.
Subscription, usage-based and one-off charges, billing schedules, invoice runs, credits and revenue recognition handled natively in RCA.
API-first quoting exposed to partner portals, D2C journeys and agentic assistants, so the same pricing engine serves rep-led and self-service channels.
From a three-week assessment to a full greenfield build and the support that follows it.
Inventory of your CPQ configuration, complexity scoring, target architecture, phasing options and an effort estimate.
Typical outcome: a board-ready migration business case in 3 to 4 weeks.
Catalogue and pricing redesign, data migration, parallel-run and cutover planning, regression testing against your real deal shapes.
Typical outcome: live on RCA in 3 to 6 months, legacy CPQ retired on a planned date.
Lead-to-cash process design across Sales Cloud and RCA, with catalogue, pricing, quoting, ordering, billing and revenue in one MVP-first build.
Typical outcome: a quote-to-cash backbone your team can extend themselves.
Usage rating, dynamic tiers, entitlements and consumption alerts, invoice runs, credit notes and revenue schedules, with ERP and payment hand-off design.
Typical outcome: monthly billing that closes without spreadsheets.
Release adoption, pricing-model changes, performance tuning on large catalogues, and admin enablement, on flexible or retained support.
Typical outcome: new offers launched by your own team, in days.
Discover. Map. Transform. Validate. Migrate.
Most of a CPQ migration's cost is spent working out what the legacy org actually does: which of the 400 price rules still fire, which bundles are dead, which approvals were built for a team that no longer exists. Our Accelerator does that discovery mechanically.
It reads your Salesforce CPQ, Industries CPQ or Communications Cloud configuration, maps it against the Revenue Cloud Advanced model, flags what cannot be carried across, and generates target configuration and migration data sets for the parts that can.
Talk to us about your orgBundled offers, usage that has to be rated, mid-contract changes every month and a renewal base too large to touch manually. These are scenarios we have designed and built on Sales Cloud plus Revenue Cloud Advanced.
Mobile, fibre broadband, fixed voice and a bundled streaming subscription, modelled with attribute-driven products, compatibility and eligibility rules, bundle-level discounts and dated promotions. One guided quote assembles and prices the household offer.
Result: a new bundle is configured by marketing, not shipped as a release.
Data, roaming and voice bundles rated with tiered rates, entitlement counters and consumption thresholds, feeding billing schedules and invoice runs inside RCA.
Result: usage, subscription and one-off charges on one invoice, rated against the rate card live on the usage date.
Amendments with correct proration, co-terminated end dates, device and contract-term handling, and credit generation where a downgrade warrants it.
Result: change orders processed without manual credit notes, and an asset base that still reconciles at month-end.
Site-level configuration against a negotiated rate card, contracted pricing that survives renewals, volume commitments and approval matrices by margin and term.
Result: a hundred-site quote generated in minutes, priced to the framework agreement every time.
The same catalogue and pricing engine exposed to reps, partner portals and D2C journeys, and to Agentforce agents that quote, amend and answer billing questions against live entitlement data.
Result: one price for one customer, whichever door they come through.
Industry data model, product specifications and order decomposition mapped into RCA, phased so order management and billing are not cut over on the same weekend.
Result: a migration sequence that keeps provisioning running throughout.
Four phases, each ending in something you can review. No phase runs blind into the next.
Configuration inventory, complexity score, target architecture, effort estimate and business case.
Catalogue and pricing model, process design, data migration plan, test strategy and release sequence.
Configured org, migrated data, quote-replay validation results and UAT sign-off.
Production go-live, in-flight quote handling, four weeks of hypercare and admin handover.
Phases 2 and 3 overlap on larger programmes, and a phased go-live by product line or business unit is usually safer than a single cutover. Complex catalogues, heavy custom code or an industry data model push the timeline out, which is exactly what Phase 1 is there to tell you before you commit.
Quote-to-cash is a core practice here: CPQ, Industries CPQ, Communications Cloud and Revenue Cloud Advanced.
The Revenue Cloud Migration Accelerator removes guesswork from discovery and proves pricing parity before cutover.
Bundles, usage rating, amendments and renewals designed against a working lead-to-cash model.
150+ implementations delivered across Sales, Service, CPQ and Industries.
Brussels, Paramus and Pune, so design happens in your time zone and build scales economically.
BRDs, traceability matrices, test scenarios and functional mappings come as standard, not as a change request.
No. Salesforce CPQ is end of sale, not end of life. Existing customers keep their licences, can add users and renew, and continue to receive support. What has stopped is new feature development, with investment moving to Revenue Cloud Advanced. No end-of-life date has been announced.
It is Salesforce's core-native revenue platform covering product catalogue, pricing, quoting, contracts, order capture, billing and revenue recognition. Unlike legacy CPQ, which ran as a managed package, RCA is built on the Salesforce platform itself and is API-first, so the same pricing engine can serve reps, partner portals, self-service journeys and AI agents.
Not entirely. The data models differ, so pricing rules, bundles and approvals are redesigned rather than copied. Salesforce has a migration assistant on its roadmap, and tooling such as our Migration Accelerator automates discovery, mapping and validation, but the commercial logic still needs a deliberate redesign.
Salesforce puts a typical migration at three to six months from discovery to go-live. Catalogue size, custom code and the number of integrated systems move that number more than anything else. Our assessment gives you a defensible estimate in three to four weeks.
No, and there is no deadline forcing you. But new quoting capability is shipping only in Revenue Cloud, so the gap grows each release. Most teams we talk to are assessing in this budget cycle and migrating in the next.
Yes. Usage rating, tiered and volume rates, entitlement counters, billing schedules and invoice runs are native. For telecom and consumption-led models this is the main reason to move off legacy CPQ, which was never built for it.
Yes. We have built lead-to-cash designs covering mobile, fibre, fixed voice and bundled streaming products, including usage billing with dynamic tiers, mid-contract amendments and multi-site B2B contracts. We can demonstrate these against your own portfolio.
Belgium, India and the United States, supporting clients across Benelux, the UK, Europe and North America.
India +91 9156025822 · USA +1 6467774977 · Belgium +32 24033629 · info@pletratech.com
Chatbot