---
title: "[Xray] Migration from Server/DC to the Cloud Xray issues types MUST be equal in both instances"
canonical: "https://docs.getxray.app/space/ProductKB/141885510/%5BXray%5D%20Migration%20from%20Server%2FDC%20to%20the%20Cloud%20Xray%20issues%20types%20MUST%20be%20equal%20in%20both%20instances"
format: markdown
---
## **The reason:**

When migrating from Jira Server/Data Center to Xray Cloud using the Jira Cloud Migration Assistant (JCMA), it's essential to ensure that all Xray issue types are identical in both instances before starting the migration,** unless you're using the "Migrate all Data at Once" option.**

If the Xray issue types are not aligned between Server/DC and Cloud, Xray cannot correctly map them, causing the migration to fail. Therefore, it's crucial to double-check the issue types in both instances before proceeding.

## **Important Notice: Matching Issue Type Names**  


The most common mismatch occurs with the Precondition/Pre-Condition issue type, as it differs between Jira/Xray Cloud.  To avoid migration issues, rename it in Jira Data Center as follows:

- Pre-Condition → Precondition

It's okay if you use different names for the Xray issue types. However, the names *must match in both instances*.

- For example:  
 If an Xray issue type is called **"Xray Type"** in Jira Data Center, it must also be named **"Xray Type"** in Jira Cloud.

## **How to check it:**

### **In Jira Data Center/Server:**

1. Go to **Jira Admin > Issues > Issue Types**.
2. Look for the following Xray issue types:
  - Test
  - Test Execution
  - Test Set
  - Test Plan
  - Precondition *(ensure it is not listed as Pre-Condition)*
  - Sub-Test Execution

### **In Jira Cloud:**

1. Go to **Jira Admin > Issues > Issue Types**.
2. Search for "Xray" and confirm the presence of these issue types:
  - Test
  - Test Execution
  - Test Set
  - Test Plan
  - Precondition
  - Sub-Test Execution

During a migration from **Xray Server/Data Center** to **Cloud**, failures can occur if the **Xray issue types** are not identical in both instances.

> ❌ Any mismatch in names or missing issue types will prevent migration from completing successfully.

### Solutions

**Option 1: Align Issue Types and Re-run Migration:**

1. Delete all migrated projects in **Jira Cloud**.
2. Rename Xray issue types so they match exactly in both instances.
3. In **Jira Data Center**, create a **new migration plan**, add the projects, and run the migration.

**Option 2: Remap via Xray Support:**

1. Contact the **Xray Support team** to remap Cloud issue types to match the Server/Data Center types.
2. Re-run the **Xray migration** without creating a new plan or re-running the Jira migration.

> ⚠️ Note: Option 2 does **not work in all cases**. Each situation must be reviewed individually.