Limitations

  • We recommend to use the latest versions of our apps in both, DC and Cloud, when migrating. But please make sure that the installed apps fulfil the minimum version requirements for the migration.

    • For migrating from Jira Data Center 10.3 or higher to Cloud, you require

      • at least Version 4.1.0 of the app in Data Center and

      • Version 7.0.0 of the app on the Cloud instance.

    • The app migration is not supported for Jira Server and Jira Data Center prior to version 10.3.

  • When linking a Confluence Data Center instance as web page, the migration does not change the link. It still points to the Data Center instance, not to a corresponding Cloud instance. When migrating both, Confluence and Jira, simultaneously, you might have to manually adapt the gadgets pointing to Confluence pages afterwards.

  • Currently, the app migration is not idempotent. If the gadgets on a dashboard are migrated multiple times, for each migration new migrated gadgets are added to the Cloud instance of the dashboard.

  • The app migration migrates Custom Content gadgets for all dashboards that are mapped to a cloud instance. As explained in https://developer.atlassian.com/platform/app-migration/mappings/, Jira stores these mappings for up to two years.
    Currently, Jira Cloud Migration Assistant has no way to distinguish whether a dashboard is part of the current migration or the dashboard was only migrated as part of an earlier migration. As a result, the dashboards that were part of earlier migrations might have duplicated gadgets or the app migration might show an error if such a dashboard has been deleted in the meantime. We are in contact with Atlassian to fix this issue as soon as JCMA has a way to distinguish data mappings for earlier migrations.