/
Migration to Confluence Cloud

Migration to Confluence Cloud

Overview

This guide walks you through migrating STAGIL Tasks for Confluence from Data Center (DC) to Cloud. While the core functionality remains consistent, there are some architectural differences 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. Permissions of the user who created the Jira connection will always be used to view and edit issues in the Confluence page macro.

Important: Jira custom fields configured as columns will not be migrated and need to be reconfigured manually in Cloud.

There are also differences in supported fields, configuration scope, and available features between platforms. For a detailed comparison, see the Feature parity: Cloud vs DC (Data Center)

Prerequisites

Before starting your migration, ensure the following:

  • Latest version of STAGIL Tasks for Confluence is installed on both your DC instance and Cloud site

  • Confluence Cloud Migration Assistant is installed and configured in your DC instance

  • You have admin permissions on both DC and Cloud instances

  • Document any Jira custom fields used as columns (these need manual reconfiguration after migration)

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

Migration Process

Step 1: Prepare Your DC Instance

  1. Ensure your STAGIL Tasks for Confluence DC app is up to date

  2. Document your current macro configurations, especially any Jira custom field columns

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

Step 2: Run the Migration

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

  2. Follow the standard Atlassian migration workflow

  3. STAGIL Tasks for Confluence data will be included automatically as part of the migration process

Step 3: Configure Jira Connection

After migration, you need to set up the Jira connection in Cloud:

  1. Go to the STAGIL Tasks for Confluence app admin page

  2. Configure the OAuth 2.0 integration to connect with your Jira instance

  3. Note that permissions of the user creating this connection will be used for all issue interactions in macros

Step 4: Reconfigure Custom Field Columns

Jira custom fields configured as columns are not migrated. For each affected macro:

  1. Edit the macro configuration

  2. Re-add any custom field columns that were previously configured

  3. Verify the display and sorting settings

Step 5: Verify Your Data

After migration completes:

  1. Spot-check macros across different pages to confirm data integrity

  2. Verify Jira issue display and editing functionality

  3. Test Confluence tasks scope functionality

  4. Confirm sorting and column configurations

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 Confluence pages and macro details

  • Steps to reproduce

  • Confluence DC version

  • STAGIL Tasks for Confluence DC version

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