...

If you are looking to migrate from Jira Server/DC to Jira Cloud, you need to consider the differences between Xray Server/DC and Xray Cloud. These differences might affect how your users work and interact with Xray.  

The ideas, goals, and major features are the same. However, while there is great similarity between them, there are a few subtle differences between the two versions. This is mainly due to:

• Jira architecture - The way apps work in Server and Cloud is completely different. In Server, apps can integrate with many aspects of Jira, while on Cloud, there are a lot of integration points missing, e.g. JQL functions, Project Templates, etc
• Product Age - Xray Cloud is a newer product. Therefore, some of the features are not yet present (e.g. Automated Step Library, Historic Test Coverage report), although we plan to include these features in future releases. Also, we took the opportunity to improve some features (e.g. Project Level Settings).  

For a full comparison between the Server/DC and Cloud versions of Xray, please refer to to Xray Server and Xray Cloud.

Jira Cloud Migration Assistant  Assistant

Atlassian provides the Jira Cloud Migration Assistant to help Jira users assess and migrate from an on-premise Jira instance (Server or Data Center) to Jira Cloud. 

Our team has worked with Atlassian to make Xray available within the official Migration Assistant tool and we hope Atlassian will launch this expanded version of the Migration Assistant.

Before going any further, check the official Atlassian documentation and procedure:  

https://support.atlassian.com/migration/docs/use-the-jira-cloud-migration-assistant-to-migrate/

...

E.g., all the Tests in the Test Plans of Project A must be part of the migrated Projects. 

Known Limitations

Issue History and Test Run Activity

...

The name of the issue types needs to be the same on both server and cloud before starting the migration. 

The Issue Type Precondition/Pre-Condition may have to be changed as it is named differently in the server and cloud versions of Xray.

https://support.atlassian.com/jira-cloud-administration/docs/add-edit-and-delete-an-issue-type/

Edit Requirement ↔ Requirement ↔ Test Link

The Issue Link used for Requirement Coverage is slightly different between Xray Cloud and Xray Server/DC. To ensure that Xray Cloud will recognise these links, the Issue Link type must be edited on Server/DC to match the link used by Xray Cloud:

• Name: Test
• Outward Description:   tests
• Inward Description: is tested by

...

If you are using Security Levels for Xray Issues - e.g. Test, Test Set Set -  youyou'll have to remove the Security Schemes/Levels or, alternatively, grant access to any logged in user for the duration of the migration.

...

• the group of Projects that you are migrating contain any Xray links to data outside of these Projects. 

If there are any such links, Xray will let you know which projects should be added to the migration to avoid ending up with missing links in the Cloud instance.  This This check should be done before any migration begins.

The preflight checks are available when the Jira the Jira Cloud Migration Assistant is installed and a version of Xray supporting the migration to Cloud is also installed. The page can be found in the Administration → Manage Apps → Xray → Apps → Xray → Cloud Migration. Here you should add all the projects for your migration and then press Validate. If there are no errors, you can leave this page and proceed with your migration through the Jira Migration Assistant. If there are any errors you can see the details and steps to fix the issues. 

Example: Project XT was selected for migration. The preflight checks found that there is a link to another project which is not part of the migration (XDTP).

...

There are no more errors, meaning that these two projects can be migrated together safely.   We can now go back to the Jira Migration Assistant and plan our migration with both projects.

...

If the Xray migration is not successful during the Jira cloud migration plan,  we we highly recommend trying it again. Before trying again, make sure the cloud project is removed. If the issue persists, please contact our support in order to get help.

...