Hi everyone,
I recently worked on migrating JSM projects along with Assets schemas and Asset fields from Data Center to Cloud using the JCMA Assets migration (beta) feature. I wanted to share my experience and also learn how others are handling similar scenarios.
What worked well
Asset schemas were migrated along with object types, objects, and their relationships
Basic Asset field types were successfully migrated, with values retained in tickets
The beta feature definitely simplifies a significant part of the migration effort
Challenges faced
Legacy Asset field types and Reference Asset field types are not supported in JCMA migration
Archived objects in Data Center were migrated as active (unarchived) objects in Cloud, since the archive feature is currently unavailable
Data Center supports Asset post functions in workflows, which are not available in Cloud
Cloud introduces Assets limitations based on plans, unlike Data Center
What I did as a workaround
Identified unsupported Asset field types in advance and converted them into supported types before migration and updated all references (JQL, workflow post-functions, automations) since field conversions were not automatically reflected
Performed post-migration cleanup to handle archived objects that were migrated as active
Recreated Asset post-function logic using automation rules in Cloud
- Cleaned up Asset data in Data Center prior to migration to stay within Cloud limits
Open questions 👇
How are you handling unsupported Asset field types during JCMA migrations?
Has anyone found a better way to manage archived objects during migration?
Any additional lessons learned while working with the Assets migration beta feature?
Would love to hear how others are approaching this, especially as the feature continues to evolve.
Thanks,
Yashaswini.
