Introduction

This section guides you through the process of migrating you Agile Hive DC data to your Jira Cloud instance. This migration takes place alongside the standard Jira Cloud migration. So, most of the work is done by the https://support.atlassian.com/migration/docs/jira-cloud-migration-assistant/ (JCMA). This means, 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/).

But application vendors are required to set up their app’s custom data structure migration outside of the Jira Cloud Migration Assistant. This applies to any custom data structures associated with a server app that are intended for migration to the Cloud.

For Agile Hive, this means at the moment, everything relates to the Project Hierarchy and the PI management require their own migration steps. This is covered in this section as well.

Scope of migration path for Agile Hive

The following data can be migrated / imported into Agile Hive Cloud. Either by the JCMA or afterwards by our custom migration path.

Project hierarchy
Work Hierarchy Links
Agile Hive-specific Custom Fields (excluding fields related to PIs and Teams)

The following data can not be imported into Agile Hive Cloud yet. Neither the JCMA, nor our custom migration path are able to import these, but should be supported in the future:

Planning Intervals and Iterations
Teams Involved (DC) customfield will not be mapped to Assigned Units (Cloud) yet
PIs Involved (DC) customfield will not be mapped to Assigned PIs (Cloud) yet

A more in-depth explanation of what’s migrated, see https://agilehive.atlassian.net/wiki/x/B4C7Ng.

Agile Hive Migration Guide

For a step-by-step guide on how to migrate Agile Hive data alongside the JCMA migration and with our custom migration path, follow the steps outlined on Agile Hive Migration Guideline .

It will help you to prepare your data on the Agile Hive Data Center instance, as well as install the Jira Cloud Migration Assistant, which is a required app for the migration from Data Center to Cloud. It will handle basic Jira data like work items (issues), spaces (projects), customfields, workflows etc.

The second section will prepare the Jira Cloud instance, you want to migrate to. It guides you on setting up Agile Hive Cloud and also our Agile Hive Cloud Migration Helper App, a required private application for mapping of Agile Hive customfields and work item hierarchy.

After the preparation phase, we’ll guide you through the JCMA workflow until you actually migrate your instance data.

As the last step, the section will guide you through the manual steps required for our custom data migration process. For now, this is the import of the Project Hierarchy from Data Center into Agile Hive 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.

Additional information

Current status for Agile Hive

Update Jan 29, 2026

We released an update to Agile Hive Cloud that migrates project hierarchy data from DC to Agile Hive Cloud. Please note that spaces and work items must be migrated in advance to ensure that the hierarchy property can be set correctly.

You can find this new feature in the Agile Hive Administration. ( Import DC Project Hierarchy into Agile Hive Cloud )

Update Jan 29, 2026

We released an updated Agile Hive Cloud Migration Helper app that migrates project hierarchy data from DC to Agile Hive Cloud. Please note that spaces and work items must be migrated in advance to ensure that the hierarchy property can be set correctly.

Update Oct 10, 2025

We released a new version of the Agile Hive Cloud Migration Helper App, which allows Users to migrate the Planned Start and End Dates for the Agile Hive Roadmaps.

Update Dec 4, 2024

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.

Update Jun 10, 2024

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 Work Hierarchy Link information from Agile Hive Server / Data Center to Cloud. AHCMH app will take care of automatically converting existing Server / DC work item links to the new storage format in Cloud and map all work item links to the corresponding Jira work items.

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 work items). 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 Feb 11, 2026 : We started working on migrating the Planning Interval data from DC to Cloud. As a prerequisite, work items, spaces and sprints must have been migrated already. As well as the migration of the Project Hierarchies from the DC instance must have been done, too.

Update Jan 29, 2026 : We are about to release a new feature in Agile Hive Cloud where it will be possible to import the Project Hierarchy structure from DC into Agile Hive Cloud. As a prerequisite, the standard Jira migration for spaces (projects) and work items (issues) must have been done already, otherwise, the import will not be able to rebuild the hierarchy properly.

After that, work on importing the PIs from Data Center will begin.

Update Dec 4, 2024: 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.

Update Nov 8, 2024: 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.

Information on data procession

For concerns about the procession of data during the migration, see Information on processing of data

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

Migrate to Cloud