Documents to help you prepare to migrate your Atlassian Server products.
A collection of topics that help prepare you to migrate your apps to the Cloud.
Ensure you’re ready to migrate with these pre-migration checklists for Jira, Confluence, and Bitbucket Server or Data Center.
Documents that walk you through using the Confluence Cloud Migration Assistant to migrate to Cloud.
Documents that walk you through using the Bitbucket Cloud Migration Assistant to migrate to Cloud.
Documents to help you use Jira Site Import to migrate to Cloud.
Resources to help get started and testing after you migrate.
Everything you need to know about moving your data from one cloud site to another.
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
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
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:
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.
Next, migrate all other projects, if you plan to do so.
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.
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.
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.
Was this helpful?