Troubleshoot migration with Jira Cloud Migration Assistant

A green tick means that the check has passed.

You can proceed to the next step in your migration.

A yellow warning means that you can continue, but you need to be aware of a potential issue.

You can expand the warning messages to view details and relevant links.

A red error means that you need to resolve the error before you can run your migration.

You can expand the error messages to view details and relevant links.

A grey error means that the check wasn’t complete due to an unexpected error.

You can refresh the checks to try again or contact support if you continue to get this message.

We are currently updating the migration service

The Jira Cloud Migration Assistant authentication token might have expired.

Learn how to renew your authentication token

We couldn’t check for users count limit

The Jira Cloud Migration Assistant authentication token might have expired.

Learn how to renew your authentication token

We couldn’t check for projects in your cloud site

The Jira Cloud Migration Assistant authentication token might have expired.

Learn how to renew your authentication token

We couldn’t check for projects in your cloud site

It’s possible that your cloud site is unavailable for migration. Here are the reasons and fixes:

Reason 1: Your sandbox has been deleted.

Fix:

1. Check if your sandbox is deleted:

   1. Go to admin.atlassian.com, and then select your organization if you have more than one.

   2. Select Products > Sandbox.

2. If deleted, contact support for further assistance.

Reason 2: Your cloud site couldn’t be found or your Jira Cloud subscription has been deactivated due to inactivity.
Fix:

1. Check if your cloud site subscription is canceled:

   1. Go to admin.atlassian.com, and then select your organization if you have more than one.

   2. Select Billing.

2. If canceled, recover the canceled site.

Projects already exists in your cloud site

Project Name and Project Key Conflict When Migrating Using Jira Cloud Migration Assistant (JCMA)

Multiple users have the same email address

info Finishing execution of check SharedEmails. Success: false

Resolve duplicate email addresses when migrating to the Cloud

Invalid email addresses

info Finishing execution of check InvalidEmails. Success: false

Resolve invalid email addresses when migrating to the Cloud

ERROR <project key> project-export: The board ‘<board name>’ is assigned invalid administrators: ‘<group name>’.

To assign valid administrators to your board:

1. Open the board for which you want to assign administrators.

2. Go to Board > Configure.

3. In the Administrators field, hover over to click the edit icon.

4. Remove the invalid groups mentioned in the error log.

5. Enter the names of the users or groups. If you start typing the name, a list of users and groups will be suggested.

6. Press the Enter key when finished.

ERROR <project key> project-export: The issue type ‘<issue type name>’ with issue key ‘<issue key>’ has no ‘<issue status>’ status in workflow ‘<workflow name>’.

To assign valid status:

1. Select Settings > Issues. 

2. Under WORKFLOWS, click Workflow Schemes.

3. In the Workflow column, look for the affected workflow.

4. Open the workflow to view the list of valid statuses in the Linked Status column.

5. Open the issue for which the invalid status was assigned.

6. From the Workflow list, select a valid status.

ERROR <projectKey> project-export Couldn't migrate Request Type with id <requestTypeId> linked to Issue Type with id <issueTypeId>

Add the Issue Type with id <issueTypeId> to the Issue type Scheme of the project with id <projectId> to resolve

You can perform step A and step B to fix this error.

Step A: Make a list of issue types used for the request types of the Jira Service Management project.

To make a list:

1. In Jira Server or Data Center go to Settings > Projects.

2. Search for the Jira Service Management project for which the error was found.

3. Click to open Project settings screen.

4. Select Request types.

5. From the Issue type column, list down all the issue types. For example, Task, Service request etc.

Step B: Check and add the issue types that are missing from the Issue Types for Current Scheme list based on the issues types list from step A.

To add the missing issue types:

1. Go to Settings > Issues.

2. From the left panel, select Issue type schemes.

3. For the relevant issue type scheme of the Jira Service Management project, select Edit.

4. Drag the missing issue type from Available Issue Types to Issue Types for Current Scheme.

5. Click Save.

After step A and step B, you can retry your migration.

 ERROR <Project_Key> project-import
