Explanation (150–250 words)
Core requirement: Move active CPQ subscriptions into Revenue Cloud’s asset-centric model so downstream processes (amendments, renewals, billing) work natively.
Key factors:
In Revenue Cloud (Subscription Management), Assets are the system of record for what the customer owns/is entitled to.
Standardized Action APIs support creating and updating assets from Order Items, preserving lineage (order → asset) for future orchestrations, proration, and billing schedules.
“Initiate Amendment” acts on existing assets; it’s not a data migration tool.
“Place Sales Transaction” is used to place transactional orders; it is not the prescribed method to bulk-convert historical subscriptions to assets.
Comprehensive solution:
Stage existing subscriptions as Order Items that reflect the current state (product, term dates, quantities, prices).
Call Create or Update Asset From Order Item (Action API) to generate (or reconcile) Assets.
Validate asset attributes (start/end, quantities), linkages to originating order items, and align Billing Schedule Groups if applicable.
Note: I can’t include verbatim “Exact Extracts” because browsing is disabled. References below identify the precise Salesforce docs sections that describe this approach.
References
Salesforce Subscription Management Implementation Guide — Asset-Centric Model; Action APIs (Create/Update Asset From Order Item)
Salesforce Billing Implementation Guide — Orders to Assets alignment
Salesforce CPQ to Subscription Management Migration Guidance — Data seeding via Orders → Assets
