---
title: "[Xray Cloud] - Completed a Cloud-to-Cloud migration using the Jira tool, but Xray data is missing?"
canonical: "https://docs.getxray.app/space/ProductKB/46269310/%5BXray%20Cloud%5D%20-%20Completed%20a%20Cloud-to-Cloud%20migration%20using%20the%20Jira%20tool%2C%20but%20Xray%20data%20is%20missing%3F"
format: markdown
---
> ℹ️ This documentation is intended for customers performing a Cloud-to-Cloud migration using Jira tools.
If you are on this page, you've performed a Cloud-to-Cloud migration using Jira tools, but the Xray data is missing when comparing the source and destination instances. This behavior is expected, as Atlassian's tool does not transfer Xray data between instances. After completing the Jira migration ( [Migrating from one Cloud instance to another Cloud instance](https://confluence.atlassian.com/confeval/other-atlassian-evaluator-resources/migrating-from-one-cloud-instance-to-another-cloud-instance)), you must manually migrate the Xray data.
To migrate the Xray from Cloud to Cloud, you must combine manual exports and imports via [Docgen](https://getxraydocs.atlassian.net/wiki/display/XRAYCLOUD/Exporting+Tests+using+Document+Generator) & [Test Case Importer](https://getxraydocs.atlassian.net/wiki/display/XRAYCLOUD/Importing+Tests+using+Test+Case+Importer) and [REST API](https://getxraydocs.atlassian.net/wiki/display/XRAYCLOUD/REST+API) & [GraphQL](https://getxraydocs.atlassian.net/wiki/display/XRAYCLOUD/GraphQL+API).
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.
Please note that Xray plans to add a feature to migrate Xray information between two Cloud instances. We have this suggestion already reported [XRAYCLOUD-4703](https://jira.getxray.app/browse/XRAYCLOUD-4703) to gather our customers' interest in this feature and be analyzed to improve future product versions. Please click on the **Vote** button so we can keep track of your interest, and then click on the **Watch** button to receive news on the suggestion.
Before importing any data to Xray, please note that it is important to perform an **Xray Re-indexing**. In some cases, after the cloud-to-cloud migration using the Jira tool ([Migrating from one Cloud instance to another Cloud instance](https://confluence.atlassian.com/confeval/other-atlassian-evaluator-resources/migrating-from-one-cloud-instance-to-another-cloud-instance)), Xray might not recognize the migrated issues.
To fix this, you’ll need to re-index the project.
Please follow these steps to re-index the project:
1. Go to the **Project Settings** on the destination instance.
2. On the left-hand menu, find **Xray Settings** and click on **Re-indexing**.
3. Click the **Re-index** button.
4. You’ll see a confirmation screen (screenshot below). Click **Confirm** to proceed.
After re-indexing, you can import the Xray to the destination instance.
**If you have any questions or doubts**, please get in touch with the [Xray Support team](https://jira.getxray.app/servicedesk/customer/portal/2/SUPPORT-85471)[!](https://jira.getxray.app/servicedesk/customer/portal/2/SUPPORT-85471)
## Related articles
> Macro (contentbylabel)
> Macro (details)
>
> | **Related issues** | > Macro (jira) |
> | --- | --- |