Troubleshoot migration with Jira Cloud Migration Assistant

If your Jira Server site is highly customized, you may face additional issues when migrating. For example, if you have any required field with a null value the migration will fail because this is not supported on your Cloud site. We recommend cleaning up your instance data before migrating.

An incomplete status means that some things have been migrated but there was at least 1 entity that we couldn’t migrate. For example, we might be able to migrate a project but 1 issue fails because there is a null value in a custom field. In this case, the project will show up as incomplete even though all the actual data is complete. Many times this status will not be a problem for your migration. Download the error logs to determine what is causing the failure. 

If you make any changes on your Server site, wait at least 10 minutes before migrating to allow all data to be updated. 

If you choose to change a project key on your Server before or during migration, make sure that all configuration, filters and boards are updated with the new project key before attempting a new migration. 

If you have chosen to migrate in smaller batches, links to projects or issues that haven't yet been migrated will be missing until that linked item is migrated. 

If a history entry refers to a missing link or attachment, the history entry won't be migrated. If a linked issue or project is migrated at a later date, the history entry will be updated. 

The migration assistant does not check that  the JQL issue filters on boards are returning the correct results after migration. If a board has a filter that mentions a project or field that is not yet migrated, the board may not return the same results after it is migrated. To fix this issue, edit the board's JQL filter after migrating. Learn more about board filters

If you use Jira Align, you need to complete additional steps before, during, and after the migration. If you’re having problems, see the linked page or contact Atlassian Support. Learn how to migrate Jira Align

The check has passed. You can proceed with your migration.

You can proceed with your migration, but you need to be aware of a potential issue. Expand the warning messages to view details.

You can’t proceed with your migration until you resolve the error. Expand the error messages to view details.

The check wasn’t completed due to an unexpected error. Refresh the checks or contact Atlassian support.

The Jira Cloud Migration Assistant authentication token might have expired.

Learn how to renew your authentication token

The Jira Cloud Migration Assistant authentication token might have expired.

Learn how to renew your authentication token

The Jira Cloud Migration Assistant authentication token might have expired.

Learn how to renew your authentication token

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 Apps > 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.

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

Fix duplicated email addresses in simple experience

Fix invalid email addresses in simple experience

This check is shown when the number of email aliases related to a single primary email exceeds the limit of 10. An alias is a variation of the primary email, for example charlie+suffix@atlassian.com vs. charlie@atlassian.com.

The limit exists on the cloud side and allows to create only 10 aliases per hour.

Download CSV file

When viewing the check, you can download a CSV file to help you resolve the issue. The file:

• Lists all email aliases (including the first 10) for cases where the limit was exceeded. It might include aliases related to multiple primary emails.

• Doesn’t include the primary email itself.

Goal

Your goal is to change the aliases into individual emails or delete the corresponding users. It’s enough if you do it for aliases that exceed the limit. However, since cloud subscriptions are billed per user, you might want to delete or deactivate these extra users.

Solve the issue

To solve this issue, use the CSV file to identify the corresponding users and either update or delete them:

• If you manage users in Jira, you can update them in Administration > User management.

• If you manage users in an external directory, we recommend that you update users in the directory so the aliases aren’t provisioned to cloud.

Issue has no issue type.

To fix this issue:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Select a valid issue type ID for each affected project and select Apply.

3. Select Rerun after you’ve applied all the changes.

You can also fix this issue in bulk:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Download the ZIP file.

3. Unzip the folder and open the CSV file.

4. In the Fix column, fill in the valid issue type ID for each affected project.

5. Select Upload ZIP to upload the updated CSV.

Issue has no default priority.

To fix this issue:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Select a valid priority ID for each affected project and select Apply.

3. Select Rerun after you’ve applied all the changes.

You can also fix this issue in bulk:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Download the ZIP file.

3. Unzip the folder and open the CSV file.

4. In the Fix column, fill in the valid priority ID for each affected project.

5. Select Upload ZIP to upload the updated CSV.

Board has no owner

To fix this issue:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Select a valid user key for each affected board and select Apply.

3. Select Rerun after you’ve applied all the changes.

