Before migrating from Xray Server/DC to Cloud be sure you've completed the steps recommended at "Steps to a successful migration": 

• Have a valid License for Xray
• 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. 

Learn more at "Steps to a successful migration".

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. If the storage offered by Xray Standard is not enough, you might consider upgrading to Xray Enterprise.

Due to the way the "Migrate all data at once" option migration process 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, to ensure a smooth migration process, 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:

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.