Plan your Cloud migration
Documents to help you prepare to migrate your Atlassian Server products.
This page will help you troubleshoot problems that you may experience with the Jira Server to Cloud migration. We have an extensive list of Knowledge Base (KB) articles to help you with your migrations.
How to use this page
Press Ctrl+F or Command+F (on a Mac) on this page and enter the error message details into the find field to look for the relevant KB article.
If you are not able to fix the problem using this page, contact support.
Note: For a quicker response from the support team, it’s recommended that you share a support zip with the Atlassian Support team. Learn how to create a Support ZIP
We have divided this page based on where you might experience problems in your migration journey.
After you select the migration options in the Choose your migration options screen, the Jira Cloud Migration Assistant performs some checks to review your Server and Cloud data. Based on these checks, the Pre-migration checks screen shows errors and warnings. You can expand the checks to read more about the problem and fix an error or warning.
The table below explains the different symbols associated with the pre-migration checks.
Symbol | Description | Action required |
---|---|---|
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. |
Here is a list of fixes / KB articles for some of the common errors that occur in the Pre-migration checks screen.
Message | Fixes / KB articles |
---|---|
We are currently updating the migration service | The Jira Cloud Migration Assistant authentication token might have expired. |
We couldn’t check for users count limit | The Jira Cloud Migration Assistant authentication token might have expired. |
We couldn’t check for projects in your cloud site | The Jira Cloud Migration Assistant authentication token might have expired. |
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:
Reason 2: Your cloud site couldn’t be found or your Jira Cloud subscription has been deactivated due to inactivity.
|
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 |
These errors are recorded in the log files (downloadable zip file) under the Data preparation check in the Pre-migration checks screen.
Error | Fix |
---|---|
ERROR <project key> project-export: The board ‘<board name>’ is assigned invalid administrators: ‘<group name>’. | To assign valid administrators to your board:
|
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:
|
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:
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:
After step A and step B, you can retry your migration. |
These errors could be a result of a failed migration or an incomplete migration. You can download the error logs to view all the errors.
To download error logs:
In the Review your migration screen, go to the Logs and Reports tab.
Under Error log, select Download.
Here is a list of KB articles that will help you troubleshoot possible errors that occur after you run a migration.
Error | Fixes / KB articles |
---|---|
ERROR <Project_Key> project-import | |
ERROR <Project_Key> project-import We couldn't import Project Version <Version_Name> because of <Number_of_Occurrences> missing dependencies: Project <Project_Key>. | We couldn't import Project Version because of missing dependencies: Project - JCMA Error |
<Project Key> project-import | We couldn't import Issue because of 1 missing dependencies: Custom Field 'Sprint' |
com.atlassian.jira.migration.orchestratorclient.OrchestratorClientErrorException: request to Migration Orchestrator failed | |
ERROR <Project_Key> project-export | |
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.. | |
ERROR <Project_Key> project-import | We couldn't import Issue because of missing dependencies: Project - JCMA Error |
ERROR <Project_Key> project-export | |
ERROR <Project_Key> project-export | List of all known Agile Lexorank error Jira server throws LexoRankIntegrityException error during reindexing or reranking operations |
sun.security.validator.ValidatorException: | Unable to connect to SSL services due to "PKIX Path Building Failed" error |
java.net.UnknownHostException: <AMAZON_S3_URL> | 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 | |
java.lang.OutOfMemoryError: Java heap space |
Error | Fixes / KB articles |
---|---|
ERROR <Project_Key> project-export |
|
We have a number of channels available to help you with your migration.
For more migration planning information and FAQs, visit the Atlassian Cloud Migration Center.
Have a technical issue or need more support with strategy and best practices? Get in touch.
Looking for peer advice? Ask the Atlassian Community.
Want expert guidance? Work with an Atlassian Partner.
Support for Atlassian Server products ends in February, 2024. Learn more about the Server end of support timeline.
Was this helpful?