You can also fix this issue in bulk:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Download the ZIP file.

3. Unzip the folder and open the CSV file.

4. In the Fix column, fill in the valid user key for each affected board.

5. Select Upload ZIP to upload the updated CSV.

Filter has no owner

To fix this issue:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Select a valid user key for each affected filter and select Apply.

3. Select Rerun after you’ve applied all the changes.

You can also fix this issue in bulk:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Download the ZIP file.

3. Unzip the folder and open the CSV file.

4. In the Fix column, fill in the valid user key for each affected filter.

5. Select Upload ZIP to upload the updated CSV.

Group reference not found (filter subscription)

To fix this issue:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Select a valid entity ID and select Apply.

3. Select Rerun after you’ve applied all the changes.

You can also fix this issue in bulk:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Download the ZIP file.

3. Unzip the folder and open the CSV file.

4. In the Fix column, fill in the valid entity ID.

5. Select Upload ZIP to upload the updated CSV.

Your input will override the existing entity IDs.

Group reference not found (issue security level permission)

To fix this issue:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Select a valid entity ID and select Apply.

3. Select Rerun after you’ve applied all the changes.

You can also fix this issue in bulk:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Download the ZIP file.

3. Unzip the folder and open the CSV file.

4. In the Fix column, fill in the valid entity ID.

5. Select Upload ZIP to upload the updated CSV.

Your input will override the existing entity IDs.

A board is referring to a filter that doesn’t exist

To fix this issue:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Select a valid filter ID and select Apply.

3. Select Rerun after you’ve applied all the changes.

You can also fix this issue in bulk:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Download the ZIP file.

3. Unzip the folder and open the CSV file.

4. In the Fix column, fill in the valid filter ID.

5. Select Upload ZIP to upload the updated CSV.

Your input will override the existing filter IDs.

Issue has an invalid status

To fix this issue:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Select a valid issue status ID for each affected project and select Apply.

3. Select Rerun after you’ve applied all the changes.

You can also fix this issue in bulk:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Download the ZIP file.

3. Unzip the folder and open the CSV file.

4. In the Fix column, fill in the valid issue status ID for each affected project.

5. Select Upload ZIP to upload the updated CSV.

Issue is assigned an issue type that doesn’t exist in the project’s scheme

To fix this issue:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Select a valid issue type ID for each affected project and select Apply.

3. Select Rerun after you’ve applied all the changes.

You can also fix this issue in bulk:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Download the ZIP file.

3. Unzip the folder and open the CSV file.

4. In the Fix column, fill in the valid issue type ID for each affected project.

5. Select Upload ZIP to upload the updated CSV.

Project component name is missing

To fix this issue:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Enter a valid component name for each affected project, then select Apply.

3. Select Rerun after you’ve applied all the changes.

You can also fix this issue in bulk:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Download the ZIP file.

3. Unzip the folder and open the CSV file.

4. In the Fix column, enter a valid component name for each affected project.

5. Select Upload ZIP to upload the updated CSV.

Swimlane has invalid JQL

To fix this issue:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Enter a valid JQL string and select Apply.

3. Select Rerun after you’ve applied all the changes.

You can also fix this issue in bulk:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Download the ZIP file.

3. Unzip the folder and open the CSV file.

4. In the Fix column, enter a valid JQL string.

5. Select Upload ZIP to upload the updated CSV.

Quick filter has invalid JQL

To fix this issue:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Enter a valid JQL string and select Apply.

3. Select Rerun after you’ve applied all the changes.

You can also fix this issue in bulk:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Download the ZIP file.

3. Unzip the folder and open the CSV file.

4. In the Fix column, enter a valid JQL string.

5. Select Upload ZIP to upload the updated CSV.

Custom field ID is invalid in the Time metric

To fix this issue:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Select a custom field ID that belongs to the project and select Apply.

3. Select Rerun after you’ve applied all the changes.

You can also fix this issue in bulk:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Download the ZIP file.

3. Unzip the folder and open the CSV file.

4. In the Fix column, fill in a valid custom field ID for each affected project.

