Data Center Latest
Versions

Troubleshooting pre-migration errors

What is Cloud-hosted migration assistant?

On this page

Related content

  • No related content found

Still need help?

The Atlassian Community is here for you.

Ask the community

This page outlines the errors encountered during pre-migration checks when creating a migration plan with the Cloud-hosted migration assistant, along with solutions to resolve them. Read how to create a migration plan

The Cloud-hosted migration assistant is currently available only to a limited number of customers participating in an early access program. We are not enrolling new customers at this time, but we will keep you updated when we reopen enrollment.

To find the resolution for an error, use Ctrl+F or Command+F to search for the error you see during your migration.

Data preparation errors

Data preparation errors can be resolved in the user interface without requiring you to upload a CSV file.

Error
 

Why is this error occurring?
 

How to fix
 

Some issues use issue types that no longer exist

The linked issue type does not exist or is invalid.

  1. Select the Fix error option.

  2. Enter an issue type to all affected issues listed, or select a new one for each issue.

Some issues use workflow statuses that no longer exist

The linked workflow status does not exist or is invalid.

  1. Select the Fix error option.

  2. Enter a status to all affected issues, or select a new status for each issue.

Some issues have missing priorities

The priority value does not exist or is invalid.

  1. Select the Fix error option.

  2. Enter a priority to all affected issues, or select a new priority for each issue.

Some issue security levels are granted to groups that no longer exist

The security levels are not linked to valid groups.

  1. Select the Fix error option.

  2. Enter a group to all affected security levels, or select a new group for each security level.

Some boards don’t have owners

The board does not have a valid owner.

  1. Select the Fix error option.

  2. Enter a single owner to all boards, or select a new one for each board.

Some SLAs have duplicate names

The name of the SLA is not unique.

  1. Select the Fix error option.

  2. Enter a new name for the affected SLAs.

Some boards reference filters that no longer exist

The filters linked to certain boards are invalid.

  1. Select the Fix error option.

  2. Enter a new filter ID for each affected board.

Some boards are assigned to user accounts that no longer exist

The board is not linked to a valid admin.

  1. Select the Fix error option.

  2. Assign the same admin to all affected boards, or select a valid admin for each affected board.

Some filters have owners that no longer exist

The board is not linked to a valid user.

  1. Select the Fix error option.

  2. Assign the same owner to all affected filters, or select a valid owner for each affected filter.

Some filters are shared with groups that no longer exist

The affected filters are linked to groups that don’t exist.

  1. Select the Fix error option.

  2. Assign a single group to all affected filters, or select a new group for each filter.

Some boards don’t have owners

The board does not have a valid owner.

  1. Select the Fix error option.

  2. Assign a single owner to all boards, or select a new one for each board.

CSV errors

These errors require you to download a ZIP file while contain detailed error reports. You can edit and upload the Remediable CSV back to resolve these errors.


Error ID/ Error
 

Why is this error occurring?
 

How to fix
 

107 - Issue has no issue type.

The issue is not linked to a default issue type.

  1. Download the CSV.

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

  3. Upload the updated CSV.

109 - Issue has no default priority.

The issue is not linked to a valid priority.

  1. Download the CSV.

  2. In the Fix column, fill in the valid priority ID for each affected priority scheme.

  3. Upload the updated CSV.

120 - A board has no owner.

Each board is linked to an owner.

  1. Download the CSV.

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

  3. Upload the updated CSV.

130 - A filter has no owner.

The filter is not linked to a valid owner.

  1. Download the CSV.

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

  3. Upload the updated CSV.

133 - An issue’s security level is assigned to a group that doesn’t exist.

Security level assigned to a group doesn’t exist.

  1. Download the CSV.

  2. In the Fix column, provide a valid entity ID.

  3. Upload the updated CSV.

Your input will override the existing entity IDs.

133 - An issue filter subscription is assigned to a group that doesn’t exist.

Filter subscription assigned to a group doesn’t exist.

  1. Download the CSV.

  2. In the Fix column, provide a valid entity ID.

  3. Upload the updated CSV.

Your input will override the existing entity IDs.

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

The filter linked to the board is missing.

  1. Download the CSV.

  2. In the Fix column, provide a valid filter ID.

  3. Upload the updated CSV.

Your input will override the existing filter IDs.

149 - Issue has an invalid status.

The issue is not linked to a valid status.

  1. Download the CSV.

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

  3. Upload the updated CSV.

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

The issue type assigned to the project scheme is invalid.

  1. Download the CSV.

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

  3. Upload the updated CSV.

155 - Project component name is missing.

Each project will require a name.

  1. Download the CSV.

  2. In the Fix column, fill in the valid component name for each affected project.

  3. Upload the updated CSV.

522 - JSM project contains a time metric with a duplicate name.

The SLA of your Jira Service Management project doesn’t have a unique name.

  1. Download the CSV.

  2. In the Fix column, provide a unique name for your SLA.

  3. Upload the updated CSV.

Your input will override the existing SLAs.

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

The Jira Service Management request references an issue type that is not associated with the project.

  1. Download the CSV.

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

  3. Upload the updated CSV.

Your input will override the existing issue type IDs.

Last modified on Apr 27, 2026

Was this helpful?

Yes
No
Provide feedback about this article

Related content

  • No related content found
Powered by Confluence and Scroll Viewport.