Rate this page:
The 'Migrate all data at once' feature is available for the Jira Cloud Migration Assistant (JCMA) version 1.9.0 and higher, for customers who want to migrate core product data and app data.
This feature may also be referred to as 'Bulk migration'.
Compared to the original Project-by-Project migration method of JCMA, the 'Migrate all data at once' feature of bulk migration:
The higher migration speed of this feature is made possible by using a direct import method on the cloud site, and makes larger migrations more viable for customers by considerably reducing the downtime required for migration.
A key focus of this feature has been to ensure compatibility with our Marketplace Partner’s existing investments into building automated migration paths for JCMA. As a result, we have designed the 'Migrate all data at once' feature to work in a way that's broadly transparent to your existing migration path.
This means that Marketplace Partners can use the same migration paths for 'Migrate all data at once' migrations, as was used by the original the Project-by-Project migration method.
The 'Migrate all data at once' feature cannot migrate data to a cloud site incrementally. This means that this feature needs to start with an empty cloud site, and its first action is to clear the destination site of all data and prepare it as a new site that's ready for import.
Functionally, a bulk migration using the 'Migrate all data at once' feature follows the same structure and has the same resources available to Marketplace Partners, as exists with the original Project-by-Project migration method.
Triggering an 'Migrate all data at once' bulk migration can only be done to an empty cloud site, and the content is considered a replacement for any site that existed at that path in the past. As a result:
As the 'Migrate all data at once' bulk migration requires a blank site, all Marketplace Partner apps will have to be re-installed as part of the migration process. This will happen as part of a migration stage before a Marketplace Partner’s app is notified of a new transfer.
It is important to note that you will not receive an uninstall event as part of this process.
Your app should also be ready to handle multiple installation events via Atlassian’s Connect framework. Also, the license for your app will remain untouched.
Read more about why this is treated as a new install
As the bulk migration of the 'Migrate all data at once' feature requires a blank site, it can only support the initial migration a customer performs.
Customers can also:
The 'Site Import' feature uses the same direct import process as the 'Migrate all data at once' feature. However, some of the limitations of Site Import are that it:
As with Site Import, the 'Migrate all data at once' feature cannot migrate to a cloud site if it already contains data.
Currently, bulk migrations will carry over the server ID for nearly all entity types. However, this is not a contractual attribute and is subject to change in the future based on other requirements.
We expect customers in the short term to be able to use Site Import tooling where it already exists, rather than the JCMA path. However, this will cease to be possible in the future, and it is recommended that all Marketplace Partners prepare their automated migration paths to ensure that it works with this new 'Migrate all data at one' bulk migration method.
Rate this page: