Migration to Jira Cloud
Overview
This guide walks you through migrating STAGIL Link Maps for Jira from Data Center (DC) to Cloud. While the core visualization functionality remains consistent, there are some architectural differences between the two platforms that you should be aware of before migrating.
The main difference between DC and Cloud is how saved views work. In DC, the app has its own separate saved views system with custom management. In Cloud, this functionality is replaced by native Jira dashboard gadgets, which integrate directly with Jira's dashboard system for sharing and permissions.
Cloud improvements: The Cloud version includes some enhancements over DC. Link colors can now be configured and saved (not available in DC), and the algorithm for generating hierarchy graph layouts is significantly better and more efficient.
Note: There is currently no automated migration for Link Maps configurations. All project configurations, filters, and saved views need to be manually recreated in Cloud. We are considering adding the ability to export custom views from DC and import them into Cloud dashboard gadgets in a future release.
Many Cloud features are actively being developed to match DC functionality. For a detailed and up-to-date comparison, see the Feature parity: Cloud vs DC (Data Center)
Prerequisites
Before starting your migration, ensure the following:
Latest version of STAGIL Link Maps for Jira is installed on both your DC instance and Cloud site
Jira Cloud Migration Assistant is installed and configured in your DC instance
You have admin permissions on both DC and Cloud instances
Document all existing configurations:
Saved views and their settings
Project configurations
Admin configurations (filters, quick filters)
Custom hierarchy settings
Review the feature parity document to understand current differences
Migration Process
Step 1: Document Your DC Configuration
Since there is no automated migration, thoroughly document your current setup:
Saved Views: For each saved view, note the name, JQL, link types, map type, and node positions
Project Configurations: Document context settings, default preferences, filters, and quick filters
Admin Configurations: Note project sidebar settings and global filters
Custom Hierarchies: If using custom issue type hierarchies, document these settings
Step 2: Run the Jira Migration
Open the Jira Cloud Migration Assistant in your DC instance
Follow the standard Atlassian migration workflow
Your Jira data (issues, links, projects) will be migrated, but Link Maps configurations will not
Step 3: Configure Project Settings in Cloud
Recreate your project configurations:
Navigate to project settings in Cloud
Set up context and default preferences (map type, link levels)
Configure default link types and filters
Set up quick filters as needed
Configure link colors (new Cloud feature)
Step 4: Recreate Saved Views as Dashboard Gadgets
In Cloud, saved views are replaced by Jira dashboard gadgets:
Create a new Jira dashboard or use an existing one
Add the Link Maps gadget
Configure the gadget with your saved view settings (JQL, link types, map type)
Use Jira's native dashboard sharing to manage viewer/editor permissions
Step 5: Verify Your Setup
After configuration:
Test Issue Link Maps from the issue view (right panel and activity tab)
Verify Project Link Maps are working correctly
Check Search Link Maps functionality
Confirm dashboard gadgets display as expected
Test filters and quick filters
Problem Reporting and Support
If you encounter any issues during or after migration, first check the feature parity document to confirm the behavior isn't an expected difference between platforms. If you need further assistance, contact STAGIL Support at support@stagil.com with the following information:
Description of the issue
Screenshots or error messages
Affected projects and configurations
Steps to reproduce
Jira DC version
STAGIL Link Maps for Jira DC version
We're here to help make your migration as smooth as possible!