Deciding on a migration methodology is highly dependant on your requirements. As a customer/partner you want to ensure that you are 100% confident with the choice you make before moving forward with the migration.
Compare cloud migration methods highlights the benefits and limitations of both tools which is also copied on the article below.
Moreover, you want to read carefully through What gets migrated with the Jira Cloud Migration Assistant and what doesn’t as it sets the expectations beforehand.
You can also attend a Demo on Cloud Migration which showcases how to execute a cloud migration, and give recommendations on the best practices and tools to use along the way.
Additional steps need to be taken to migrate the app data. You can view Atlassian Marketplace apps that are available in cloud with migration paths and also sign up for Early access program for app migration using Jira and Confluence Cloud Migration Assistants
Jira Method
Jira Site import
Jira Cloud Migration Assistant
Pros
Good for migrations to new cloud sites
Jira Service Desk will be migrated
Advanced Roadmaps (Portfolio) will be migrated
Can migrate all data (highest data resolution) at once
Can migrate in stages
Will not overwrite existing data in your cloud site
You can choose what projects you want to migrate
You can choose to migrate only users and groups
You can choose to migrate only users related to the projects you need to migrate
The app is installed in your server instance, and can help identify issues before you migrate
Guides you through the migration with an easy to use interface
Cons
App data won’t be migrated
The migration will overwrite any existing data in your cloud site (except users and groups)
Users may need to be imported separately if managed externally
You’ll need to be on a supported self managed managed version
You can’t choose what you do and don’t want to migrate (for example, only select projects)
Because this method is “all or nothing” large amounts of data can result in longer downtimes
Jira Service Desk will not be migrated (use Jira Site Import or CSV import instead)
Advanced Roadmaps (Portoflio) will not be migrated
You’ll need to be on a supported self-managed version
Specific entities (eg. custom fields, cross-project boards, dashboards, etc.) are not migrated
Need to allowlist specific IP addresses
Thank you @Amna Elabbas for comparing this. It would be definitively useful. The biggest problem however is that both methods still have limitations..
Hi @Mirek , we are constantly improving our methodologies and while both methods indeed have limitations, they are both very powerful and demonstrated success for customers' use cases. It's crucial that the customers/partners have the right migration strategy in place to workaround the limitations.
Hi There,
It's Jason here. I'm from the Cloud Migration Platform team that builds both the Jira Cloud Migration Assistant and Site import.
I just wanted to give an update on the Cons for the Jira Cloud Migration Assistant;
If you are interested in joining any of the EAPs please sign up here https://go.atlassian.com/appmigrationseap
@Mirek which limitations would you like us to address first?
@Jason Wong- Migrating Insight data for example. But if you ask to choose from the EAP list that you added above then I think Service Desk and definitively app data since both methods do not cover that..
It looks like you're new here. Sign in or register to get started.
