Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Next »

General information

Atlassian initially did not provide an automated migration path for cloud apps build with Forge (such as Agile Hive; https://developer.atlassian.com/platform/forge/). Automated migration paths were only available for apps built with Atlassian Connect. Even though on , Atlassian released a migration path for Forge apps, a large time invest already was being made to provide a stable migration path with our separate Agile Hive Migration Helper app.

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 (see https://support.atlassian.com/migration/docs/what-gets-migrated-with-the-jira-cloud-migration-assistant/).

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. As of , our custom migration path is able / not able to handle the data structures listed below:

  • (error) Project hierarchy

  • (tick) Issue Hierarchy Links

  • (error) PI & Iteration information

  • (tick) Agile Hive-specific Custom Fields (excluding fields related to PIs)

For more detailed information, please refer to the sections https://agilehive.atlassian.net/wiki/spaces/CLOUD/pages/550633474/Migrate+to+Cloud#Current-status-for-Agile-Hive and https://agilehive.atlassian.net/wiki/spaces/CLOUD/pages/550633474/Migrate+to+Cloud#Migration-Path-Roadmap right below.

Current status for Agile Hive

Update

We released a new version of the Agile Hive Cloud Migration Helper App, which allows big instances to migrate a large amount of data and also migrates custom fields (excluding PI-related fields). Due to a lot of technical and infrastructural changes, the app must be installed with a new URL. So if you already have access to the Migration Helper App, make sure to request a new installation link.

 Previous updates

Update

The development team has finished setting up the foundation for migrating Agile Hive Server / DC related data structures to the Cloud counterpart. Since Atlassian currently does not yet provide a direct migration path for Forge apps, we’ve set up a dedicated Agile Hive Migration Connect app in the Cloud with the single purpose to receive data from the Server / DC app using JCMA. This basic setup has already been released privately (see Agile Hive Migration Guideline for more information on how to request the migration helper app).

With the current version of Agile Hive Cloud Migration Helper (AHCMH) app it is possible to migrate Issue Hierarchy Link information from Agile Hive Server / Data Center to Cloud. AHCMH app will take care of automatically converting existing Server / DC issue links to the new storage format in Cloud and map all issue links to the corresponding Jira issues.

For the upcoming version of AHCMH app, we’ve already started extending the migration path to handle Agile Hive-specific Custom Field data. We’re currently working on preparing our migration infrastructure to handle large sets of data (tens of thousands of issues). After this, we’ll start mapping the Custom Field data migrated from Server / DC to the corresponding fields of the Cloud app.

Migration Path Roadmap

Update : We have released an updated version of the Agile Hive Cloud Migration Helper app, which now includes support for migrating Agile Hive-specific Custom Fields. Additionally, we've enhanced the stability and performance of the overall migration process for Agile Hive. We will begin assessing this latest version with our customers who are currently migrating to the Cloud, and will plan our future actions based on this evaluation.

We’ll keep you updated on our progress in our Public Review once a month - You are invited to join us there to discuss the timeline for your company's migration project.

 Previous updates

Update : Due to high levels of complexity we decided to postpone migration of Project Hierarchy and PI Data and focus on improving stability and performance of the current version of our custom migration path. However, we will continue to evaluate ways of migrating project hierarchy as well as PI data from Server / DC sites to Cloud.

Get support

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.

Also, the pages listed below might help you when actively migrating data from Jira Server / Data Center to a Cloud site:

Link to this page: https://seibert.biz/ahc-migrate

  • No labels