In this article we describe how to migrate Dependency Maps from Jira DataCenter (or Server) to Jira Cloud. (If you want to migrate the other way, you can follow the same process but in “reverse”).
It is quite straightforward to manually create dependency maps in Jira Cloud that are equal in most aspects to the Jira Data Center/Server maps. Here is a step-by-step instruction on how to do this.
Dependency Map Cloud will support a superset of the DataCenter/Server features, with greatly improved usability.
There are still some features in the Dependency Map Data Center/Server that have not yet been implemented in the Jira Cloud version. An example of this is customizing the issue hover content. More information, see the Feature parity checklist below.
If you have any questions, please contact us!
Migration steps
This assumes you have access both to the Jira DataCenter/Server containing the Dependency Maps to migrate, and the Jira Cloud containing the projects you have migrated from Jira Server/DataCenter.
Note: In Jira Cloud, the term ‘Issue’ has been updated to ‘Work item’.
To migrate a map, follow the steps in the table below.
| Jira Data Center/Server | Jira Cloud |
|---|---|
| General settings | |
|
|
|
|
|
|
|
|
|
No choice – Work item type icons are always displayed |
|
There is no Map layout field – the layout is determined by the Rows field and Columns field setting. See below! |
|
|
|
|
|
|
| Issue colors | |
|
|
| Issue content | |
|
|
| Issue hover content | |
|
|
| Links | |
| Link types can be individually hidden/shown by unchecking the link type in the Link type legend in the map. Customize the link type color, line type and width with “Link type” settings. Read more here: https://dependency-map.com/customize-link-styles/ | |
| Advanced layout settings | |
| Custom grouping replaces the Columns/Rows advanced layout settings, allowing for merging/renaming field values. Read more here: https://dependency-map.com/custom-grouping-of-issues/ | |
| Advanced options | |
|
|
|
|
|
|
| The remaining settings are not implemented yet – see the Feature parity checklist. |
Feature parity checklist
Also see the Roadmap for more details.
| Feature | Data Center/Server | Cloud |
| Create map based on Jira issue filter | Yes | Yes |
| Ungrouped layout | Yes | Yes |
| Sections layout | Yes | Planned(1) |
| Columns only layout | No | Yes |
| Issue coloring | Yes | Yes |
| Follow links | Yes | Yes |
| Share maps | Yes | Yes |
| Show/hide links by type | Yes | Yes |
| Freeze row/column headers | No | Yes |
| Show completed issue key as strikethrough | No | Yes |
| Customized issue coloring | Yes | Yes |
| Customized link style | Yes | Yes |
| Edit fields | Yes | Yes |
| Edit links | Yes | Yes |
| Export / print | Yes | Yes |
| Merge field values | Yes | Yes |
| Customized field value merge | Yes | Yes |
| Custom sort order | Yes | Yes |
| Filter rows/columns by field values | Yes | Planned |
| Show sum of numeric field | Yes | Yes |
| Favorites | Yes | Yes |
| Issue hover content | Yes | Yes |
| Manual sorting | No | Planned |
(1): Sections layout is planned for 2026/Q2. For now, create a map with only the Rows field selected. It will automatically be rendered with the Sections layout when the feature is release.