5. Select Upload ZIP to upload the updated CSV.

JSM project contains a time metric with a duplicate name

To fix this issue:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Enter a unique name for your SLA and select Apply.

3. Select Rerun after you’ve applied all the changes.

You can also fix this issue in bulk:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Download the ZIP file.

3. Unzip the folder and open the CSV file.

4. In the Fix column, enter a unique name for your SLA.

5. Select Upload ZIP to upload the updated CSV.

A JSM request type references an issue type that isn’t associated with the project

To fix this issue:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Select an issue type ID that belongs to the project’s issue type scheme and select Apply.

3. Select Rerun after you’ve applied all the changes.

You can also fix this issue in bulk:

1. Select Fix remediable errors in the Data preparation section of the Pre-migration checks page.

2. Download the ZIP file.

3. Unzip the folder and open the CSV file.

4. In the Fix column, enter an issue type ID that belongs to the project’s issue type scheme.

5. Select Upload ZIP to upload the updated CSV.

ERROR [JCMA 124] <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 [JCMA 147] <project key> project-export: The Kanban / Scrum board '<board name>’ cannot be linked to the Business project ‘<project name>’ on cloud.

Convert a project to a different template or type

ERROR [JCMA 151] <project key> project-export: The workflow ‘<workflow name>' with transition '<transition name>’ is linked to an invalid screen.

To assign a valid screen to the workflow transition:

1. Select Settings > Issues. 

2. Under WORKFLOWS, select Workflows.

3. Look for the affected workflow name, and select Edit.

4. In the diagram, select the affected transition.

5. On the right-hand side of the screen, select Edit to change the screen name.

6. Select Save.

7. Repeat steps 4 through 6 to fix multiple transitions.

ERROR [JCMA 510] <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 CROSS-PROJECT-DATA project-export Exception Message generated on executing query for fetching arPlanPermissions -> <exception message>
Exception Cause -> <exception cause>

Use the following KB articles to resolve the error:

• How to fix the collation of the Microsoft SQL Server database for Jira manually

• Plans missing in Advanced Roadmaps for Jira after updating SQL Server Collation

Unsupported custom field configuration

Migration of <custom_field_type_name> custom field type isn't supported. Therefore, the configuration for this field won't be migrated, and any items that reference it, such as workflow schemes and filters, may no longer work.

If you need this custom field, recreate it in your cloud site and use a CSV import to update the issues post-migration. Refer to the Adding additional entities with CSV section in this document:

What gets migrated with the Jira Cloud Migration Assistant

Unsupported custom field configuration

Migration of the <custom_field_name> custom field isn't supported. The value for this issue will not be migrated.

If you need this field value, use a CSV import to update the issues post-migration. Refer to the Adding additional entities with CSV section in this document:

What gets migrated with the Jira Cloud Migration Assistant

Unsupported issue type

During the migration, the <issue_type_name_A> issue type will be renamed to <issue_type_name_B> issue type.

Review the issue type after migration to ensure it functions as expected. Some JQL references may be affected and need to be updated after migration.

Unsupported notification scheme

The notification schemes aren't supported and won't be migrated.

The default notification scheme will be assigned to each project in the cloud site. Review the permissions post migration.

Missing configurations or references in the condition of the workflow

The workflow will be migrated. However, the condition on <transition_name> transition of the workflow will be skipped, which may impact the permissions in your cloud site.

Review the workflow post-migration to ensure that the permissions are set correctly. To identify workflows that might be affected during pre-migration, run SQL queries from this page:

Troubleshooting errors and non-migrated entities with the Jira Cloud Migration Assistant

Missing configurations or references in the transition of the workflow

The <transition_validator_name> validator isn't supported. The workflow will still be migrated. However, the validator on <transition_name> transition of the workflow will be skipped, which may impact the permissions in your cloud site.

Review the workflow post-migration to ensure that the permissions are correctly set. To identify workflows that might be affected during pre-migration, run SQL queries from this page:

Troubleshooting errors and non-migrated entities with the Jira Cloud Migration Assistant

Missing configurations or references in the post function of the workflow

