Rate this page:
This page includes release notes and updates about the App migration platform for individuals who develop migration paths to move app data from server/data center to cloud.
Use this page to keep track of new or updated features, deprecations, and bug fixes.
Read our docs on getting support through the right channel.
When an app migration fails or is incomplete, customers can now re-run it without having to create a new migration plan. This feature is generally available starting with Jira Cloud Migration Assistant (JCMA) 1.9.17
To handle a request to re-run a migration, your server app can use its existing implementation of the DiscoverableListener interface or implement the RerunnableDiscoverableListener interface available in atlassian-app-cloud-migration-listener:1.2.0.
To identify the original migration, events generated during a re-run have an additional property, originalTransferId.
Learn more about re-running an unsuccessful app migration.
When an app migration fails or is incomplete, customers can now re-run it without having to create a new migration plan. This feature is generally available starting with Confluence Cloud Migration Assistant (CCMA) 3.4.14.
To handle a request to re-run a migration, your server app can use its existing implementation of the DiscoverableListener interface or implement the RerunnableDiscoverableListener interface available in atlassian-app-cloud-migration-listener:1.2.0.
To identify the original migration, events generated during a re-run have an additional property, originalTransferId.
Learn more about re-running an unsuccessful app migration.
This issue is fixed in Jira Cloud Migration Assistant version 1.9.14.
When the status of a check result is WARNING and the user selects the Download report button in the migration assistant, the operation no longer fails with an HTTP 500 error and the message UnableToWriteCsvException: Csv content is empty when the content is not empty.
Related ticket: https://jira.atlassian.com/browse/MIG-1482
More info: https://developer.atlassian.com/platform/app-migration/build-app-vendor-checks/#known-issues
We will be introducing Progress Logs, a new feature that provides users with better visibility into recent migration activities in descending time order, such as app data uploaded events and status updates from your Cloud app. This enhancement is available for JCMA 1.9.12 and CCMA 3.4.11 onwards.
Key highlights of Progress Logs:
Information Progress Logs: Expected progress logs that occur during an app migration
Warning Progress Logs: Logs that could impact the success of a migration, like failure to notify your Cloud app of an event.
CSV Download: Users can download a CSV containing progress logs.
Please note that not all migration actions produce logs, and the current display limit is up to the most recent 4000 logs.
You can now perform migrations with the “Migrate all data at once” mode in JCMA.
Support has been added for App Migrations with the new “Migrate all data at once” mode added to JCMA earlier this year. This new mode makes use of the existing JCMA migration path that partners have created for their apps.
You can find information about important similarities and differences on this page.
The Marketplace Endpoint for App Migrations has been updated with new fields.
These new fields will help Marketplace Partners to have more control of the migration path for their apps. This status will reflect directly on the App Assessment
screen in CMAs for the column “Can be Migrated”.
For more details see this page.
Available in the versions:
Jira Cloud Migration Assistant: 1.9.7
Confluence Cloud Migration Assistant: 3.4.8
App Migration platform allows webhook endpoints to be registered at any time through our APIs or via Atlassian Connect descriptors.
Currently, if the endpoints were changed while a long-running migration is in progress, different events could be delivered to a different set of endpoints.
We are now changing this to have the set of webhook endpoints to be defined at the start of the migration and to keep it consistent until it ends.
App Migration has a convenient way to trigger app migrations on CMAs without forcing the user to create and run a new migration plan every time. This is focused on development experience and it doesn’t take into consideration the selection done on App Assessment and some other constaints.
Starting from JCMA 1.9.8 and CCMA 3.4.8, we are extending that endpoint so you can select which apps to trigger.
To use the new endpoint, you need to send a POST request to the /trigger endpoint with a payload like this:
1
2
3
4
5
{
"includeServerAppKeys": [
"com.atlassian.my.app"
]
}As an example, a curl request would look like this:
1
curl -v -u admin:admin "http://localhost:1990/confluence/rest/migration/latest/app-migration/trigger/e508b1f0-364d-4a0f-8c66-198ac67b2a2b" -H "Accept: application/json" -H "Content-Type: application/json" -d "{\"includeServerAppKeys\":[\"com.atlassian.my.app\"]}"We have now enabled adding a migration path in your app’s connect descriptor, which can make your app migrations more reliable and improve the migration experience for your customers. App migration webhook in connect descriptor will take precedence over event-based registration and is becoming preferred way to declare app migration webhook URLs.
Learn how to add app migration webhook path to your app’s Jira or Confluence connect descriptor →
Updated Connect descriptor JSON schema for both Jira and Confluence now contain the new field cloudAppMigration.migrationWebhookPath. For more details about Connect app descriptors, see:
We’re introducing a new feature to re-run failed or incomplete app migrations, which can be used by enabling a feature flag in:
CCMA version 3.4.7 and above
JCMA version 1.9.4 and above
If an app migration results in a failed or incomplete status, customers and Marketplace Partners can re-run the migration for apps individually without having to create a new migration plan.
We've added a section to the migration readiness checklist page for checking your migration path. If you've built an automated migration path for your app, check it's not on the install-only list, otherwise your migration code will be skipped.
We are excited to announce following 2 new app related pre-migrations checks are now also available in JCMA v1.9.0 and above. Customers will be able to proceed with the migration if either of these checks fails.
Cloud app license check
Check to verify if apps can receive migration notification
You can find more details about Atlassian offered app checks at: https://developer.atlassian.com/platform/app-migration/app-vendor-checks/#atlassian-created-app-related-checks-running-by-default.
These checks are already available in CCMA v3.4.3 and above.
App vendor checks feature, which was first introduced in JCMA on 7 December 2022, is now publicly released to customers starting with JCMA v1.9.0. This means any checks written and registered by marketplace partners will run for customers by default. For now, these checks are non-blocking even if they fail, migration can proceed.
Read our docs for more information on how to build the pre-migration checks and write effective content for the checks.
Please note, App vendor checks feature is already available for customers in CCMA v3.4.3 and above.
We are excited to announce following 2 new app related pre-migrations checks in CCMA v3.4.3 and above. Customers will be able to proceed with the migration if any of this check fails.
1. Cloud app license check
This pre-migration check verifies that all apps participating in the migration plan have an active cloud app license installed on their cloud site instance. If the license for any of those apps is inactive, customers will be redirected to manage the app license on the cloud site. Free apps will pass the check.
2. Check for apps to verify if apps can receive migration notification
This pre-migration check verifies all apps participating in the migration plan are registered to receive migration notifications. This means the check will pass for the apps that have registered a webhook to receive migration events or apps that don’t require them to function. If this check fails, the customer will be directed to the marketplace partner support portal.
Watch the changelog for future updates when this feature will be available for Marketplace Partners in the Jira Cloud Migration Assistant (JCMA).
You can find more details about Atlassian offered app checks at: https://developer.atlassian.com/platform/app-migration/app-vendor-checks/#atlassian-offered-app-related-checks-that-run-by-default
App vendor checks feature was first introduced in CCMA on 31 January 2023. This is now publicly released to customers from CCMA v3.4.3. This means any checks written and registered by vendor will always run for customers. For now, these checks are non-blocking for customers.
Read our docs for more information on how to build the pre-migration checks and write effective content for the checks.
App vendor check feature allows you to create and run pre-migration checks for your customer’s app migration. This feature of the Cloud Migration Assistant allows you to:
detect and warn your customers about any issues that can affect their app migration
guide them to resolve potential pre-migration issues