Migration from xray to xray cloud

[Monika Lykke Borges]

Hi - i'm migration from xray server to xray cloud. In xray servide test execution is names Test Execution but in the cloud it is calles Xray Test excution. That means that we can't migrate this field. How to name it so i can migrate. 

[Łukasz Modzelewski _Lumo_]

Hi @Monika Lykke Borges , welcome the Atlassian Community!

From the docs it looks like this might be an extra step for migrations:

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

Make sure to double check and follow the migration guide: https://docs.getxray.app/display/XRAY/Jira+Cloud+Migration+Guide

In case of any problems I recommend reaching out directly to Xray Support

[Francisco Fonseca _Xray_]

Hi @Monika Lykke Borges ,

Welcome to the Community!

I'd like to invite you to open a migration ticket with us so we can help you throughout the journey: https://jira.getxray.app/servicedesk/customer/portal/2/create/37

Additionally, as @Łukasz Modzelewski _Lumo_ pointed out, we have a support article that can assist you with this. Should you have chosen "Migrate all data at once" you should follow the steps highlighted.

Article for reference: Jira Cloud Migration Guide 

Should you need any assistance just reach out to our support! They'll be happy to help.

Best, Francisco.

[Sahir Maharaj]

Hello @Monika Lykke Borges

When migrating from Xray Server to Xray Cloud, discrepancies in naming conventions (e.g., "Test Execution" on Server vs. "Xray Test Execution" on Cloud) can cause issues.

To address this, map the fields explicitly during migration or rename the fields in your server instance to match the Cloud naming structure before initiating the migration.

If manual adjustments aren’t feasible, I recommend to consider using a migration tool or API to handle the field mappings.