--- title: "Copy of Jira Cloud Migration Guide" canonical: "https://docs.getxray.app/space/XRAY/301665733/Copy%20of%20Jira%20Cloud%20Migration%20Guide" format: markdown --- This prchivedage describes the migration path you can follow to migrate Xray data from Jira Server/Data Center **to Jira Cloud**. If you have any questions about which approach best suits your organization, please contact our support team directly. > Macro (widget)
Table of Contents > Macro (toc)
> ⚠️ ### Required steps to migrate > ⚠️ > ⚠️ Before migrating from Xray Server/DC to Cloud, ensure you've completed the steps recommended at ["Steps to a successful migration"](#Stepstoasuccessfulmigration):  > ⚠️ > ⚠️ - 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 steps and download our [Xray Migration from Server to Cloud Checklist.](https://9030804.fs1.hubspotusercontent-na1.net/hubfs/9030804/MigrationChecklist-V2.pdf)  > ⚠️ > ⚠️ > Macro (auibutton) > ⚠️ > ⚠️ Learn more at ["Steps to a successful migration"](#Stepstoasuccessfulmigration). > ⚠️ > ⚠️ Also, make sure you are aware of the differences between [Xray Server and Xray Cloud](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301697915). > ⚠️ > ⚠️ Be also sure, that if you select the Xray Cloud Standard you are [aware of the storage limit](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565773) and [API rate Limit](https://getxraydocs.atlassian.net/wiki/display/ProductKB/%5BXray+Cloud%5D+Rest+API+Limit). If the storage and API rate limit, offered by Xray Standard is not enough, you might consider upgrading to [Xray Enterprise.](https://www.getxray.app/xray-enterprise) # Migration Assessment As in any 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 seemingly integrated with Jira, so its migration can be as complex as Jira itself.  In the assessment follow the following steps:  1. Determine current Xray Version. 2. Determine data size. 3. Evaluate differences between Xray Cloud & Xray Server/DC. 4. Evaluate the Xray offering - Standard or Enterprise. ## Xray Version In order to use Jira Cloud Migration Assistant to [migrate you need to have Xray version 7.7.0 or higher](https://getxraydocs.atlassian.net/wiki/spaces/ProductKB/pages/46269308).  In case you have a lower version, please upgrade to a more recent version. ## Data Size Assessment Knowing your luggage weight will have a big impact on the effort and time to migrate. So the first step is to understand exactly what will be the data size. **Guardrails ** | **Object** | **Mapping to App Assessments Data** | **Guardrail** | **Risk** | **Recommendations** | | --- | --- | --- | --- | --- | | `Test runs` | `TOTAL_TEST_RUNS` | `<1M` | Low | No actions needed | | `TOTAL_TEST_RUNS` | `1M<2M` | Medium | [Cleanup data](https://getxraydocs.atlassian.net/wiki/spaces/ProductKB/pages/46269630) to decrease data size or accept risk | | `TOTAL_TEST_RUNS` | `>2M` | High | [Contact Support](https://jira.getxray.app/servicedesk/customer/portal/2/create/37) | | `Xray Attachment size` | `TOTAL_ATTACHMENT_SIZE` | `<100GB` | Low | No actions needed | | `TOTAL_ATTACHMENT_SIZE` | `>100GB` | Medium | [Cleanup data](https://getxraydocs.atlassian.net/wiki/spaces/ProductKB/pages/46269630) to decrease data size or accept risk | | `TOTAL_ATTACHMENT_SIZE` | `>1.5TB` | High | [Contact Support](https://jira.getxray.app/servicedesk/customer/portal/2/create/37) | ### How to Determine Test Runs & Attachments Data size The volume of Test Runs and Attachments can have huge contribution to the time it takes to migrate and increases also the complexity.  Before committing to a timeline to migrate, please make a serious assessment of your data size.  Check the following articles to:  - [How to determine the Test Runs size?](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUDDRAFT/pages/44832566) (couldn't find the new link) - [How to determine the Attachments in Test Runs & Test Steps](https://getxraydocs.atlassian.net/wiki/spaces/ProductKB/pages/46269215) ## Server/DC vs Cloud - Product Comparison If you are looking to migrate from Jira Server/DC to Jira Cloud, you need to consider the differences between Xray Server/DC and Xray Cloud. These differences might affect how your users work and interact with Xray. The ideas, goals, and major features are the same. However, while there is great similarity between them, there are a few subtle differences between the two versions. This is mainly due to: - **Jira architecture** - The way apps work in Server and Cloud is completely different. In Server, apps can integrate with many aspects of Jira, while on Cloud, there are a lot of integration points missing, e.g. JQL functions, Project Templates, calculated fields at agile boards (like requirement status), etc. - **Product Age** - Xray Cloud is a newer product. Therefore, some of the features are not yet present (e.g. Automated Step Library, Historic Test Coverage report), although we plan to include these features in future releases. Also, we took the opportunity to improve some features (e.g. Project Level Settings). For a full comparison between the Server/DC and Cloud versions of Xray, please refer to [Xray Server and Xray Cloud](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301697915). ## Xray Standard + Xray Enterprise When moving to Cloud, confirm which apps you will need to fulfill your needs.  We recommend you compare [between the offers](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301697915) to select the best option for your use case. Be also sure, that if you select the Xray Cloud Standard you are [aware of the storage limit](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUDDRAFT/pages/44838299) and [API rate Limit](https://getxraydocs.atlassian.net/wiki/spaces/ProductKB/pages/46268656). Learn more about the differences at [https://www.getxray.app/xray-enterprise](https://www.getxray.app/xray-enterprise) or [contact our sales team](https://www.getxray.app/contact-us) to get more information. # Migration Planning Now that you've completed your assessment and we have a clear idea of what you are moving to Cloud and what expects you, you can start planning your migration. To plan the migration follow the steps:  1. Select the migration strategy - we recommend using Jira Cloud Migration Assistant. 2. Communicate and understand the limitations. ## Select the Migration Strategy  ### Jira Cloud Migration Assistant Atlassian provides the [Jira Cloud Migration Assistant](https://confluence.atlassian.com/cloud/use-the-jira-cloud-migration-assistant-to-migrate-from-server-to-cloud-993925215.html) (JCMA) to help users transition from an on-premise Jira instance (Server or Data Center) to Jira Cloud. Thanks to our integration with the JCMA, migrating from Xray Server/Data Center to the Cloud is straightforward and user-friendly. ### Migration Options The JCMA app provides two approaches for migrating to the Cloud: 1. **Choose What to Migrate (Recommended): **this option allows you to select specific projects, issue types, or configurations to migrate. It offers flexibility by enabling a phased migration and reduces the risk of transferring unnecessary or outdated data. 2. **Migrate All Data At Once (Not Recommended)** This option migrates all data from your Server/Data Center instance to the Cloud in a single operation. While it may seem efficient, it’s important to note the following considerations: - **Data Volume**: large datasets can prolong migration times and potentially lead to errors or interruptions during the transfer. - **Increased Complexity**: Migrating everything at once may bring over unnecessary data, such as outdated configurations, unused custom fields, or inactive projects, which could clutter your Cloud environment. - **No Phased Testing**: Unlike selective migration, this approach doesn’t allow for phased validation, making it harder to troubleshoot issues. For these reasons, **we recommend using the *****Choose What to Migrate*** option for most scenarios. However, if your dataset is relatively small or you’re confident in its consistency, the *Migrate All Data At Once* can be a viable option. > ℹ️ Please note that Atlassian has discontinued the *Migrate All Data At Once* option. Please see: *[Discontinuing migrate-all-data-at-once.](https://community.atlassian.com/t5/Atlassian-Migration-Program/Discontinuing-migrate-all-data-at-once-and-we-re-going-all-in-on/ba-p/2621674?utm_campaign=immediate_general_article&utm_content=topic&utm_medium=email&utm_source=atlcomm)* 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](#JiraCloudMigrationGuide-JiraCloudMigrationGuide-EditIssueTypeNames). **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. > ❌ 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. ## Understanding and Communicating the Limitations #### Issue History and Test Run Activity Due to the textual nature of the data in the activity logs, the entries are mostly copied directly. 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 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?](https://docs.getxray.app/pages/viewpage.action?pageId=182944188) #### Cucumber Settings Will not be migrated to the Cloud ([Miscellaneous](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301407212) settings section). #### Gadget Configuration Configuration of Xray gadgets will not be migrated. **Xray Notifications** Xray Notifications (events) will not be migrated. Xray Cloud does not provide this feature. #### Document Generator Templates migrated from the Server must be revised once there are some differences between the Server and Cloud versions. #### Archived Issues Xray data belonging to the archived issues are not migrated. 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](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301672631) settings). > ℹ️ 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?](https://docs.getxray.app/pages/viewpage.action?pageId=178749515) (couldn't find the link) # Migration Preparation Before hitting "Migrate" you need to perform some steps to avoid issues and unsuccessful migrations. ### Pre-Migration Checks - Steps for a Successful Migration > ❌ Pre-Migration Checks are mandatory for a successful migration. Before initiating the migration, it's crucial to perform the following checks to ensure a smooth process: - Confirm you have a valid License for Xray. - Jira migration stage must be successful. - Confirm sub-tasks are enabled on Jira Cloud. - Confirm Issue Types names are the same both on Server and Cloud. - Confirm 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](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/160137357) Issue Screens Scheme. - **Run a Preflight Check**: Confirm project linkages, issue linking, issue security schemes, and other dependencies are properly configured. - **Pre-load attachments:** if you want to save time on the migration day, you can pre-load attachments. These preparatory steps simplify the migration process and minimize potential issues. For more detailed guidance, refer to: - [The Comprehensive Cloud migration guide](https://www.atlassian.com/migration/plan/cloud-guide#introduction). - [How to use the JCMA to migrate](https://support.atlassian.com/migration/docs/use-the-jira-cloud-migration-assistant-to-migrate/). > Macro (rw-ui-steps-macro) > > > Macro (rw-step) > > #### Licensing > > > 📝 A valid Xray app license is required to migrate Xray data, otherwise, Xray data won't be migrated to the cloud. > > > Macro (rw-step) > > #### Jira migration stage must be successful > > Before the Xray migration stage is executed, all issues and Jira entities are migrated by Atlassian's JCMA. To guarantee that Xray migration is successful, all these Jira entities must be 100% migrated, without warnings. If you encounter problems in Jira's migration stage, please contact the [Atlassian support team](https://support.atlassian.com/). > > > ℹ️ Atlassian provides a feature that allows you to migrate Jira attachments in advance, saving you time on the migration day. Go above to see more. > > > Macro (rw-step) > > #### Confirm Sub-Tasks are enabled in Jira Cloud > > Xray makes use of Sub-Tasks for Sub-Test Executions, so you need to make sure that Sub-Tasks are enabled in your Jira Cloud to accommodate the issue type Sub-Test Execution.  > > To learn more about enabling sub-tasks in Jira Cloud check the [Atlassian Documentation.](https://support.atlassian.com/jira-cloud-administration/docs/configure-sub-tasks/) > > > Macro (rw-step) > > #### 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/](https://support.atlassian.com/jira-cloud-administration/docs/add-edit-and-delete-an-issue-type/) > > > ⚠️ This procedure is only applicable when using the option "Migrate all data at once" from JCMA. If the migration is carried out using the "Choose what to migrate" option (i.e., choosing the specific projects to migrate), the extra steps described below should be disregarded. > > > 📝 Due to the way the "Migrate all data at once" option works on JCMA, when choosing this option a few additional steps must be taken to ensure compatibility with the Xray migration. So if you are using the "Migrate all data at once" option, please follow the steps below: > > 📝 > > 📝 - On the Server side, rename all Xray issue types like this (avoid spaces before and after): > > 📝 - Pre-Condition → Xray Precondition > > 📝 - Test → Xray Test > > 📝 - Test Execution → Xray Test Execution > > 📝 - Test Plan → Xray Test Plan > > 📝 - Test Set → Xray Test Set > > 📝 - Sub Test Execution → Xray Sub Test Execution > > 📝 > > 📝 > > 📝 - Still on the Server side, and only after the Xray types are renamed, create 6 dummy issue types like the list below: > > 📝 - Precondition. > > 📝 - Test. > > 📝 - Test Execution. > > 📝 - Test Plan. > > 📝 - Test Set. > > 📝 - Sub Test Execution. > > 📝 > > 📝 After carrying out the previous operations, the Issue Types on the Server should look like this: > > 📝 > > 📝 ![Figure 1 - Issue Types](media://8c7ab66d-b7ef-4dab-9a05-919243bc12f5) > > 📝 > > 📝 After the migration is completed, the dummy Issue Types created with this purpose can be deleted, and the Xray Issue Types can be renamed back to their original names. > > > ⚠️ Sometimes when migrating with the "Migrate all data at once" option, the Issue Type avatars can be broken on the Cloud side after the migration (i.e., the migration is successful but the icons of the Xray issue types are missing). If that happens, the icons can be downloaded and updated manually on the Cloud following the procedure described [here](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565860). > > > Macro (rw-step) > > #### Edit Requirement ↔ Test Link > > The Issue Link used for Requirement Coverage is slightly different between Xray Cloud and Xray Server/DC. To ensure that Xray Cloud will recognize these links, the Issue Link Type must be edited on Server/DC to match the link used by Xray Cloud: > > - Name: Test > - Outward Description: tests > - Inward Description: is tested by > > This step must be done manually prior to migrating since the Issue Links are migrated by Jira instead of Xray. > > The configuration can be found in `MY_JIRA_SERVER_URL/secure/admin/ViewLinkTypes!default.jspa` > > > Macro (rw-step) > > #### Some Xray custom fields must be visible > > Make sure that the following Xray-created custom fields are added to the Test Execution Issue screen and are visible to all users in all projects that you are migrating. > > - [Begin Date](https://getxraydocs.atlassian.net/wiki/spaces/XRAY740/pages/48432493). > - [End Date](https://getxraydocs.atlassian.net/wiki/spaces/XRAY740/pages/48432493). > - [Revision](https://getxraydocs.atlassian.net/wiki/spaces/XRAY740/pages/48432493). > > > Macro (rw-step) > > #### Check Issue Security Levels > > The Issue Security Scheme may restrict Xray's access to issues during the migration. > > If you are using Security Levels for Xray Issues  ( Test, Test Set, Test Plan, Test Execution, Sub-Test Execution and Pre-Condition)  - you'll have to temporarily add "Any Logged in user" to all the security levels used by Xray Issue Types or remove all the Security Schemes/Levels from those Issues. ### Running 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 contains 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 missing links in the Cloud instance. This check should be done before any migration begins. 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 see a table with all the instance projects listed, select all the projects for your migration and then press Validate. If there are no errors, you can 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 issues. ![Figure 2 - Issue Types]() Example: Project Xray Test Project was selected for migration. The preflight checks found that there is a link to another project that is not part of the migration (Xray Dev Test). ![Figure 3 - Preflight Checks]() We'll select the missing projects for the preflight checks and validate. ![Figure 4 - Project List - no errors]() 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](https://support.atlassian.com/migration/docs/migrate-jira-attachments-in-advance/) that allows you to migrate Jira attachments in advance, saving you 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.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](https://support.atlassian.com/migration/docs/preload-app-data-before-migration/). By following these steps, the preload process should work as expected, ensuring a smoother migration with minimal downtime. > ℹ️ Go [here](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301505508) to see more about Xray attachments. # The Migration Process Now that you've assessed, planned, and prepared the migration, you are ready to go to Jira Cloud Migration Assistant and start the migration. If you want to know how to start the migration please go to [Atlassian Documentation.](https://getxraydocs.atlassian.net/wiki/display/XRAY/Jira+Cloud+Migration+Guide) ### Migrating 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. ![Figure 5 - JMCA Users Migration]() The Xray migration starts right after the Jira migration. While Xray is migrating projects, the Xray app screens/actions will be disabled until the end of the migration. Those screens will show a warning and an action to allow the user to see the current progress of the migration. This progress shows details about what is being done. ![Figure 6 - Xray Blocked message in Tests]() Xray Cloud also provides a page in the app administration section with all the migration plans in progress and done. Here the Jira administrator could see the history of migration and the ongoing migration plans. Learn more about it [here](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUDDRAFT/pages/44827873). ![Figure 7 - Migration Status]() # Unsuccessful Migrations We are continuously working to improve and reduce the effort of migrating Xray to Cloud. Nevertheless, we recognize that issues may affect your migration that will cause a failure.  Our Migration Effort Score is rated by our customers as "Normal" and a big percentage of customers do not face any blockers. The success depends on understanding and following all the steps needed and the data size and complexity. If the Xray migration is not successful during the Jira cloud migration plan, we highly recommend trying it again. Before trying again, make sure the cloud project is removed. If the issue persists, please contact our [support](https://getxraydocs.atlassian.net/wiki/spaces/XRAY610/pages/50431830) to get help. **Most Common Reasons for Unsuccessful Migration** | Problem | Solution | Reference | | --- | --- | --- | | ![image-20250212-144814.png](media://cdc30b41-f73d-4bea-bbe8-ccf5eb1f7b0f)
The Xray version is not compatible with Jira Cloud Migration Assistant | Upgrade Xray Version | - [[Xray] Do I need to upgrade Xray to migrate to the Cloud? Which version do I need to upgrade?](https://getxraydocs.atlassian.net/wiki/spaces/ProductKB/pages/46268631) - [[Xray] Server/DC to Cloud Migrations (JCMA) – Advantages of Updating the Xray App Prior to Migration](https://getxraydocs.atlassian.net/wiki/spaces/ProductKB/pages/46269308) | | ![image-20250212-144814.png](media://cdc30b41-f73d-4bea-bbe8-ccf5eb1f7b0f)
During the migration, there was a data change. | Re-run Migration and make sure there is no data change | [[Xray] Can I continue to create tests, test plans, test executions or any other Xray entity while doing a migration from Server to Cloud?](https://getxraydocs.atlassian.net/wiki/spaces/ProductKB/pages/46269187) | | ![image-20250212-144814.png](media://cdc30b41-f73d-4bea-bbe8-ccf5eb1f7b0f)
Migration failed due to Archived projects | Unarchived the projects and migrated again | [[Xray] Server/DC to Cloud Migrations (JCMA) – Xray migration got failed due to archived projects.](http://docs.getxray.app/pages/viewpage.action?pageId=178749529) (couldn’t find the link) | | ![image-20250212-144814.png](media://cdc30b41-f73d-4bea-bbe8-ccf5eb1f7b0f)
Migration failed due to Issue Security Scheme | Remove issue security schemes from projects before migration, **or **set issue security to "Any logged-in user."** **and then run the migration again | ⁠⁠[[Xray] Server/DC to Cloud Migrations (JCMA) – Xray migration failed due to issues with Security Schemes](https://getxraydocs.atlassian.net/wiki/spaces/ProductKB/pages/46269282) (couldn’t find the link) | | ![image-20250212-144814.png](media://cdc30b41-f73d-4bea-bbe8-ccf5eb1f7b0f)
Missing Permissions | Update the Xray app to** 7.2.0 and later,** or grant th**e "Browse Projects" and "Edit Issues" permissions to "Any logged-in user”** | [[Xray] Can a migration from Server/DC to Cloud fail due to a missing atlassian-addons-project-access on the security level?](https://getxraydocs.atlassian.net/wiki/spaces/ProductKB/pages/46269175) | | ![image-20250212-144814.png](media://cdc30b41-f73d-4bea-bbe8-ccf5eb1f7b0f)
Migration failed due to Missing Projects | Re-run the Migration and include all the projects that share the dependency | [[Xray] Can I migrate only certain projects from Server/DC to Xray Cloud?](https://getxraydocs.atlassian.net/wiki/spaces/ProductKB/pages/46268619) | | ![image-20250212-144814.png](media://cdc30b41-f73d-4bea-bbe8-ccf5eb1f7b0f)
Migration failed due to Xray Issue Types not matching | Re-run the Migration. But, before please check and rename all the Xray issues to match in both instances before the migration | [Xray] Migration from Server/DC to the Cloud Xray issues types MUST be equal in both instances | | ⚠  Xray Sub Test Execution is not installed on the Xray Cloud | Before the migration, please ensure that the Jira Sub-task is enabled, and then re-install Xray via the Health Check on the Jira Cloud | Xray Cloud Health Check shows that the Xray Sub Test Execution issue type is not installed | > ℹ️ To learn more about migration from Xray Server to Xray Cloud you might want to take our dedicated course available for free at Xray Academy: [Migration from Xray Server to Xray Cloud](https://academy.getxray.app/trainer/course/id:143) (Figure 7) > ℹ️ > ℹ️ ![Figure 7 - Xray Academy]()