• Products
  • Documentation
  • Resources

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

What is migrated

What isn’t migrated

  • Plans with issue sources as projects

  • Plans with issue sources as single- or cross-project boards

  • Plans that have issue sources as filters

  • Users and groups

  • Global configuration

  • Custom issue types, custom fields and custom hierarchy mapping

  • Live plans will be migrated as plans with improved interface

  • Classic plans

  • Plans that have issue sources as private filters

  • Unsaved scenario data

  • Saved views

  • User defined custom fields of type

    • Parent Link

    • Team

    • Target start

    • Target end

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.

Before you begin

Make sure you have Jira Work Management in your destination cloud site.

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.


Additional Help