Changelog

A new RFC is ready for review at: https://community.developer.atlassian.com/t/rfc-118-cloud-to-cloud-identifier-mapping/96871

Starting from CCMA 3.13.1 and JCMA 1.12.47 and `atlassian-app-cloud-migration-listener` version 1.8.7, you can use the Object Store data plane to migrate data into Forge Object Store from Server/DC.

See Forge Object Store migration documentation

AppDataListResponse in the Forge migration API has been updated to match the actual response.

Previously, the definition didn't match the API response, which could cause cast errors or undefined object errors when accessing response fields. This fix ensures the response structure is consistent with the API documentation, so the API can be effectively used to migrate apps from Server or Data Center to Cloud.

If you were using the previous definition, you may see a compile error after updating. To resolve this, change any usage of response.result to response when calling this API.

Starting with JCMA 1.12.46 App Data Only migrations will be available. See exp-app-data-only-migration for more details.

Starting with CCMA version 3.11.16 we now support migrating Confluence Server Macros directly to Forge Macros. See p2-to-forge-macros for more details.

Building on top of our previous announcement about Forge Storage, starting from JCMA 1.12.42 (CCMA coming soon), App migration can automatically update server ID references to their respective cloud equivalent as part of the migration pipeline.

Learn more about it at Data transformers.

Starting from JCMA 1.12.36 and CCMA 3.11.13, we are offering, in early access, a new feature that allows you to migrate data directly into Forge Storage.

We are starting with Key-Value Store and Custom Entity Store. Soon, we should have coverage for other Forge Storage data planes.

Read more about it at Key-Value Store & Custom Entity Store

Starting from JCMA 1.12.37 and CCMA 3.11.12, apps can now define up to 7 app vendor checks, up from 3.

Following our announcements on Support for Multi Transfers, we are pleased to announce that starting from CCMA 3.11.9, Multi Transfers will also be available for Confluence apps.

Starting from JCMA 1.12.27, apps will have more flexibility about how they organise and report on the transfer progress.

Currently, no matter how big or complex your app’s migration path is, each migration will receive a single transfer to both operate and to report statuses updates. Furthermore, in the event of a retry, the whole data export and import process is restarted.

Multi transfers adresses these scenarios by nesting multiple transfers that can be independently managed. They also enable the developer to identify where there’s a dependency between them and to flag what transfers can be completed in the background without blocking the customer’s migration downtime.

Soon, we’ll be delivering this for Confluence migrations through CCMA, and then there will be a new announcement.

We have introduced a message size limit for the logMessage string parameter in the addLog Forge API. The maximum allowed size for messages are 65,536 characters. Log messages exceeding this limit will be truncated by the app migration platform.

Starting from @forge/migrations 1.0.5 If you encounter an unrecoverable error during app data processing in Forge app migrations, you can call migration.messageFailed(transferId, messageId) to fail the migration early (this will immediately settle the transfer as FAILED for users) instead of letting the transfer time out.

Please ensure adequate logging is added for users, to help them understand and remediate issues with migration.addLog(transferId, "your log message").

A new RFC is ready to review at https://community.developer.atlassian.com/t/rfc-80-app-migration-multi-transfers/87348

Starting from Jan 6, 2025 , the App Migration Platform will be filtering out some events for Atlassian Connect that are not actionable.

For now, the only event to be omitted is app-data-uploaded strictly during scenarios in which the data can no longer be retrieved, such as when the transfer has been marked as settled.

Please note that even before this change, if an app tries to retrieve the data for a settled migration, an error will occur.

Starting from JCMA 1.12.15, customers will be able to identify when an app migration has done migrating its critical part hence enabling them to start using the cloud instance.

This feature is expected to reduce up to 60% of the migration downtime on selected apps.

We are now exploring how to extend this feature to make it self-serve for all the migrating apps.