...

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 sometime soon.

Introduction

This page concerns the migration of Xray from Server to Cloud hosting through the Jira Cloud Migration Assistant app. 

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

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

https://support.atlassian.com/migration/docs/jira-pre-migration-checklist/

Migrating Xray data through Jira Cloud Migration Assistant: 

Any Xray related projects that have relations between them must be migrated together within the same migration, otherwise any Xray links between the projects will not be present in the Cloud after the migration. E.g. all the Tests in the Test Plans of Project A must be part of the migrated Projects. 

Steps to a successful migration

Edit Issue Type Names

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/

Preflight Checks

These checks are meant to help you plan your migration by taking into consideration Xray related constraints.

The checks will let you know if 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 check should be done before any migration is started.

The preflight checks are available when 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 → Cloud Migration.

Here you should fill all the projects for your migration and then press Validate.

If there are no errors, you may now 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 issue.

For Example:

Image Added

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

We now add the missing project to the preflight checks and validate:

Image Added 

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.

Limitations

Issue History and Test Run Activity

Due to the textual nature of the data in the activity logs, the entries are mostly copied as is. The language, phrases and markups may differ from Server to Cloud.

Migration drift not supported

All the linked data must be migrated together so data integrity can be guaranteed on the Cloud.

Automated Step Library

Not supported by Xray Cloud and will not be migrated.

Cucumber settings

Will not be migrated to cloud. (Miscellaneous settings section)

Xray Cloud Migration Scripts 

Status
colour Yellow title AVAILABLE - With No Support

...