Migrate Advanced Roadmaps plans

The Jira Cloud Migration Assistant allows you to migrate your Advanced Roadmaps plans including issue sources such as projects and single-project boards from Advanced Roadmaps server to cloud. Learn how you can use the Jira Cloud Migration Assistant to migrate Advanced Roadmaps plans.

Advanced Roadmaps plans migration is currently under development. When you migrate, not all data will be migrated to your cloud site.

What is migrated and what isn’t migrated

Supported Advanced Roadmaps version

Make sure you’ve installed the right Advanced Roadmaps plans version:

• For JSW DC 8.15 and higher, it’s the corresponding bundled version of ARJ.

• For JSW DC 8.14 and lower (and Jira Core and JSW Server), it’s 3.17.0 or higher.

Recommendation about Advanced Roadmaps migration strategy

1. If you’re planning to migrate in multiple phases, for example, if you want to migrate Jira Software projects today and Advanced Roadmaps plans tomorrow, we recommend you:

   1. First, migrate Advanced Roadmaps plans. All associated projects, boards, filters (except private filters), permissions, and users and groups will be migrated along with the plans.

   2. Next, migrate all other projects, if you plan to do so.

2. If you update issue sources or cross-project releases while migrating, the latest updates won’t be migrated. We recommend you don’t update issue sources and cross-project releases once you decide to migrate.

   If you update issue sources, you will have to run the migration again to migrate the changes to the plans.

   If you update cross-project releases, you will have to first delete them on your destination cloud site and then run the migration again to migrate the changes to the plans.

3. Unsaved scenarios won’t be migrated, so we recommend you save your all scenarios before migrating.

4. When Advanced Roadmaps is installed, and you migrate your issues from your Server or Data Center instance, epic links from custom issues at and above the epic (or custom epic) don't get migrated. Learn about the differences between both the issue hierarchies.

To view the affected issues:

1. Download the CSV file from the warning under the Project section of the Check for errors screen.

2. View the list of affected issues and update the corresponding epic links.

To maintain the epic link information during migration, follow one of the following approaches:

• If your epic link data is important to maintain, you can move any affected issue types to the base level in your issue hierarchy.

• If your issue hierarchy is important in its current form, you can add the epic as a linked issue.

If your epic link data is important to maintain, you can move any affected issue types to the base level in your issue hierarchy.

1. In the navigation bar, select Plans > Administration, and then choose Hierarchy configuration from the sidebar.

2. Locate and deselect the affected issue type(s) under the Jira Issue Types column, and select Apply. This will remove the issue type from its current level.

3. Select Save changes.

If your issue hierarchy is important in its current form, you can add the epic as a linked issue.

You can maintain your epic relationships by changing them to different relationships using linked issues.

1. Open the issue that you want to link to.

2. Select More > Link.

3. In the Link window, select Jira Issue. 

4. Select the type of issue link. For example, for This issue, select ‘relates to.’

5. Specify the issue(s) you want to link to by doing one of the following:

   • Type the full issue key. For example, type ‘TRYPROJ1-2’.

   • Select search for an issue to perform a text search or an advanced search.

6. Add a comment to describe why you're linking these issues and select Link.

7. Select Epic Link and remove the epic.

Before you begin

Make sure you have Jira Work Management added in your destination Cloud site if you have Jira Work Management in your Server instance. Depending on the number of Jira Work Management users you've in your Server instance, you may need to upgrade to the Jira Work Management Standard plan.

Post-migration tasks

When you finish migrating your Advanced Roadmaps plans using the Jira Cloud Migration Assistant, you’ll need to configure your default start and end dates in your cloud site.

In server, the default start and end dates for your plans are Target start and Target end date. In cloud, the default start and end dates are Start date and End date.

If you are using default start and end dates in server, after you migrate, the dates won't appear in cloud because the default fields are different. To resolve this, you'll need to configure the default start and end dates to be Target start and Target end in your cloud site.