Migrate to Cloud: Agile Hive Cloud Migration Helper App

Currently it is not possible to automatically migrate Agile Hive data without assistance from our team. Please contact us via the Service Desk.



Introduction

For the purpose of migration it is necessary for us to make use of an external service because Atlassian currently does not currently (Mar 13, 2024) offer a direct migration path from the on premise version of Agile Hive to the Forge version running on Jira Cloud (for more information please refer to ).

To migrate the data we need to first transfer the data to the AHCMH (Agile Hive Cloud Migration Helper) app which is running on Atlassian Connect. The AHCMH app transforms the data into the format required by the Agile Hive Cloud Forge app and writes the data to the target Jira Cloud instance.

Obtaining the Agile Hive Cloud Migration Helper app

AHCMH is available free of charge on request via our Service Desk. Simply raise a new request of type ‘Cloud Migration Agile Hive’ and briefly describe your migration project:

  • Company: Name of your company (for partners: Company that plans to migrate)

  • Cloud Site: URL of the target Cloud site you’re migrating to

  • User: Current Jira Server / DC user tier & Cloud user tier

  • Migration Type: Sandbox or production?

We’ll then provide you with a customized installation link that can be used to install AHCMH in your Cloud target site.

Installation

To install the Agile Hive Cloud Migration Helper app in your Jira site, a Jira Administrator needs to navigate to ‘Manage apps’ in the ‘Apps’ section of Jira Administration. Then, scroll to the bottom of the list of installed apps and click on ‘Settings’. In the modal window, activate the checkbox for ‘Enable private listings’.

image-20240314-105005.png

Then, refresh the page in your browser by performing a reload. After the page has reloaded, click the new button ‘Upload app’ right next to ‘Build a new app’ in the table header.

image-20240314-105404.png

In the modal window, enter the URL you received from the Agile Hive team. Then click ‘Upload’ to install the AHCMH app.

Enabling migration for the Agile Hive app with the JCMA

Unfortunately, it is currently (as of Jun 17, 2024) necessary to use a Dark feature flag in Jira to enable Agile Hive migration.

To enable the Dark feature please follow these steps in your Jira Server / Data Center site:

  1. Navigate to <Jira_instance_URL>/secure/SiteDarkFeatures!default.jspa

  2. Enter migration-assistant.app-migration.dev-mode into the input field

  3. Click “Add” or “Submit”

You can disable the feature after migrating by navigating to the URL in step 1 and deleting the migration-assistant.app-migration.dev-mode key.

Information on processing of data

Here are the most important points in regards to what data is used in what way and which data is stored persistently on an external database:

  • Persistently stored data on an external database

    • the Atlassian Connect framework automatically tracks the Cloud-ID and instance url. This is not controllable on our side

    • we additionally persist the Cloud-ID and the transaction IDs that Atlassian attaches to migration requests to allow better status tracking for debugging as well as continuous operations for larger instances.

    • this is necessary to handle possible duplicate requests and cancellation requests

    • the transaction ID for a migration is deleted once the migration is successfully completed

  • Other customer generated data is non-persistently stored on external services only for the duration of the migration

    • issue data is loaded via a JQL query to specifically identify issues which have a Agile Hive hierarchy issue-link

    • this data is only non-persistently stored in RAM

    • this is necessary for the AHCMH app to transform the data from the on premise format to our Cloud app format and store it in the target Jira Cloud instance

    • this data is only ever accessed when migration requests from the Jira Cloud Migration Platform are sent to the ACHMH App

  • Some meta data is persistently logged for troubleshooting

    • total number of issues to migrate

    • number of issues migrated

    • IDs of migrated issues

    • error information from requests to the Jira Cloud instance

    • this data allows us to identify the scope and possible cause of issues that occurred during migration

    • this data is only accessed for error analysis and performance analysis