Migration to Jira Cloud

This guide walks you through migrating STAGIL Assets for Jira from Data Center (DC) to Cloud. While the core functionality remains consistent, there are some architectural differences and feature changes between the two platforms that you should be aware of before migrating.

Important changes to note:

• Third-party integrations work differently in Cloud. In DC, integrations used hidden links functionality in Jira. In Cloud, integrations are available through the REST API as advanced link fields, or alternatively, you can base advanced links on default Jira link types through link storage configuration.

• Traffic Lights is now a separate app on Cloud — install STAGIL Traffic Lights for Jira if you need this functionality

• User Time Account & Required User Work Log has been deprecated and is not available in Cloud

• QR codes cannot be migrated because the instance URL changes — you'll need to regenerate them after migration

• Panel settings are not available in Cloud due to platform limitations

There are also differences in display styles, synchronization options, supported JQL variables, name of the JQL function, and available project templates. For a detailed comparison, see the https://stagil.atlassian.net/wiki/x/BQCQ1

In Jira Data Center, advanced links created by the app are stored as standard Jira links. Because of this, when JCMA migrates data from Data Center to Cloud, it correctly migrates these links as default Jira links.

In Jira Data Center, advanced links created by the app are stored as standard Jira links. For this reason, when JCMA migrates data from Data Center to Cloud, these links are migrated as default Jira links. During the migration process, our app automatically detects these default links and converts them into advanced links in Jira Cloud. As part of this process, the original default links are removed.

This conversion happens:

• per work item

• sequentially

• within Jira Cloud API limits

For small instances, this completes quickly. In large instances, this phase can take a significant amount of time and may cause early progress indicators to appear unchanged, even though the migration is actively running.

Automated migration path via JCMA end-to-end is suitable when:

• the number of work items is limited

• link volume is modest

• migration is expected to complete within hours

Manual migration is recommended for large instances. Typical indicators:

• very high work item count

• high number of links per work item

This approach still uses JCMA to migrate core data, but the link configuration is imported manually. Then, a built-in tool converts default links into advanced ones.

Before starting your migration, ensure the following:

• Latest version of STAGIL Assets 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

• If using Traffic Lights functionality, install STAGIL Traffic Lights for Jira separately on Cloud

• Document any QR code configurations (these need to be regenerated after migration)

• (Optional) Issue Security: If you use issue security levels, ensure the STAGIL app has access to secured issues before running the migration. You can either remove issue security before migration, or manually recreate the security scheme in Cloud and add the Space Role atlassian-addons-project-access to it before the automated migration runs

• Check if the issue link limit is not exceeded: Jira Cloud enforces limits on the number of issue links per work item. During migration, issues are first migrated with default Jira links, which are then converted into advanced links by JCMA as part of the migration process. If an issue exceeds link limits at this stage, some links may not be migrated. Learn more here.

• Review the feature parity document to understand any differences that may affect your workflows

1. Ensure your STAGIL Assets for Jira DC app is up to date

2. Document your current configurations, especially:

   • Advanced link field settings

   • Issue filter panel configurations

   • Project sync settings

   • Third-party integrations using hidden links

   • Any QR code usages

3. Note any features that may differ or be unavailable in Cloud (refer to the feature parity document)

If you use issue security levels:

1. Manually recreate the security scheme in your Cloud instance

2. Add the Space Role (atlassian-addons-project-access) to the security scheme

3. This ensures the app can access secured issues during and after migration

1. Open the Jira Cloud Migration Assistant in your DC instance

2. Follow the standard Atlassian migration workflow

3. STAGIL Assets for Jira data will be included automatically as part of the migration process

After migration, some features require manual attention:

Third-Party Integrations: If you used third-party integrations via hidden links in DC, reconfigure them in Cloud using either the REST API (accessing advanced links as fields) or by setting up link storage to sync with default Jira link types.

QR Codes: Regenerate all QR codes in Cloud, as the old ones contain DC instance URLs that are no longer valid.

Traffic Lights: If you were using Traffic Lights functionality in DC, install and configure the separate STAGIL Traffic Lights for Jira app on Cloud.

Display Styles: Some display styles (Label, Popup variants) are not available in Cloud. Review and adjust affected configurations to use Table, List, or Hierarchy table styles.

Synchronization: User sync and Version sync are not available in Cloud. If you relied on these features, consider alternative workflows.

After migration completes:

1. Spot-check Advanced link fields across different projects

2. Verify Issue filter panels are displaying correctly

3. Test Asset navigator functionality

4. Confirm project sync is working as expected

5. Review any JQL-based configurations for unsupported variables

6. Review any usage of JQL function and replace it with “issue in link()” instead of “issue in relation()”

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 project and field details

• Steps to reproduce

• Jira DC version

• STAGIL Assets for Jira DC version

We're here to help make your migration as smooth as possible!