---
title: "[Xray] Server/DC to Cloud Migrations (JCMA) – Xray migration got failed due to Issue Security Schemes"
canonical: "https://docs.getxray.app/space/ProductKB/140574916/%5BXray%5D%20Server%2FDC%20to%20Cloud%20Migrations%20(JCMA)%20%E2%80%93%20Xray%20migration%20got%20failed%20due%20to%20Issue%20Security%20Schemes"
format: markdown
---
This guide explains why certain Jira Server/Data Center to Cloud migrations may fail due to issues with security schemes and how to resolve the issue.

### Cause of Migration Failure

If security schemes are applied to issues during a Jira migration, they can cause the migration to fail.

- **Xray 7.7.0 and later**: Migrations can proceed even if up to **100 issues are missing**, preventing unnecessary failures.
- **Earlier Xray versions**: The migration fails if even **one issue is missing** due to security restrictions.

However, the migration will fail if:

- More than **100 missing issues** exist. ( Missing issues can be the ones that have Issue Security Scheme or the ones that were created during the migration)

Issue security schemes must be removed from projects before the migration to **avoid migration failures.** To ensure all issues are accessible, set them to "Any logged-in user."

### Error Message

When checking the migration logs in Xray Cloud, the Support team will encounter an error similar to the following:

```
Error: Error updating Test Execution 10652 in Jira: Issue not found in Jira
Error updating Test Execution 11141 in Jira: Issue not found in Jira
Error updating Test Execution 11163 in Jira: Issue not found in Jira
Error updating Test Execution 10771 in Jira: Issue not found in Jira
```

If too many missing issues are detected, the migration process stops:

```
Exceeded skip migration errors limit (current: 100.5, limit: 100)
```

To maintain data integrity, Xray imposes a limit on the number of missing issues. Once this threshold is exceeded, the migration will fail.

### Diagnosis

1. In Jira Data Center, navigate to:  
`Jira Administration → Issues → Issue Security Schemes`
2. Check whether the projects included in migration have Issue Security Schemes.
3. Verify if **“Any logged-in user”** permission is set.

> ℹ️ Missing this permission prevents migration of the affected projects.

### Solutions

**Option 1 – Quick Fix on Cloud:**

1. Add **“Any logged-in user”** to the Issue Security Schemes **directly on Cloud**.
2. Re-run the app migration from JCMA.

> ⚠️ For future migrations, add this permission t**o the Data Center** before running the Jira migration.

**Option 2 – Adjust Security Before Migration:**

1. Remove Issue Security Schemes from projects **before migrating**, or set them to **“Any logged-in user”**.
2. Create a **new migration plan**, adding only Jira projects (exclude Xray).
3. Access the failed migration plan, then re-run **Xray migration** using the **Re-run feature in JCMA**.

> ⚠️ The Xray Re-run option works reliably for this type of failure.

For guidance on modifying issue security schemes, refer to Atlassian’s documentation: [Configuring issue-level security](https://confluence.atlassian.com/adminjiraserver/configuring-issue-level-security-938847117.html)