Before attempting to migrate migrating from Xray Server/DC to Cloud be sure you've completed the steps recommended at "Steps to a successful migration":
Learn more at "Steps to a successful migration".
- 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, calculated fields at agile boards (like requirement status), 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).
E.g., all the Tests in the Test Plans of Project A must be part of the migrated Projects.
Avoid data change during the migration, otherwise the migration might fail.
Issue History and Test Run Activity
Configuration of Xray gadgets will not be migrated.
Xray Notifications (events) will not be migrated. Xray Cloud does not provide this feature.
Xray data belonging to the archived issues are not migrated.
In the past we've seen migrations failing due to archived projects. Xray does not have visibility/permissions into these projects so please check if you are trying to migrate archived projects.
Templates migrated from the Server must be revised once there are some differences between the server and cloud version.
A valid Xray app license is required to migrate Xray data, otherwise, Xray data won't be migrated to the cloud.
Jira migration stage must be successful
Before the Xray migration stage is executed, all issues and Jira entities are migrated by Atlassian's JCMA. In order to guarantee that Xray migration is successful, all these Jira entities must be 100% migrated, without warnings. If you encounter problems in Jira's migration stage, please contact the Atlassian support team.
Edit Issue Type Names
The name of the issue types needs to be the same on both server and cloud before starting the migration.
If you are using Security Levels for Xray Issues - e.g. Test, Test Set - you'll have to remove the Security Schemes/Levels or, alternatively, grant access to any logged in user for the duration of the migration.
These checks are meant to help you plan your migration by taking into consideration Xray related constraints. The checks will let you know if:
It is recommended that you select the option "All users and groups from the Jira directory" when choosing which users to migrate in the Jira Migration Assistant. This is due to the way that Jira checks which users are related to a project which will not consider users assigned to Test Runs.
The Migration Process
The Xray migration starts right after the Jira migration. While Xray is migrating projects, the Xray app screens/actions will be disabled until the end of the migration. Those screens will show a warning and an action to allow the user to see the current progress of the migration. This progress shows details about what is being done.
Xray Cloud also provides a page on the app administration section with all the migration plans in progress and done. Here the Jira administrator could see the history of migration and the ongoing migration plans. Learn more about this here.
If the Xray migration is not successful during the Jira cloud migration plan, 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.
To learn more about migration from Xray Server to Xray Cloud you might want to take our dedicated course available for free at Xray Academy: Migration from Xray Server to Xray Cloud