Last updated Feb 16, 2024

Changelog

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.

16 February 2024

Announcement Increased retention period for exported app data

We've increased the retention period from 5 days to 12 days for all app data exported to the migration platform’s intermediary cloud storage.

Note that we’ve only increased the app data retention period. The overall expiration period for migration transfers is still 14 days.

Learn how to export app data and access it in the cloud

18 January 2024

Announcement Customers can now initiate transfer cancellation

Previously, if customers wanted to cancel an ongoing migration, they would have to contact Atlassian support to cancel it. We have now updated JCMA and CCMA to allow customers to initiate cancellation.

Upon initiating cancellation, the app migration platform will send a new event transfer-cancellation-requested to your cloud app. The cloud app should handle the event and will have 60 minutes to complete any clean-up tasks then settle the transfer.

Learn more about transfer cancellation here

12 December 2023

Added Status REST API: Improved handling of percent progress values

Previously, if the percent parameter wasn't provided to the Send migration progress operation or the value was set to 0, the request would fail when there was a prior update with a non-zero value.

We have updated the Status REST API so that status updates no longer fail when the value of the percent field isn't provided or is set as zero. When there is a prior, non-zero value for percent, that value is retained.

With this change, applications no longer need to track percentages, making it easier to update migration status.

Learn more about reporting migration progress.

17 November 2023

Added Status messages now limited to 300,000 characters

The Status REST API Send migration progress operation now limits the length of the message parameter to 300,000 characters. Values that exceed this limit are truncated to 300,000 characters and appended with this string: <truncated, message too large>.

Learn how to report migration progress

6 October 2023

Announcement App migration resiliency: Guidance on retrying HTTP 5xx responses

We’ve updated our documentation with an important recommendation to retry HTTP 5xx errors instead of allowing a single error to cause an app migration to fail. This recommendation applies to the following REST APIs:

We’ve observed numerous migration failures that could have been prevented if temporary HTTP 5xx errors were retried. These are typically transient service failures, and retrying the request can often lead to successful completion.

4 October 2023

Announcement App workflow rules and custom fields are now compatible with Migrate all data at once

The Migrate all data at once feature in the Jira Cloud Migration Assistant (JCMA) now supports apps that implement workflow rules and custom fields. Starting with JCMA 1.9.17 the feature is enabled by default and no longer behind a feature flag.

Learn more about Migrate all data at once.

18 September 2023

Added Support for re-running unsuccessful app migrations in JCMA

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.

11 September 2023

Added Support for re-running unsuccessful app migrations in CCMA

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.

5 September 2023

Fixed Downloading a report no longer fails when a vendor check status is WARNING

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

9 August 2023

Announcement App Migration Progress Logs in CCMA and JCMA

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:

  1. Information Progress Logs: Expected progress logs that occur during an app migration

  2. Warning Progress Logs: Logs that could impact the success of a migration, like failure to notify your Cloud app of an event.

  3. 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.

28 July 2023

Added Support for App Migrations via JCMA's new "Migrate all data at once" mode has been released

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.

26 July 2023

Added New fields for Marketplace Migration APIs

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

24 July 2023

Announcement Webhook endpoints are now consistent through a single App Migration

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.

11 July 2023

Announcement Extending the /trigger endpoint so individual apps can be selected

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.

More details

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\"]}"

15 June 2023

Added App migration webhook now in Jira and Confluence Connect descriptor

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 →

More details

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:

Rate this page: