/
Migration to Confluence Cloud

Migration to Confluence Cloud

Overview

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

Due to Confluence Cloud platform limitations, it is not possible to use Confluence application links with Jira. Instead, the Jira connection is configured through a custom OAuth 2.0 integration in the app admin page. In Cloud, you can choose between view and edit permissions based on the current user, or enable view permissions based on a technical user.

The limitations to be aware of:

  1. The following fields will not be migrated to Cloud:

  • Key (displayed by default)

  • Updated and Summary (not supported in Cloud)

  1. The following fields in macros will not be migrated to Cloud:

  • Type, Priority and Updated (not supported in Cloud)

  • Any other custom field (not supported in Cloud)

  • The "All fields with values" option (this functionality is available only for PDF export in Data Center)

  1. Page Restrictions:

  • The technical user used to connect Jira and Confluence Cloud must have ‘Can View’ or ‘Can Edit’ permissions on the corresponding pages in Data Center. Otherwise, synchronisation will not occur.

  1. CQL limitations:

Some CQL queries may require manual adjustment after migration, including queries that reference:

  • IDs (for example: ancestor, id, parent)

  • $username (mentions)

This is because the IDs and usernames in the Cloud environment differ from those in Data Center.

  1. The “Hide unreleased version from users without edit permission” setting is not available in Cloud (Page Restrictions configuration) and therefore will not be migrated.

  2. The “Jira user” field is not available in Cloud (Synchroniser configuration) and therefore will not be migrated.

  3. Synchronisation of page labels to issue labels is not available in Cloud. Therefore, labels will not be migrated to Jira issues.

There are also differences in display styles and some new Cloud-only features like Fields history and Document search. For a detailed comparison, see the https://stagil.atlassian.net/wiki/spaces/SWFC/pages/3566141460

Prerequisites

Before starting your migration, ensure the following:

  • Latest version of STAGIL Workflow and Fields is installed on both your DC instance and Cloud site.

  • Confluence and Jira Cloud Migration Assistant is installed and configured in your DC instances.

  • You have admin permissions on both DC and Cloud instances.

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

Migration Process

Step 1: Prepare Your DC Instances

  1. Ensure your STAGIL Workflow and Fields DC app is up to date

  2. Note any features that may differ in Cloud (refer to the feature parity document)

Step 2: Run the Migration

  1. Migrate your Jira instance first using Jira Cloud Migration Assistants

  2. Migrate your Confluence instance using CCMA once Jira migration is completed

  3. Follow the standard Atlassian migration workflow

Step 3: Configure Jira Connection

After migration, set up the Jira connection in Cloud:

  1. Install the STAGIL Workflow and Fields app on your Confluence Cloud instance

  2. Go to the Jira Space Synchronizers page.

  3. Configure Jira Connection following this guide: Administration

  4. Use the user who will act as the technical user for the synchronizers. Make sure this user has access to all relevant Jira projects and Confluence spaces.

Step 5: Verify Your Data

After migration completes:

  1. Verify page-to-issue links are working correctly

  2. Test sync configurations are functioning as expected

  3. Check field display and editing on pages

  4. Review transition on page edit functionality

Problem Reporting and Support

If you encounter any issues during or after migration, first check the feature parity document to confirm the behaviour 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 Confluence spaces and pages

  • Steps to reproduce

  • Confluence DC version

  • STAGIL Workflows and Fields DC version

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