Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note
titleRequired steps to migrate

Before migrating from Xray Server/DC to Cloud be sure you've completed the steps recommended:

  • Have a valid License for Xray
  • Enable Sub-Task in Jira Cloud
  • Issue Types names are the same both on Server and Cloud
  • Requirement ↔ Test Link must match both on Server and Cloud

  • Review Issue Security applied to Xray Issues.
  • Xray Custom Fields must be visible on Test Execution Issue Screens Scheme
  • Run the pre-flight checks

Ready for a Checklist? Make Sure you do not forget any step and download our Xray Migration from Server to Cloud Checklist. 

Button Hyperlink
titleDownload Checklist
typestandard
urlhttps://9030804.fs1.hubspotusercontent-na1.net/hubfs/9030804/MigrationChecklist-V2.pdf

Learn more at Migration Preparation.

Also make sure you are aware of the differences between Xray Server and Xray Cloud.

Be also sure, that if you select the Xray Cloud Standard you are aware of the storage limit and API rate Limit. If the storage and api rate limit, offered by Xray Standard is not enough, you might consider upgrading to Xray Enterprise.

Migration Assessment

As in any other other move, you first need to make sure you run a comprehensive and complete assessment. 

  • Ensure that the Xray Cloud is properly installed. Before proceeding, make sure that Xray Cloud is correctly installed in your Jira Cloud instance. Please access Jira Cloud Admin, Apps, and Manage your Apps to check. On the left-hand side, look for Health Check and check if the Xray is working as expected. It should be like the example below:
    Health checkImage Added

    Please note
    : If your Jira Cloud instance has no projects, the Health Check might show that some Xray custom fields are missing. This is expected behavior. These fields will be automatically created once a project is added or during a data migration.
  • Enable Sub-Task in Jira Cloud
  • Issue Types names are the same both on Server and Cloud
  • Requirement ↔ Test Link must match both on Server and Cloud

  • Review Issue Security applied to Xray Issues.
  • Xray Custom Fields must be visible on Test Execution Issue Screens Scheme
  • Run the pre-flight checks

Ready for a Checklist? Make Sure you do not forget any step and download our Xray Migration from Server to Cloud Checklist. 

Button Hyperlink
titleDownload Checklist
typestandard
urlhttps://9030804.fs1.hubspotusercontent-na1.net/hubfs/9030804/MigrationChecklist-V2.pdf

Learn more at Migration Preparation.

Also make sure you are aware of the differences between Xray Server and Xray Cloud.

Be also sure, that if you select the Xray Cloud Standard you are aware of the storage limit and API rate Limit. If the storage and api rate limit, offered by Xray Standard is not enough, you might consider upgrading to Xray Enterprise.


Migration Assessment

As in any other other move, you first need to make sure you run a comprehensive and complete assessment. 

Avoid assessing and planning data migration too late on your migration journey. Xray is seemly integrated with Jira, so it's migration can be as Avoid assessing and planning data migration too late on your migration journey. Xray is seemly integrated with Jira, so it's migration can be as complex as the Jira itself. 

...

Info

Please note that Atlassian has discontinued the Migrate All Data At Once option. Please see: Discontinuing migrate-all-data-at-once. If you follow this migration and use an old version from Xray, please notice that you will need to follow a different process. To learn more, please check the edit issue type names.

Migrating Xray Data through Jira Cloud Migration Assistant

Any Xray related projects that are somehow connected, must be migrated together within the same migration, otherwise, any Xray link 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.

from Xray, please notice that you will need to follow a different process. To learn more, please check the edit issue type names.


Migrating Xray Data through Jira Cloud Migration Assistant

Any Xray related projects that are somehow connected, must be migrated together within the same migration, otherwise, any Xray link 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.

Warning

Avoid creating, modifying, or deleting Issues related to Xray or connected projects during migration, as this can cause failures if more than 100 Issues are missing. Disable all automation and third-party app modifications to prevent exceeding this limit. Ensure all Jira projects are fully migrated; otherwise, Xray won’t find the expected Issues. Also, remove issue security schemes or set them to "Any logged-in user" before migration to avoid permission-related failures

Warning

Avoid data change during the migration, otherwise the migration might fail.

Understand and Communicate the Limitations

...

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.Automated Steps Library will be migrated but you need to perform a re-index. Check more details on [Xray] Will the automated Automated Step Library be migrated to the Cloud when performing a migration from Server/DC to the Cloud using JCMA?

Cucumber settings

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

...

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.

Project Level Settings

The project level settings get transferred when migrating from Xray Data Center to Xray Cloud (except for Default Column Layouts settings).

Info

If you want to migrate archived projects, you first need to unarchived them. 

Follow this article to understand how to check which projects are archived: [Xray] How to get all Archived Projects?

...

There are no more errors, meaning that the projects can be migrated together safely. We can now go back to the Jira Migration Assistant and plan our migration with both projects.

...

Preloading Xray Data Before Migration

Atlassian provides a feature

...

 that allows you to migrate Jira attachments in advance, saving you

...

For more details about the steps required to preload the Xray attachments, please check these steps:

...

time on the migration day.

It is essential to have Xray version 7.8.2

...

or the latest installed, as this version includes the attachments feature. Additionally, you'll need to ensure

...

that JCMA (Jira Cloud Migration Assistant) is updated to version 1.

...

12.

...

16 or higher. Below is a step-by-step guide

...

on how the preload process works:

1. Install Xray version 7.8.2

...

or the latest

This version is

...

required as it introduces the attachments functionality.

...

2. Ensure JCMA version 1.

...

com.atlassian.jira.migration.app.data.preload.feature

...

12.16 or above is installed

Starting from JCMA 1.12.16, no feature flags are required. A new option, "Preloadable app data only," is now available on the projects screen.

  • If this option does not appear, customers can contact Atlassian to enable the feature flag for them.
  • For JCMA versions 1.12.13 to 1.12.15, customers must reach out to Atlassian to have the feature flag enabled manually.

3. Additional References

For more details on preloading app data before migration, refer to Atlassian's official documentation.

By following these steps, the preload process should work as expected, ensuring a smoother migration with minimal downtime.

Info

Go here to see more about Xray attachments.

...

If you want to know how to start the migration please go to Atlassian Documentation.

Migrate All Users

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.

...