Documents to help you prepare to migrate your Atlassian Server products.
A collection of topics that help prepare you to migrate your apps to the Cloud.
Ensure you’re ready to migrate with these pre-migration checklists for Jira, Confluence, and Bitbucket Server or Data Center.
Migrate your Jira data with the Jira Cloud Migration Assistant. This is the recommended way to migrate.
Migrate your Confluence data with the Confluence Cloud Migration Assistant. This is the recommended way to migrate.
Documents that walk you through using the Bitbucket Cloud Migration Assistant to migrate to Cloud.
Complete these tasks after migrating from Server or Data Center to Cloud.
Resources to help get started and testing after you migrate.
Everything you need to know about moving your data from one cloud site to another.
A set of optional best practices that you can apply to your migration.
Your company managed project boards can contain issues from team and company managed projects. Some of these issues have statuses with the same name and category, creating duplicate statuses. Team managed projects have project-level statuses, and company managed projects have global-level statuses. But both are considered the same category of status during import which causes an error.
Duplicate statuses check
Before you migrate, we check your data for duplicate statuses. You need to fix them to continue with the migration.
Remove duplicate statuses
Before you can run the migration, fix this error by removing duplicate statuses from the projects.
Go to the Check for Conflicts screen, and find Your projects contain duplicate statuses.
Download the CSV file for the list of affected projects and do one or more of the following to fix:
Remove the affected statuses manually from your projects before migration.
Go to your Jira instance.
Go to Project <projectName>
Select the three-dot icon on the left side and select Board settings.
Select General. Under Filters > Saved filters, select Edit Filter Query.
Remove reference to team-managed projects from the JQL filter query.
Go back to board settings and select Columns. The Column management screen displays the status of team-managed projects in a warning state.
Drag these projects to the Unmapped status column and then continue migrating the project.
Skip the projects with duplicate statuses.
Check the projects with duplicate statuses from the downloaded CSV file.
Go back to the Choose screen.
Deselect the affected projects that were listed in the CSV file.
Proceed with the migration of the remaining projects.
To fix the projects with duplicate statuses, contact support
We only remove duplicate statuses from the migration. Your source site will still contain these statuses in the team managed projects. Your destination site will not have the removed statuses.
Was this helpful?