---
title: "[Xray] Can I continue to create tests, test plans, test executions or any other Xray entity  while doing a migration from Server/DC to Cloud?"
canonical: "https://docs.getxray.app/space/ProductKB/46269187/%5BXray%5D%20Can%20I%20continue%20to%20create%20tests%2C%20test%20plans%2C%20test%20executions%20or%20any%20other%20Xray%20entity%C2%A0%20while%20doing%20a%20migration%20from%20Server%2FDC%20to%20Cloud%3F"
format: markdown
---
##   
When migrating from **Xray Server** to **Xray Cloud**, it’s important to understand:

- **Migration only moves existing data: **Test Plans, Test Cases, Test Sets, and Test Executions are transferred as-is. The migration process **does not create or modify data** in the Server or Cloud.
- **No new data should be created during migration.: **Any changes, edits, or new entities created in the Server/Data Center **during the migration** may **not be included** and can potentially cause the migration to fail.
- **Critical threshold: **If more than **100 modifications** happen during the migration, the migration will fail.

### Problem:

**Migration failures caused by modifications during the migration, such as:**

- New issues created
- Existing issues edited or deleted

### Diagnosis:

Check internally with all teams working on the projects being migrated. Ensure that **no new data is created** and **no existing data is changed** during the migration.

### Solution Options:

**Option 1:**

1. Delete the already migrated projects on the Cloud.
2. Create a **new migration plan**, adding the projects for migration again.

**Option 2:**

1. Create a **new migration plan** including only the Jira projects (exclude Xray).
2. Access the failed migration plan and re-run the Xray migration using the **Re-run feature in JCMA** on the original plan.

> ⚠️ Note: The second option may **not work in all cases**. Each situation needs individual review. Contact the **Xray Support team** for guidance if needed

  
  
  



---

See more **Frequently Asked Question about Migration from Server to Cloud: **

> Macro (contentbylabel)