On this page:
General information
As of , Atlassian does not yet provide an automated migration path for Cloud apps built with Atlassian Forge (such as Agile Hive; https://developer.atlassian.com/platform/forge/). Automated migration paths are only available for apps built with Atlassian Connect. For the latest information on automated migration paths for Forge apps please see https://jira.atlassian.com/browse/MIG-771.
Application vendors are required to set up an application migration path distinct from the Cloud Migration Assistant. This applies to any custom data structures associated with a server app that are intended for migration to the Cloud. It's important to note that basic Jira data will be transferred for all apps as part of the overall Jira system migration process.
Scope of migration path for Agile Hive
For Agile Hive Data Center (as well as Agile Hive Server) there are several data structures that cannot be migrated automatically using JCMA (Jira Cloud Migration Assistant) yet. Those include:
Project hierarchy
Issue Hierarchy Links
PI & Iteration information
Agile Hive-specific Custom Fields
Current status for Agile Hive
The development team is currently evaluating potential solutions for migrating Agile Hive-specific data structures like the ones mentioned above. As it is not possible to directly migrate from DC to a Forge app, we need to come up with a workaround. The team is testing some ideas at the moment and will most likely be able to provide more information around early November 2023.
Our current plan is to have a migration path available for Agile Hive DC to Cloud (including the data structures listed above) by the end of 2023.
In case you have individual questions originating from the migration project in your company or need help with an ongoing migration, please feel free to contact us via our service desk.
Link to this page: https://seibert.biz/ahc-migrate