Migration path from On-Premises to the Cloud for GitLab for Confluence

This documentation provides information on how to migrate from the GitLab for Confluence from Data Center app to Cloud.

Before starting your migration, make sure you review the prerequisites and any differences between the Data Center and Cloud versions of the app.

Prerequisites

Before you start, make sure you have:

• A Confluence Data Center instance with GitLab for Confluence (Data Center) installed and configured.

• A Confluence Cloud instance with GitLab for Confluence (Cloud) installed.

• Administrator permissions for both the Confluence Data Center and Confluence Cloud instances.

• Access to your GitLab instance, whether you use GitLab.com or a self-hosted, internet-accessible GitLab instance.

Migration Steps

Step 1. Prepare GitLab for Confluence on Confluence Cloud

Before migrating your Confluence content, ensure that GitLab for Confluence (Cloud) is installed on your Confluence Cloud instance.

You should also review the Cloud setup requirements and configure the GitLab integration as required.

For the full step-by-step procedure, see the GitLab for Confluence (Cloud) setup guide.

Step 2. Migrate your Confluence content to Cloud

Use Atlassian Migration Assistant to migrate your Confluence content from Data Center to Cloud.

To access Migration Assistant, go to Confluence administration → General configuration → Migration Assistant and run the migration for the required spaces, pages, users, and attachments.

During the migration, supported GitLab for Confluence macros are migrated automatically.

After the migration is complete:

• Your migrated pages, spaces, and attachments are available in Confluence Cloud.

• Supported GitLab macros are migrated to their Cloud equivalents automatically.

• You do not need to manually remove and recreate supported GitLab macros on each migrated page.

Step 3. Review your migrated content

After completing the migration, review your migrated Confluence content to confirm that your GitLab macros are displayed and configured as expected.

If you need to adjust a migrated macro, you must recreate it by inserting a new GitLab for Confluence Cloud macro and configuring it with the required settings.

Important considerations

• Macro feature parity.
  Not all macros and features available in the Data Center version are currently supported on Cloud. Before migrating, review the differences between the Data Center and Cloud versions to understand any feature limitations.

• Configuration and macro parameters.
  The available fields and options for macros on Cloud may differ from those available on Data Center. After migration, review your macro configuration and adjust settings where necessary to achieve the intended display.

• Authentication model.
  The authentication model differs between Data Center and Cloud.

  On Data Center, GitLab can be connected at two levels using a Personal Access Token:

  • Global connection, configured by an administrator and used by all users.

  • Personal connection, configured by individual users so they can access GitLab content according to their own permissions.

• On Cloud, the available authentication method depends on your GitLab environment:

  • For GitLab.com (SaaS), GitLab for Confluence Cloud can be connected using OAuth.

  • For other supported GitLab environments, GitLab can be connected at the global level using a Personal Access Token configured by a Confluence administrator.

• Before migrating, review the available authentication options and ensure that the GitLab integration is configured appropriately for your environment.

Need help?

If you have any questions or need help with migration, please contact our Support Team. Our dedicated team can help you with the migration process and answer any questions you may have.

Updated: 2026-08-13