Skip to main content
Skip table of contents

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.

Migration Assistant support is not available yet

We are actively working on support for Migration Assistant. Once released, GitLab macros will be carried over automatically during migration. Until then, please follow the manual procedure below.

Prerequisites

Before you start, make sure you have:

Migration Steps

Step 1. Migrate your Confluence content to the Cloud

To start this journey, it is recommended to use Cloud migration methods for Confluence to ensure a successful migration.

If you use Atlassian Migration Assistant, go to Confluence administration → General configuration → Migration Assistant and run the Confluence Cloud Migration Assistant for your spaces, pages, users and attachments.

After the Migration Assistant runs:

  • All your pages, spaces, and attachments will be available on Cloud.

  • Any GitLab macros embedded on these pages will appear as unknown or unrendered macros in Cloud because they haven't been automatically migrated yet. They must be recreated manually (see Step 3).

Step 2. Configure the GitLab integration in Confluence Cloud

As a Confluence administrator, connect your Confluence Cloud instance to your GitLab instance.

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

Step 3. Recreate GitLab macros on the migrated Cloud pages

Because GitLab macros are not yet migrated automatically, on each Cloud page that previously contained GitLab content, you'll need to:

  1. Edit the page in Confluence Cloud.

  2. Remove the unknown/unrendered Data Center macro placeholder.

  3. Insert the equivalent GitLab for Confluence (Cloud) macro (type / and search "GitLab").

  4. Configure it with the same parameters as the original macro.

  5. Publish the page.

Important considerations

  • Macro feature parity. Not all macros available on the Data Center version are currently supported on Cloud. Please review the differences article before migrating.

  • Configuration parameters differ. The available fields and options for each macro on Cloud may differ from Data Center. Adjust the macro settings to match your intended display.

  • Authentication model differs. On Data Center, GitLab can be connected at two levels using a Personal Access Token: global (configured by an administrator and used by everyone) and personal (configured by individual end users so they only see GitLab content they have access to). On Cloud, GitLab can be connected only at the global level, using a Personal Access Token configured by a Confluence administrator.

Need help?

If you have any questions or need help with migration, please contact our Support Team. Our dedicated team will answer all your questions and expertly guide you through the entire migration process.

Updated:

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close