The <name> post function isn't supported. The workflow will still be migrated, however the post function on <name> transition will be skipped, which may impact the workflow in your cloud site.

Review the workflow post-migration to ensure it functions as expected. To identify workflows that might be affected during pre-migration, run SQL queries from this page:

Troubleshooting errors and non-migrated entities with the Jira Cloud Migration Assistant

Unsupported custom event type

The notification for the event type <event_type_name> isn't supported through migration (custom event issue). The value for this issue will not be migrated.

If you need this field value, use a CSV import to update the issues post-migration.

Null filename for attachments

Attachments with a null value for the filename aren't supported and won't be migrated.

If you need this attachment on your cloud site, you need to first assign a non-null filename to the given attachment ID on your server and then run the migration.

Unsupported gadget

This gadget isn't supported and won't be migrated.

1. In the server, from the Dashboards menu, select the dashboard identified in the Entity IDs or keys column of the CSV file.

2. From the unsupported gadget identified in the Entity name column, select … > Delete.

3. In the cloud site, open the migrated dashboard and select Edit.

4. Identify the desired gadget from the Add a Gadget list and select Add.

5. Select Done once you've added the gadget.

View the list of supported gadgetsView the list of supported gadgets

Partially migrated gadget

Found errors while migrating this gadget; therefore, it will be migrated without its configurations. For error details, refer to the log files generated when creating the support zip.

Steps to create a support zip

1. Identify the affected gadget and the corresponding dashboard from the log file.

2. Open this dashboard on your cloud site.

3. Select Edit.

4. Select … > Configure in the affected gadget.

5. Update the configuration value in this gadget.

6. Select Save.

 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 YYY project-import We couldn't import Permission Scheme 'XYZ scheme'.

Reason: IllegalStateException: Errors: {holder.parameter=User 'user.name' does not exist}

There are permission schemes associated with the selected projects in your migration that reference invalid, or missing users. These users are often located in out of date accounts in your Crowd or External Identity Provider (IDP) that were never migrated across to begin with.

Fix:

1. Remove the referenced user from named permission scheme in your server/DC instance.

2. Remove or delete users from permission schemes.

3. Use the Jira Cloud Migration Assistant to rerun the migration.

ERROR YYY project-import We couldn't import Field Layout Item XXXXX-customfield_XXXXX.

Reason: Field customfield_XXXXX does not exist in FieldLayout XXXXX.

ERROR YYY project-import We couldn't import Project YYY.

Reason: IllegalArgumentException: Issue type scheme [XXXXX] does not exist.

ERROR YYY project-import We couldn't import Project YYY.

Reason: IllegalArgumentException: Workflow scheme [XXXXX] does not exist.

ERROR YYY project-import We couldn't import Issue YYY-XXXX.

Reason: NullPointerException: There is no step in workflow [workflow] linked to status [status].

This is as a result of updating or removing previously migrated entities from the source or destination sites.

Do one of the following to mitigate this problem:

• If you have run into this problem on a test site, reset and delete all data from your cloud site. Or,

• If you are unable to reset the target site, contact Atlassian Support.

ERROR YYY project-import We couldn't import Project Role Association XXXXX.

Reason: IllegalArgumentException: Project role [XXXXX] does not exist

Indicates that the projects in your migration have roles or permission schemes, which reference groups or roles that no longer exist.

Do one of the following to mitigate this problem:

• Re-create these roles or groups so that they exist on the source before running the migration again. Or,

• Edit the project's permissions to remove any references to these roles or groups before running the migration again.

More about editing permissions and roles in your Jira projects

ERROR <Project_Key> project-import We couldn't import Permission Scheme '<Project_Key> Standard Permission Scheme'. Reason: IllegalStateException: Errors: {holder.parameter=Group '<group name>' does not exist}
Error Messages: []
Error reasons: [VALIDATION_FAILED]. This caused 377987 other items to fail.

• Add the required <group name> to the Jira access on cloud.

• Remigrate the project from server to cloud

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

Exceeded the limit of Asset Objects allowed per custom field in an issue.

Each issue can have limited number of Asset Objects linked to a custom field on Cloud.

