Plan your Cloud migration
Documents to help you prepare to migrate your Atlassian Server products.
How Advanced Roadmaps plans are migrated
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.
Supported version of Advanced Roadmaps
You need to be on the supported version of Advanced Roadmaps:
For Jira Software Data Center 8.15 and higher, it’s the bundled version of Advanced Roadmaps.
For Jira Server or Data Center 8.14 and lower, it’s Advanced Roadmaps 3.17, or later.
What data is migrated
The following data is migrated:
What is migrated | What isn’t migrated |
|---|---|
|
|
How best to migrate Advanced Roadmaps
Here’s a few tips on the best way to migrate Advanced Roadmaps.
Migrate plans separately, before project data
If you’re planning to migrate in multiple phases, for example Jira Software projects today and Advanced Roadmaps plans tomorrow, we recommend that you:
Migrate Advanced Roadmaps plans first. They will be migrated together with all associated projects, boards, filters (except private filters)l permissions, and users and groups.
Next, migrate all other projects.
Don’t make updates during migration
If you update issue sources or cross-project releases while migrating, the latest updates won’t be migrated.
If you update issue sources, you’ll have to migrate the latest changes to the plans again.
If you update cross-project releases, you’ll have to delete them in your destination cloud site, and then migrate the changes to the plans again.
Save scenarios before migration
Unsaved scenarios won’t be migrated, so make sure to save them before migration.
Details about epic links
When Advanced Roadmaps is installed and you migrate issues, epic links from custom issues at and above the epic (or custom epic) don’t get migrated.
How to view the affected issues
To view the affected issues:
Download the CSV file from the warning under the Project section of the Pre-migration checks screen.
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.
How to maintain the epic link data
If your epic link data is important to maintain, you can move any affected issue types to the base level in your issue hierarchy.
In the navigation bar, select Plans > Administration, and then choose Hierarchy configuration from the sidebar.
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.
How to maintain the issue hierarchy
You can maintain your epic relationships by changing them to different relationships using linked issues.
Open the issue that you want to link to.
Select More > Link.
In the Link window, select Jira Issue.
Select the type of issue link. For example, for This issue, select ‘relates to.’
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.
Add a comment to describe why you're linking these issues and select Link.
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, 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.
More information and support
We have a number of channels available to help you with your migration.
For more migration planning information and FAQs, visit the Atlassian Cloud Migration Center.
Have a technical issue or need more support with strategy and best practices? Get in touch.
Looking for peer advice? Ask the Atlassian Community.
Want expert guidance? Work with an Atlassian Partner.
Support for Atlassian Server products ends in February, 2024. Learn more about the Server end of support timeline.
Was this helpful?