---
title: "CMJ Cloud Migration Error: \"Create of service desk failed\""
canonical: "https://support.appfire.com/space/SUPPORT/3461185556/CMJ%20Cloud%20Migration%20Error%3A%20%22Create%20of%20service%20desk%20failed%22"
format: markdown
---
## Summary

This article addresses a specific failure during Jira Cloud-to-Cloud migrations where the app fails to create a Jira Service Management (JSM) service desk in the target instance, typically due to insufficient administrative permissions or mismatched permission schemes.

## Use Case

A user attempts to migrate Jira Service Management (JSM) projects between two Jira Cloud sites using Configuration Manager for Jira (CMJ) and encounters a deployment failure.

### Problem

The migration fails with the following error message in the deployment logs:  
`Cause of failure: Create of service desk '' with source id/key '3' failed.`

### Cause

This error is generally caused by:

- Insufficient Permissions: The user performing the migration lacks the necessary administrative rights on the target Jira instance to create service desks.
- Permission Scheme Mismatches: Discrepancies between the source and target permission schemes or missing roles that prevent CMJ from successfully configuring the new project.

### Solution

To resolve this issue, ensure that both the user and the CMJ app have the appropriate access levels and that the environment configurations match.

#### Step 1: Verify Administrative Permissions

The user performing the migration must have the following permissions in the target instance:

- **Jira Administrator**
- **Jira Service Management Administrator**

#### Step 2: Verify Project Permission Schemes

Mismatched roles or restricted permission schemes can block the creation of the service desk.

1. Navigate to Jira Settings > Issues > Permission Schemes on both the source and target instances.
2. Compare the schemes to ensure:
  - The same Roles exist in both environments.
  - The CMJ app (or the user performing the migration) has the "Administer Projects" permission within the scheme.
3. If roles or permissions differ, manually adjust the target instance to match the source before re-running the deployment.