...

...

1. Go to “System” and under “Import and Export” go to “Migrate to cloud”

2. Under “Assess” click “Begin assessing” and make sure to select “Needed in cloud” for Agile Hive Suite

3. Under “Prepare” click “Begin preparing” and then “Choose cloud site”

4. For “Migrate from” enter you base URL of the server instance and choose the destination cloud site in “Migrate to”

5. Check the “Allow Atlassian to access migrations data to perform your migration” checkbox and click “Confirm”

6. Back in the previous screen in “Connect to cloud”, choose the authorized cloud site from the dropdown menu and click “Continue”

7. Under “Install” Agile Hive may not appear as a required app for cloud (because as of 05 Dec 2024 Atlassian cannot handle privately listed apps, see this issue https://jira.atlassian.com/browse/MIG-1787), so just click “Continue” again

8. Under “Agree” Agile Hive should show up and the policy needs to be agreed

9. Click “Done”

10. Assess and prepare users and email domains according your needs, and maybe migrate your users in advance

11. Create a new migration

12. Provide a unique name for the migration, choose migration stage (Production or Testing) and make sure your target cloud site is selected

13. In the next step, select “Choose what to migrate” and select Projects according to https://agilehive.atlassian.net/wiki/spaces/CLOUD/pages/614268930/Agile+Hive+Migration+Guideline#General-migration-guidelines-%2F-advice

14. For “Advanced Roadmap plans”, “Dashboards, boards and filters” and “Users and groups” select options according your needs (data related to the project should be sufficient)

15. Make sure to select Agile Hive (or the option “All”) under “Apps” and click “Run pre-migration checks”

16. Fix potential errors in the list and click “Review migration” afterwards click “Run”

17. Back in the migrations dashboard, you can click on “View details” to examine the progress of the migration even further.

...

Manual migration steps

After a successful migration run (for a part of your organization), you need to follow these manual steps to recreate all possible data from your Server / DC instance, as not all Agile Hive data gets migrated automatically (yet):

1. Go to “My organization” and resemble the project hierarchy to match your Server / DC instance (see My Organization for more information)

2. Check and update hierarchical links via ‘SAFe® Hierarchy’ panel in Jira Issue Detail View for individual issues as needed.

3. Adjust your project configuration of Screens, Screen Schemes, and Issue Type Screen Schemes to the Agile Hive default or adjust as needed (see Configure Jira Projects For Use With Agile Hive for additional information on recommended / minimum required configuration).

   1. The “Milestone Date” custom field gets migrated automatically, but is not included in the Screens from Agile Hive Cloud. You can add the migrated field to the desired screens (where the Cloud version of the field should already exist), rename the Cloud field to something else and make sure that your migrated field is called “Milestone Date” (without any “migrated”-suffix). Now the Milestones should also appear in Agile Hive views like the Roadmap or in Reports

4. To maintain your set dependencies from Server / DC, go to the Agile Hive Administration and select the Issue Link Type and Direction that you used before, and click “Save”.

5. Create your PIs as you need for the future

   • If you already had PIs planned for the future on you Server/DC instance, you can recreate the PIs with the same dates in the Cloud Solution Train and/or ART and go to each corresponding team’s Agile Hive project settings to map the iterations created in Cloud with the sprints, that were migrated from Server/DC. You can delete the newly created sprints from Cloud again afterwards
     

After the migration

After all projects are successfully migrated you can do the following things on your Cloud site

• Delete the Issue Link Type, that was used on Server / DC for managing the Issue Hierarchy (as in Cloud, the Issue Hierarchy is managed through issue properties, see Issue Hierarchy) – by default, the Issue Link Type is called “Agile Hive Link”

...

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

...