How to Upgrade apps from Confluence 3.x to 4.x and Above?

Owned by Robert Alexander Marshall
Last updated: Oct 12, 2023 by Robert Alexander Marshall
2 min read
1 Take it step by step | 2 Upgrade instructions for each app | 3 Safety Upgrade Paths for Confluence with Composition, Scaffolding, and Reporting | 4 What if I'm only updating Composition, Scaffolding, or Reporting? | 5 What about other related apps? | 6 Unmigrated wiki markup content

Take it step by step

After you upgrade Confluence, pages that contain related apps, specifically Composition, Scaffolding, and Reporting macros may render incorrectly.

If you are upgrading Confluence to v4.3 and above, there might be some problems with the Wiki Markup migration if you upgrade directly from Confluence v3.x to the latest version.

It is recommended instead to upgrade Confluence version by version so that your data can be maintained.

Refer to the Confluence safety upgrade steps below to ensure all Wiki Markup data are migrated completely.

Upgrade instructions for each app

Before upgrading Confluence

  • go to Confluence Administration → Apps

  • disable the related app(s)

  • upgrade Confluence

You can upgrade the apps via the following methods:

  • Download the .obr files for each app from the Atlassian Marketplace

  • upload it via:

    • Confluence Administration → Apps→ Upload app

    • Confluence Administration → Apps → Upgrade

  • Enable the app(s)

Safety Upgrade Paths for Confluence with Composition, Scaffolding, and Reporting

Upgrade Confluence v3.x → Confluence v3.5.x with

  • Composition 2.3.5, Scaffolding 3.4.2, Reporting 3.4.2

Upgrade Confluence v3.5.x → Confluence 4.2.x with

  • Composition 3.0.3, Scaffolding 4.0.4, Reporting 4.1.0

Upgrade Confluence v4.2.x → Confluence 4.3.x with

  • Composition 3.0.3, Scaffolding 4.6.5, Reporting 4.1.0

Upgrade Confluence v4.3.x → Confluence v5.8.x with

  • Composition 4.0.0, Scaffolding 6.3.0, Reporting 5.3.0

While on Confluence 5.8.x, upgrade according the following upgrade path

  • Composition 4.0.0 & Scaffolding 6.3.0 & Reporting 5.3.0 → Composition 4.0.0 & Scaffolding 6.3.0 & Reporting 5.8.1 → Composition 5.0.0 & Scaffolding 8.0.0 & Reporting 6.0.0 → Composition 5.9.1 & Scaffolding 8.8.0 & Reporting 6.6.0

On Composition ≥5.0.0, Scaffolding ≥8.8.0, Reporting ≥6.6.0, uninstall all older dependencies which are not required by modern version of Composition, Scaffolding, and Reporting. You can refer to this on the App Dependencies page.

Upgrade Confluence v5.x → Confluence v6.x with

  • the latest compatible version of Composition, Scaffolding, and Reporting

What if I'm only updating Composition, Scaffolding, or Reporting?

You can check out the following Knowledge Base on each respective ServiceRocket add-ons:

The rest of the apps do not have require a specific upgrade path, as they don't acquire large portion of Wiki Markup content compared to Composition, Scaffolding, and Reporting.

Unmigrated wiki markup content

Confluence might not be able to migrate some Wiki Markup content due to various reason.

The most commonly encountered issue is the complicated structure on a page, which causes some part or whole Confluence page to not be migrated. When this happens, you can try the following solutions

  • rebuild the Confluence Index through Administration → Content Indexing → Rebuild both

  • running a force migration on Confluence - you can check the specific steps in the Atlassian documentation

  • manually migrate the Wiki Markup Content by using the inserting Wiki Markup function on Confluence - access it via CTRL + SHIFT + D or Insert Macro → Insert Markup