We're planning a large migration of legacy Asset records into Revenue Cloud and want to confirm we're not missing a bulk-friendly path.
We've confirmed HasLifecycleManagement, LifecycleStartDate/EndDate, and the underlying AssetStatePeriod object are all read-only via standard DML - Data Loader/Bulk API reject any attempt to write them (INVALID_FIELD_FOR_INSERT_UPDATE).
The only supported path we've found is the Connect REST API generate endpoint (asset-management/assets/actions/generate). It looks like a single-asset-per-call API with no bulk/batch equivalent, and the start date of the first asset state period is locked once the call completes.
Has anyone done a large historical Asset migration into lifecycle management this way? Curious about:
- Whether a bulk-friendly path exists that we're missing
- Realistic call volumes/patterns others have used against the generate endpoint
- Whether it's common practice to leave older/inactive assets non-lifecycle-managed and only onboard active ones
- Appreciate any recommendations.
we did it using PST api. the approach here is to bulk create Order using PST and then activate the Order, it will create Asset lifecycle managed records automatically, this is will give audit history as well.
PST api supports bulk record creation (1500 records in a single api call).
