Page History

...

• Jira-managed data: Includes issue summaries, descriptions, custom fields, workflows, and permissions. This data is transferred using Atlassian’s Cloud-to-Cloud migration tool.

• X-rayXray-managed data: Includes test steps, test runs, links between issues (e.g., Test → Test Plan), and X-ray-specific metadata. These need to be migrated separately.

Pre-Migration Checklist

1. Xray Installation Health Check

Make sure that Xray is properly correctly installed on the destination Jira Cloud instance:

...

• Test
• Test Plan
• Sub Test Execution
• Precondition
• Test Execution
• Test Set

If these issue types do not match, you may need to manually move migrated issues to the correct types after the Jira migration.

Recommended Method to migrate: 

...

To migrate the Xray from Cloud to Cloud, you must combine manual exports and imports via  Docgen & Test Case Importer and REST API & GraphQL.

There are two ways to migrate Xray from Cloud to Cloud:

1. Using Manual Exports and Imports: You can utilize Docgen and Test Case Importer to perform exports and imports manually. This method involves exporting entities like Test Sets, Tests, Preconditions, and Test Repository structure from the source instance and importing them with the Xray Test Case Importer. 

2. Using Xray APIs: You can leverage a combination of REST API endpoints to import test types, test runs, and other data and the GraphQL API to transfer all Xray entities, including Tests, Test Plans, Test Executions, Test Repositories, Preconditions, and links between tests.

The difference between the options mentioned above is that using the Xray APIs is option 1; you will need to create some scripts to make this process faster and less manual. Option 2 uses Doc Gen + Test Case Import and more of the Xray APIs.  The easiest way to migrate is using option 2. However, this option works only to import the Tests mentioned above, and to migrate the other Xray data you must use the Xray APIs.

...

• The CSV source file must follow some simple rules.   Preparing the source file. You can name the fields as you wish since they are going to be mapped during the importation process, but three mandatory fields must be mapped. 
• Issue Id – a unique identifier for the issue; this field is used to group lines that belong to the same test case or to identify a precondition or a test set.
• Summary – this field is mandatory since Jira doesn’t allow you to create an issue without a summary.
• Test Type – this field defines the test type of the each test to import. The test type must match one of the types of the project to which the test is being imported.

Finally, the remaining Relations and the Test Run's Data should be transferred by performing exports and imports with REST API and Xray's GraphQL API. This method is necessary because this data is not saved in Custom Fields but by our field entities, which cannot be handled by default export methods or the REST API cannot handle.

Final Step: Before importing the Xray Data: Re-index the Project

...

• Go to Project Settings in the destination instance

• Click on Xray Settings > Re-indexing

• Click Re-index and confirm the action

After re-indexing, you can import the Xray data to the destination instance. 

If you have any questions or doubts, please contact the Xray Support team! 

...