In your next migration, we recommend that you reduce the number of Asset Objects in your migration. Read how to reduce the count of Asset Objects

If you’ve concerns with the existing limits, contact support.

Exceeded the limit of Select attributes in Object history.

Object history can only have up to 100 Select attributes.

If you’ve concerns with the existing limits, contact support.

Exceeded the limit of unique constraints per object type.

Each object type can have a maximum of 2 attributes with unique constraints in Cloud. Any additional unique constraints will be marked non-unique when migrated.

In your next migration, we recommend that you reduce the number of unique constraints per object type to 2. Read how to reduce the count of unique constraints

Attributes with duplicate values are no longer marked as unique.

If Object attributes have duplicate values, they are marked as non-unique, even if they were configured as unique in Data Center.

In your next migration, we recommend that you delete duplicate values. Read how to delete duplicate values

Exceeded the maximum cardinality for the URL, Email, and Select attributes.

The maximum supported limit for URL, Email, and Select attribute types is 50 in Cloud. We have migrated only 50 values, randomly selected within the limit.

You can contact support to understand what data has not been migrated.

In your next migration, we recommend deleting URLs, Emails, and Select attributes that are not required.

Exceeded the maximum cardinality in an attribute.

The maximum supported limit for an attribute is 20,000. We couldn’t migrate additional values beyond this limit.

You can contact support to understand what data has not been migrated.

In your next migration, we recommend deleting attributes that are not required.

Exceeded the combined character limit for the URL, Email, and Select attributes.

The character limit for URL, Email, and Select attributes is 2700 characters. We couldn’t migrate additional data beyond this limit.

You can contact support to understand what data has not been migrated.

In your next migration, we recommend reducing the character count.

Exceeded the total character limit for the TextArea attribute.

The character limit for all TextArea attribute values is 10,000. We couldn’t migrate additional data beyond this limit.

You can contact support to understand what data has not been migrated.

In your next migration, we recommend reducing the character count.

Exceeded the maximum character limit for the Text attribute.

The character limit for a text attribute value is 255 characters. We couldn’t migrate additional data beyond this limit.

You can contact support to understand what data has not been migrated.

In your next migration, we recommend reducing the character count.

Assets Query Language (AQL) for this entity couldn't be fully resolved.

We couldn’t resolve Assets Query Language (AQL) for this entity due to one or more of the following reasons:

• It references an unsupported reference function.

• It references unsupported connectedTickets.

• It references an unsupported custom field ID.

• It references objectSchemaId missing from the data copy.

Contact support for help.

Exceeded the limit of Name and/or Description fields in the Object Type Attribute

The character limit for Name and Description fields is 255 characters. We couldn’t migrate additional data beyond this limit.

You can contact support to understand what data has not been migrated.

In your next migration, we recommend reducing the character count.

Exceeded limit of Regex validation field in Object Type Attribute

The character limit for Regex validation field in Object Type Attribute is 128 characters. We couldn’t migrate additional data beyond this limit.

You can contact support to understand what data has not been migrated.

In your next migration, we recommend reducing the character count.

Exception occurred in the server app

An error has most likely occurred in the server app. This may stop further migration operations in the server app, and could cause a timed-out app migration.

If the app’s migration does not settle, contact the Marketplace Partner and provide the following information:

• the app migration status and a clear description of the warning of the server exception

• your cloud site url

• entire progress logs of the app

• details on how Marketplace Partners can handle server exceptions

The Marketplace Partner may direct you to contact Atlassian Support if they need Atlassian to help with server exception.

Failed to notify Cloud app about start of app migration

An failure error occurred when attempting to notify with the Cloud app that app migration has started. Multiple retries to notify the cloud app has not returned as successful response.

Notifying the cloud app is needed to allow Marketplace Partners to begin app migration. Potentially, this error can lead to a timed-out app migration.

If the cloud app does not get updated, contact the Marketplace Partner and provide the following information:

• the app migration status and a clear description of this warning

• your cloud site url

• entire progress logs of the app

• details on how Marketplace Partners can handle server exceptions