General App Documentation
General App Documentation
Breadcrumbs

Cloud Migration Hub: Jupyter Viewer for Confluence

Atlassian is ending support for Confluence Data Center by March 2029.
This page explains how Jupyter Viewer for Confluence 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 Jupyter Viewer for Confluence

Migration effort and automation level

Migration effort: Low / Medium

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

Main risks / limitations

  • Including notebooks from Bitbucket Data Center will not render as we don’t currently support connections from Bitbucket Data Center.

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

Commercial Cloud

info What Jupyter Viewer for Confluence does

Jupyter Viewer for Confluence renders Jupyter/IPython notebooks directly inside Confluence pages.

It supports:

  • Notebook rendering including code cells, markdown, math formulas, and plots

  • Notebooks stored as attachments in Confluence

  • Remote notebooks via URLs (GitHub, Bitbucket, Dropbox, etc.)

  • Interactive visualization of notebook content

🔄 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

Supported versions

  • Supported Confluence Data Center version according to Atlassian migration requirements

  • Jupyter Viewer for Confluence must be installed on Confluence Cloud and configured

Preparation checklist

  • Create a full backup of your Confluence instance

  • Update Jupyter Viewer to the latest DC version

  • Install the Cloud version of app in Confluence

  • Configure the Cloud version if access to private GitHub repositories is required (optional)

  • Identify all pages containing Jupyter macros

  • Review Cloud feature differences

  • Use a test or staging environment for trial migration (recommended)

How the migration works

📖 Migration approach

Recommended: Use Atlassian Confluence Cloud Migration Assistant (CCMA)

The CCMA migrates Confluence content and attachments automatically.

How the migration works

  • Confluence pages migrate via CCMA

  • Notebooks references by URL migrate automatically

  • Notebooks references by attachment migrate automatically

  • Note limitations: Bitbucket DC connections currently not supported

🔢 Step‑by‑step

Step 1 – Prepare on Data Center

  • Verify Confluence and app versions

  • Identify all pages using Jupyter 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 Jupyter Viewer for Confluence (Cloud version) if not installed previously

  • Configure the Cloud version if access to private GitHub repositories is required (optional)

  • Open migrated pages

  • Verify rendering of code, plots, and formulas

  • Inform users that notebooks are available in Cloud

After Migration

🎉 Recommendation for most customers:

We recommend spot checking Jupyter notebook rendering after migration.

Ensure:

  • Attachments are accessible

  • Remote URLs are reachable

  • Authentication for private repositories works

  • Notebook visuals render correctly

🤝 Support & resources

❓ FAQ for Jupyter Viewer for Confluence migration

Can users continue working while migration runs?

We recommend read-only mode for affected spaces during migration to avoid inconsistencies. Users can browse content but macro rendering must be verified after migration.

What is not migrated?

  • Admin configuration for access to private GitHub repositories

What are the biggest changes compared to Data Center?

  • Cloud editor behaves differently

  • Some rendering behaviors may differ

  • Including notebooks from Bitbucket Data Center will not render as we don’t currently support connections from Bitbucket Data Center.

See Feature Parity & Known Limitations.