Excerpt | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||
Take it step by stepAfter 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.
Refer to the Confluence safety upgrade steps below to ensure all Wiki Markup data are migrated completely. Upgrade instructions for each appBefore upgrading Confluence
You can upgrade the apps via the following methods:
Safety Upgrade Paths for Confluence with Composition, Scaffolding, and ReportingUpgrade Confluence v3.x → Confluence v3.5.x with
Upgrade Confluence v3.5.x → Confluence 4.2.x with
Upgrade Confluence v4.2.x → Confluence 4.3.x with
Upgrade Confluence v4.3.x → Confluence v5.8.x with
While on Confluence 5.8.x, upgrade according the following upgrade path
Upgrade Confluence v5.x → Confluence v6.x with
What if I'm only updating Composition, Scaffolding, or Reporting?You can check out the following Knowledge Base on each respective ServiceRocket add-ons:
What about other related apps?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 contentConfluence 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
|
Page Comparison
Manage space
Manage content
Integrations
App links