Alternative solutions for migrating JSM Cloud Assets Schema from Sandbox to Production

Summary

Learn how to copy or move Jira Assets Object Schemas, including object types, attributes, and objects, between Jira Cloud instances.

Solution

Current status and limitations

Jira Cloud currently lacks native support for direct migration of complete Assets Object Schemas between cloud sites. Atlassian is aware of this limitation and is tracking customer interest through these feature requests:

• Support Cloud to Cloud migration for Assets

• Support "Copy Product Data" for JSM Assets

Workaround 1: Manual export/import (CSV or REST API)

Export object data from your source schema and import it into your target schema.

• Export objects

• Prepare your data for importing into Assets

Limitations

• Schema Structure: The Object Schema structure must be manually recreated in the target instance before importing the object data.

• Schema Configurations: Settings like import configurations and Assets automation rules will not be migrated.

• Custom Field Values: Links between Jira custom fields and Assets objects might not be preserved or may need re-mapping.

• Object Keys: New keys are generated upon import, affecting JQL queries and integrations.

• Object History: The history of changes for each object is not migrated.

Workaround 2: third-party Marketplace apps

Explore third-party apps in the Atlassian Marketplace for Jira migrations or data synchronization.

• Action: Look for tools specializing in Jira instance migration or Assets/Insight data migration.

• Considerations: Evaluate apps based on features, reviews, support, and cost.