We completed the Jira Cloud-to-Cloud migration, including data from the Xray Test Management for Jira application, for three months.
Migrating data between two Jira systems can be challenging, especially when it involves critical information from third-party applications such as Xray Test Management for Jira. In this article, we’ll explain how we helped the client with a complex migration and overcame the challenges of transferring test data.
Challenge: Ending Jira system and the need to preserve data
Our client found themselves in a situation where they were working in a Jira system from another company on several projects. However, this system was soon to be decommissioned, which posed the risk of losing essential data. As a result, they decided on a Cloud-to-Cloud Jira migration to their environment to retain all the data securely.
The initial migration was only partially successful – critical data from Xray Test Management for Jira was missing. Since the original system was to be shut down soon, they needed us to supplement the data within several weeks.

Solution: Detailed analysis and quick implementation
We analyzed the current state together at the initial meeting and identified all the missing data. We prepared a short questionnaire, which helped us determine the scope of the necessary work and optimize the migration process.
Analysis of source and target environments for Jira migration
The first step was analyzing both the source and target environments. It was necessary to map all existing data and check for potential conflicts with target data – including applications, projects, automation, and custom fields. We found that the target Jira environment still contained incomplete data from a previous migration that the client had performed. Therefore, we first had to remove the incomplete data to conduct the migration properly.
Creating a testing environment and preparing for the Xray migration
The next step was creating a Jira testing environment where we could safely verify the migration process without the risk of damaging target data. After agreement with the client, we determined the scope of migrated data – approximately 30 Jira projects, half of which used the Xray Test Management application. The client was not interested in migrating other applications.
The data transfer via Atlassian tools proceeded without complications, but as expected, Xray data were not automatically included in the migration. Therefore, we had to implement our solution to supplement them.
Collaboration with the Xray supplier and dividing the migration into steps
To ensure a complete transfer of Xray data, we contacted the supplier of the Xray application – Xblend. Based on their documentation, we identified that the migration needed to be split into two main steps:
- Supplementing test data, test sets, and assumptions – Not the tasks themselves, but Xray data associated with them. We exported this data to the Xray Document Generator and then imported it into the target environment using the Xray Test Case Importer.
- Supplementing all data for test execution – We created our script to retrieve the data through the GraphQL API and upload it to the target environment via the REST API. During this part of the migration, we had to address several technical challenges:
- Each environment may be in a different region and have a different API URL.
- Attachment data had to be obtained via separate requests.
- Defect information is returned as an issue ID, but the issue key must also be obtained. These were then supplemented into the target environment.

Merging configuration and completing the Jira migration
After the migration, it was necessary to merge the configuration of the Xray application itself, such as test statuses and test steps, and manually reconfigure the migrated projects, including adding Xray custom fields.
After completing the test migration of Jira, we agreed with the client on post-migration adjustments in the target environment. For example, we set permission schemes so that migrated projects were read-only.
Once the results of the test migration were approved – where the client had full access to the test environment and could verify everything – we proceeded with the production Jira migration.
The production migration was completed without major complications thanks to the migration plan created based on the test migration. Even though time was tight towards the end, we finished everything, and the client did not lose any data.
Result: Successful migration and preservation of critical data
Thanks to a systematic approach and our experience with Jira migrations, we promptly supplemented the missing data and ensured its continuity in the new system. The client was able to continue working without losing any critical information.
If you are planning a Jira migration or need assistance transferring data between systems, please get in touch with us. We’ll be happy to help you with an efficient and secure solution!
Our Atlassian Solutions