Contact
Privacy
Legal Notice - Impressum
Career
News
Salesforce CPQ is in end of sale, and new revenue capabilities now ship in Revenue Cloud (Agentforce Revenue Management). Moving there is not a quoting upgrade. It is a migration of the pricing history, ramp structures, and quote lines that renewals, forecasts, and billing depend on, and it only works when every quote arrives complete.
Most revenue teams first meet this move as a roadmap decision. Salesforce has confirmed that Salesforce CPQ is end of sale, not end of life: existing customers keep support and critical fixes, while new product innovation goes to Revenue Cloud Advanced, part of the Agentforce Revenue Management suite. No retirement date has been announced, yet the direction is clear.
Agentforce Revenue Management uses a different object model and a different way of writing quotes, and legacy quote data has to be rebuilt to fit it. This article looks at what that data carries, where migrations lose it, and how to plan an Agentforce Revenue Management migration that keeps quotes intact.
It means the platform your quotes live on stops gaining capability while the rest of the revenue stack moves forward. CPQ keeps running, and current customers can renew. What changes is where Salesforce invests.
Salesforce positions Revenue Cloud Advanced as the CPQ successor, built natively on the platform and exposing revenue capabilities through APIs, automation, and agent-ready workflows. Teams that want Agentforce acting on quotes, orders, and renewals will find that work happening in Revenue Cloud, not in the managed CPQ package.
There is a second, quieter cost to waiting. Every quarter on legacy CPQ adds quotes, amendments, and renewals to a data model the organization will eventually leave. The migration does not get smaller with time. It gets larger, and the history it has to carry gets more valuable.
Because the quote record sits at the center of renewal pricing, multi-year commitments, and billing, not only at the moment of sale. Treat it as a quoting tool and the migration plan will focus on the wrong data.
Historical quotes hold the prices and discounts a customer actually agreed to. Renewal teams price against that baseline. When it does not survive the migration, renewals start from list price, negotiations reopen terms that were already settled, and margin erodes in the conversations where it is hardest to recover.
In Agentforce Revenue Management, a ramp deal divides a subscription term into segments, each with its own attributes such as quantity, discount, or dates. Legacy systems often model the same commercial intent through separate lines or manual groupings. Each of those has to be rebuilt into the correct segment and group in the target, or the multi-year price schedule the customer signed no longer exists in the system of record.
Quote lines are the records downstream order and billing processes read from. A line that arrives without its attributes or its parent relationship produces an order that does not match the contract. Finance then forecasts on numbers it cannot trust, and reps requote from scratch instead of selling.
They break when records are moved one object at a time into a model that expects each quote as a complete, related unit. Three structural differences cause most of the damage.
Agentforce Revenue Management introduces structures such as quote line item attributes and quote line relationships that most legacy systems do not have. Salesforce documents that a QuoteLineRelationship describes how quote line items relate, such as items in a bundle, and that it can't be edited or removed once created. A relationship loaded wrong cannot simply be patched later. Every source quote needs enrichment, transformation, and reference resolution before it loads.
Agentforce Revenue Management creates quotes through business APIs such as Place Sales Transaction, which builds a quote or order with integrated pricing and configuration. Line items, attributes, and relationships have to arrive together as one transactional payload. Generic tools that insert records object by object either fail validation or produce quotes that look complete but do not price or configure correctly.
Products and pricebook entries are frequently harmonized during the move, especially when quotes come from several CPQ, CRM, ERP, or billing sources. Historical quotes then have to point to the new catalog while preserving the price that was actually agreed. Lift-and-shift cannot do this, because the reference the old quote used no longer exists in the same form.
These are the same dependency problems that make CPQ one of the Salesforce objects that break data migration projects. Moving into Agentforce Revenue Management adds the transactional load requirement on top.
It should establish scope, mapping, payload design, and validation cycles before anyone commits to a cutover date. Each one is cheaper to get right early than to discover mid-project.
Start with a readiness assessment of every source system: how many quotes, products, and ramp deals exist, how far the product catalog needs harmonizing, and which historical quotes must carry full commercial detail. Timelines depend on exactly these factors, so they belong in the plan before budget is fixed.
Mapping should start from the Agentforce Revenue Management structure, not from the legacy one. Metadata matching across source and target makes visible which fields need enrichment, which relationships need to be derived, and where commercial intent from the old model has no direct home.
Because quotes load as transactions and some relationships are permanent once written, validation has to happen before production. Run full test loads, inspect quotes in the target, and repeat until pricing, ramp segments, and line relationships match the source. Real-time migration tracking keeps every test cycle visible to project owners and revenue stakeholders without a manual status report.
A quote migration that requires a long freeze costs pipeline. Schedule the production cutover around quarter-end and renewal peaks, and use delta loads so reps keep quoting in the legacy system until the last moment. Approvals, proposals, and renewals should continue on schedule, and the first quote a rep opens in Agentforce Revenue Management should already carry the history behind it.
conemis transition cloud (ctc) assembles each quote with its line items, attributes, and relationships, and loads it through a bulk-capable framework on the Sales Transaction API. Ramp deals are rebuilt with their correct group assignments so multi-year pricing arrives intact. Payloads are validated through iterative test loads before production cutover, and the Data Transfer module handles extraction, transformation, and loading with an audit trail the business and its auditors can follow.
Sources are not limited to Salesforce CPQ. ctc migrates quote-to-cash data from Salesforce, Microsoft Dynamics 365, Oracle CX, ERP, and custom applications, and prebuilt CPQ-to-Agentforce Revenue Management templates shorten delivery on engagements that match those patterns. For a short walkthrough of the data challenges involved, see our Agentforce Revenue Management video.
See how revenue teams move off legacy CPQ with quote integrity intact on our Agentforce Revenue Management migration page, book a demo, or contact the conemis team to scope your migration.