TL;dr To ensure that we're able to continue to meet the needs of our ever-evolving migrators, we're discontinuing the migrate-all-data-at-once pathway in JCMA in favor of project-by-project migration. Migrate-all-data-at-once will no longer be available starting on September 1st, 2024.
Currently, in JCMA, migrators have two ways they can migrate their data to cloud, each with its own set of advantages and disadvantages, that is:
Project by Project (PbP) refers to the “Choose what to migrate” feature in the Jira Cloud Migration assistants.
Migrate-all-data-at-once (MAO) refers to the “Migrate all data at once” feature in the Jira Cloud Migration assistants.
However, our long-term goal has always been to offer migrators a simpler and more comprehensive path for migrating their product data to cloud. With this objective in mind, we are now announcing our intentions to begin the process of discontinuing MAO and going all-in on PbP. In the past few years, we’ve made significant advancements in the capabilities of PbP, and this announcement marks another milestone in establishing it as the preferred pathway for Jira migrations.
As of this announcement, we’ll no longer be making enhancements to "Migrate all data at once". However, for migrators who are actively using MAO, we’ll continue to support and maintain our current functionality until its formal discontinuation.
Scale & Complexity: Project-by-project is designed with scale in mind so we can continue to meet the ever-evolving needs of migrator's customers. PbP will allow you to more reliably support complex migration strategies where the goal is to transform how your teams work and advanced migration methods like phased that allow you to migrate at a pace that doesn’t disrupt your business:
migrate in phases allowing you to support complex change management programs.
select which data you want to migrate to the cloud. PbP will be enhanced with functionality that allows you to “Select all data”.
migrate data from multiple sites since it's non-destructive to the cloud environment.
decrease the number of iterations needed before a successful migration with more comprehensive troubleshooting capabilities.
Advanced Migration Capabilities: PbP is underpinned by a collection of shared services that are part of the Migration Tooling Platform. By investing more in PbP we’re investing in a more consistent experience across all our data portability offerings, as well as, new and innovative migration capabilities, such as, public migration APIs which are coming soon!
Improved Migration Experience: In addition to continuing to address the scale and complexity needs of migrators, PbP will offer migrators a better overall migration experience. Migrators will see a more:
complete data portability offering eliminating the need to use multiple pathways or bespoke configurations to migrate all of their data to the cloud.
curated user experience that’s designed to streamline the process of migrating providing migrators more visibility into how their migration is going and more granularity into what's going wrong.
To ensure that you and your teams are well-prepared for this transition, we are notifying you that Migrate-all-data-at-once will no longer be available as of September, 1st 2024.
If you’re actively pursuing a migration, we strongly recommend going through the following checklist:
Scenario |
Migrate-all-data-at-once Selected |
No Migration Method Selected |
---|---|---|
Migrating to Cloud with a plan to migrate date before September of 2024. |
PBP RECOMMENDED We strongly encourage you to revisit your existing migration plans and reassess whether project-by-project is a viable option for your migration. However, if you’ve already run multiple successful production migrations and your plan to migrate date is nearing (within 30 days) you do have the option to continue to use migrate-all-data-at-once. |
PBP RECOMMENDED |
Migrating to Cloud with a plan to migrate date after September of 2024. |
PBP RECOMMENDED |
PBP RECOMMENDED |
If you require assistance reach out to Atlassian Support or your Cloud Migration Manager who can give you more information on the change or relay any concerns you may have to our product team.
Branimir Kain
7 comments