The process of automated migration depends on whether you're migrating to Connect or Forge. From JCMA (version 1.12.46) or CCMA (version 3.12.0), if you have both listeners defined with the same server and cloud app key pair, then we will invoke the migration path for the app type installed in the cloud. As an example, if you are using any Forge modules in your cloud app and have both a Connect and Forge listener defined in your app, then we will invoke the Forge migration path.

How automated migration works for Connect.

How automated migration works for Forge.

[Preview] Restricted Confluence Space Access

As of 21/July/2026, the platform places the destination cloud site into a temporary migration state while a migration is in progress. During this window, your app can migrate and access data from restricted spaces that are part of the migration. This includes spaces that are restricted to a specific set of users or groups.

This is intended to allow your app to migrate data into or modify data within those spaces to ensure that the migration is successful. The migration state is automatically cleared once the final app migration reaches a finalized state (SUCCESS, FAILED, INCOMPLETE, TIMED_OUT, orCANCELED).

Treat any data read while the migration is in progress as migration-scoped only. Do not retain, surface, or expose restricted content to users who would not otherwise have access to it.