We couldn't import Project Component <Project_Component_Name>.
Reason: name: A component with the name <Project_Component_Name> already exists in this project...
This caused <Number_of_Items> other items to fail.

We couldn't import Project Component - JCMA Error

ERROR <Project_Key> project-import We couldn't import Project Version <Version_Name> because of <Number_of_Occurrences> missing dependencies: Project <Project_Key>.
This caused <Number_of_Issues> other items to fail. Check the reasons for the missing dependencies on your server site.

We couldn't import Project Version because of missing dependencies: Project - JCMA Error

 <Project Key> project-import
We couldn't import Issue <Project Key>-<Issue Number> because of 1 missing dependencies:
Custom Field 'Sprint'. This caused <Number of Ocurrences> other items to fail.
Check the reasons for the missing dependencies on your server site.

We couldn't import Issue because of 1 missing dependencies: Custom Field 'Sprint'

 com.atlassian.jira.migration.orchestratorclient.OrchestratorClientErrorException: request to Migration Orchestrator failed
com.atlassian.jira.migration.orchestratorclient.OrchestratorServerErrorException: failed to send a request to server

Request to server or Migration Orchestrator failed in JCMA

 ERROR <Project_Key> project-export
The workflow: [Workflow_Name] transition [Transition_Name] Missing config [Config_Name] value refence [Value_Reference_Name] in workflow rule condition/validator or post-function [Workflow_Rule_Name].
Double-check the workflow rule for missing config values or references.

Workflow missing config values or references - JCMA Error

ERROR <project-key> project-import We couldn't import Comment <comment-id> (on Issue <issue-key> by '<user>' on <timestamp>). Reason: CommentBodyCharacterLimitExceededException: No message.

ERROR <project-key> project-import We couldn't import Issue <issue-key>. Reason: description: The entered text is too long. It exceeds the allowed limit of 32,767 characters..

"CommentBodyCharacterLimitExceededException: No message" or "The entered text is too long. It exceeds the allowed limit of 32,767 characters.." error message in JCMA

 ERROR <Project_Key> project-import
We couldn’t import Issue <Issue_Key> because of 1 missing dependencies: Project <Project_Dependency_Key>.
This caused <Number_of_Items> other items to fail.
Check the reasons for the missing dependencies on your server site.

We couldn't import Issue because of missing dependencies: Project - JCMA Error

ERROR <Project_Key> project-export
The workflow: [Workflow_Name] transition: [Transition_Name]
has unsupported custom field reference in config hidFieldsList
for workflow rule validator [Validator_Name].
Double-check the workflow rule for missing config values or references.

Workflow rules migrated via Jira Cloud Migration Assistant

ERROR <Project_Key> project-export
We couldn't export Issue <Issue_ID>.
Reason:
com.atlassian.greenhopper.manager.lexorank.LexoRankIntegrityException:
Expected exactly <X> rows; the maximum marker row and the lowest
ranked row for rank field[id=<Field_ID>].

List of all known Agile Lexorank error

Jira server throws LexoRankIntegrityException error during reindexing or reranking operations

sun.security.validator.ValidatorException:
PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException:
unable to find valid certification path to requested target

Unable to connect to SSL services due to "PKIX Path Building Failed" error

java.net.UnknownHostException: <AMAZON_S3_URL>
java.net.ConnectException: Connection refused (Connection refused)

Preparing your firewall to migrate using the Jira Cloud Migration Assistant

We couldn't import Issue ABCD-12345. Reason: DataAccessException: java.sql.SQLException: PSQL_TOO_MANY_CONNECTIONS Exception already occurred in this workcontext, skipping next getConnection. This caused X other items to fail

'FATAL too many connections' error when using PostgreSQL database due to user-specific connection limit

java.lang.OutOfMemoryError: Java heap space

Jira server crashes with OutofMemory Java heap space error

ERROR <Project_Key> project-export
We couldn't export Issue <Issue_ID>.
Reason: com.querydsl.core.QueryException:
Caught SQLServerException for <SQL_QUERY>

How to fix the collation of Microsoft SQL Server database for Jira manually | Jira | Atlassian Documentation