Salesforce CPQ Consulting Services
Get more out of the Salesforce CPQ you already run, and a clear-eyed plan for the day it makes sense to move.
Atrium is a Salesforce consulting partner with a dedicated revenue practice. We optimize, extend, and support existing CPQ implementations across quoting, approvals, contracting, billing, integrations, and reporting.
CPQ is end of sale but not end of life, so it still receives support and critical fixes while new development goes to Revenue Cloud Advanced. That shapes our advice rather than replacing it: we keep your CPQ working well now, and when moving is the right call we plan and run the migration to Revenue Cloud Advanced.
Get More from Your CPQ
Most CPQ estates have years of useful life left in them. The work splits in two: getting more out of what you run today, and knowing when moving to Revenue Cloud Advanced is the right call.
Both answers come from the same evidence: how much of your quoting logic lives in Quote Calculator Plugin JavaScript, how many rules are still active, and how much of your catalog should have been retired three acquisitions ago.
What Actually Changes Between Salesforce CPQ and Revenue Cloud Advanced
The reference layer, in four segments. Open the one you are scoping.
CPQ is a managed package with a tightly coupled, quote-centric architecture, adopted all or nothing. Revenue Cloud Advanced is native to the core and API-first, so you can adopt configuration, quoting, ordering, or billing independently. CPQ executes its logic browser-side through rules with sequential execution, where changing the order changes the outcome. Revenue Cloud Advanced executes server-side through declarative procedures and logs each step, so you can explain how a quote reached its result. The product model moves from SKU-based bundles to an attribute-based catalog, and the configurator from rules-based to constraint-based. The clearest signal sits in the developer docs rather than the marketing language: the Place Quote API was deprecated as of API version 63.0 and replaced by the Place Sales Transaction API, raising the line limit from 300 to 1,000.
SBQQ__ProductOption__c becomes ProductRelatedComponent, and nested bundle dependencies need planning. SBQQ__Quote__c becomes Quote and SBQQ__QuoteLine__c becomes QuoteLineItem, where custom fields need manual recreation. SBQQ__Subscription__c becomes Asset, and the full asset action history chain is required, because Revenue Cloud Advanced amends against assets rather than subscription records. That amendment model is genuinely different from CPQ’s and it surprises most teams.
Where CPQ uses record types to identify its records, Revenue Management uses App Usage Assignment records, which must be populated on all transactional records or asset lifecycle operations fail. The asset action history chain is the second: amendments, renewals, and cancellations all run against assets, so an incomplete history surfaces as broken renewals months after cutover. Neither is hard. Both are expensive to find late.
Revenue Management, CPQ, and Salesforce Billing can coexist in one org where all three are provisioned and enabled, which requires both the Revenue Cloud Advanced and Revenue Cloud Billing licenses. In coexistence you can create quotes, orders, and contracts, activate orders to create assets, amend, renew, cancel, and run billing schedules and invoices, and Salesforce publishes further guidance for Subscription Management, sales force automation, Service Cloud, and B2B Commerce. This also explains the Agentforce sequencing: CPQ’s logic sits in browser-side scripts agents cannot reason over, so a CPQ estate blocks Agentforce until the catalog and quoting logic move.
Migrating from Salesforce CPQ to Revenue Cloud Advanced
Treat it as a redesign rather than a migration. Revenue Management is a different system with a different data model and configuration approach, so porting your existing configuration is usually the wrong goal. Salesforce publishes a three-phase approach and recommends engaging a systems integrator during design rather than after it. There is no automated migration tool, and the tools Salesforce has vetted cannot move custom Apex or Quote Calculator Plugin code, integrations, document templates, or page layouts and permission sets, which is where scope actually lives.
Salesforce reports that a typical migration runs three to six months from discovery through go-live, that roughly 15% of Revenue Cloud Advanced customers today came from Salesforce CPQ, and that its own internal move produced a 75% decrease in quoting time and an 87% reduction in clicks. Our Agentforce Revenue Management consulting page covers the destination platform in detail.
Salesforce uses three different terms here, and they are not interchangeable.
What Stays the Same
End of sale means Salesforce stopped selling CPQ to new customers. For you, nothing changes commercially: you keep the licenses you have, you can add users, and you can renew. Salesforce states plainly that the end of sale does not affect your current CPQ contract.
What Keeps Working
End of life, in Salesforce’s words, means a product no longer supported or maintained. That has not happened to CPQ. Salesforce has published no date on which it will, and states there is no forced migration. Neither CPQ nor Salesforce Billing appears on Salesforce’s Active Product and Feature Retirements list.
What Changes Over Time
The maintenance phase is where CPQ actually sits, and it is the one that matters for planning. Support and critical fixes continue, so there is no deadline forcing your hand. What you give up is new features, which is why the case for moving strengthens as you add revenue models, channels, and asset complexity.
Why Atrium for Salesforce CPQ
Revenue engineering is a named practice
Atrium’s Revenue Engineering and Operations team works on Agentforce Revenue Management, Revenue Cloud Advanced, CPQ, and CLM engagements full time, with a scoping and level-of-effort methodology built for catalog and configuration complexity, on CPQ today and Revenue Cloud Advanced next.
800+ Salesforce certifications across 275+ employees
Atrium holds seats on multiple Salesforce Partner Advisory Boards, including Sales Cloud, Service Cloud, Tableau, Data 360, and Financial Services, so the practice sees roadmap direction before it ships.
Measured, not asserted
We define business outcomes at the start of a program and measure against them with conservative attribution. That method is how the $1B in measured customer impact figure was built, and customer satisfaction across engagements runs at 4.9.
Migrations Aren’t One Size Fits All
Revenue models, asset structures, and channel mix differ across technology and software, manufacturing, healthcare and life sciences, and financial services, and the migration scope follows.
Salesforce CPQ FAQ
Is Salesforce CPQ end of life?
No. Salesforce CPQ is end of sale, which means Salesforce no longer sells new CPQ licenses to new customers. Existing customers keep their licenses, can add users, can renew, and continue to receive support and critical fixes. Salesforce has not announced an end-of-life date and has stated that CPQ is not being switched off. CPQ is in a maintenance phase, supported but no longer receiving new feature development.
If we stay on Salesforce CPQ, do we still get support and security fixes?
Yes. Salesforce’s published position is that existing customers continue to receive support and critical fixes during the maintenance phase. Claims that support ends on a specific date, or that Salesforce will stop patching vulnerabilities, have no Salesforce source and contradict what Salesforce has published. What you do lose is new functionality, since all new development is going into Revenue Cloud Advanced and Revenue Cloud Billing.
Can we keep buying Salesforce CPQ licenses for new sales reps?
Yes. Existing CPQ customers can add users and renew licenses. End of sale applies to selling new CPQ licenses to new customers. Salesforce also states that the end of sale does not affect your current CPQ contract, so the practical constraint on staying is the widening feature gap rather than a licensing cliff.
Is Salesforce Billing also end of sale?
Yes. The Salesforce statement covering CPQ covers Salesforce Billing as well: existing CPQ and Billing customers continue to receive full access including support, and can renew and add licenses, while new customers are offered Revenue Cloud Advanced and Revenue Cloud Billing instead. Like CPQ, Salesforce Billing does not appear on Salesforce’s official product retirements list.
What happens to our quoting rules and Quote Calculator Plugin code in a migration?
CPQ’s sequential rules become declarative procedures and elements, and execution order logic differs significantly, so rules cannot be ported one for one. Quote Calculator Plugin JavaScript and custom Apex cannot be migrated by any tool and have to be reimplemented in Revenue Cloud Advanced concepts. Because that logic is invisible in quote output, the usual approach is explainability tooling across all rules and scripts, then validation against a curated pack of historical quotes with known outputs.
Can we run Salesforce CPQ and Revenue Cloud Advanced at the same time?
Yes, and Salesforce officially supports it. Coexistence requires both the Revenue Cloud Advanced and Revenue Cloud Billing licenses with billing enabled in Revenue Management, and Salesforce publishes coexistence guidance for CPQ, Salesforce Billing, Sales Cloud, Service Cloud, and B2B Commerce. Phased cutover by business unit or product line is the most common approach, and it is the reason a migration rarely needs to be a single event.
Latest Insights from Our Experts
Ready for Real Results?
Reach out to our team—dedicated to the metrics that matter most. We’re here to help you adapt and grow.