General App Documentation
General App Documentation
Breadcrumbs

Cloud Migration Hub: Include from GitHub to Confluence

Cloud Migration – Include from GitHub to Confluence

Atlassian is ending support for Confluence Data Center by March 2029.
This page explains how Include from GitHub will be migrated from Confluence Data Center to Confluence Cloud, what you need to prepare, and what you can expect.

🔎 Quick overview

Question

Answer for Include from GitHub to Confluence

Migration effort and automation level

Migration effort: Low
Automation Level: Partially Automated. Install the Cloud version of the app, configure the app then migrate using the Confluence Migration Assistant.

Main risks / limitations

None

Best practices / Key prerequisites

We recommend:

  1. Latest DC version recommended

  2. Confluence Cloud site provisioned and accessible

  3. Cloud app installed and configured

  4. Backup of Confluence Data Center spaces recommended

  5. Test migration in a staging environment suggested

Available Cloud types

Include from GitHub is available for Commercial Cloud

info What Include from GitHub does

With Include from GitHub to Confluence, you can securely include Git files and gists from public or private GitHub repos.

🔄 How to migrate

Please unfold the sections below to view the complete, detailed instructions for the upcoming migration.

By expanding these folders, you will gain access to all the necessary steps and guidelines for a smooth, successful migration.


Before you start

Use this checklist before planning the migration.

Supported versions

Preparation

  • Plan a test migration in a staging environment (recommended).

  • Inform users about a possible short maintenance window.

How the migration works

📖 Migration approach

Recommended: Use Atlassian Confluence Cloud Migration Assistant (CCMA)

Automatic vs manual parts

  • Automatically migrated: GitHub Macros

  • Manually Configure GitHub integrations

  • Must be recreated in Cloud: all other macros such as pull request lists, branches lists, commits lists, and issues macros.

🔢 Step‑by‑step

Step 1 – Prepare on Data Center

  • Verify Confluence and app versions

  • Identify all pages using app macros

  • Backup your instance

  • Optionally run a test migration

  • Communicate timing and impact

Step 2 – Run the migration

  • Start Confluence Cloud Migration Assistant

  • Select spaces for migration

  • Confirm app data policies

  • Run the migration and monitor progress

Step 3 – After migration in Cloud

  • Install Include from Github for Confluence (Cloud version) if not installed previously

  • Configure the Cloud GitHub integrations if not done earlier

  • Open migrated pages

  • Verify rendering of GitHub content in Confluence pages

After Migration

🎉 Validation checklist

  • Confirm GitHub macros display correctly in Confluence Cloud.

🤝 Support & resources

❓ FAQ for Include from GitHub to Confluence migration

Can users continue working while the migration runs?
Confluence migrations are typically planned with a maintenance window to avoid content changes during the run. For app macros, validate pages after the migration.

What is migrated automatically?
Only GitHub macros.

What is not migrated?

Github admin configuration

Are you a solution parter and have questions about licensing during migration?

Contact us via Partner Fast Lane