Tree View Migration Guide
As the migration support must be considered beta as of today - please consider opening a support ticket prior to migration so that we can assists you.
Scope
This guidance explains the migration from Tree View Server/Data Center to Cloud.
Feature differences
The following notable differences exist:
Element | Major differences |
|---|---|
UI | While the primary user interface elements to control Tree View Server/Data Center are in the Watch Page dialog the Tree View Cloud user interface is accessed via a symbol. |
REST interface | Tree View Cloud does NOT offer a REST interface. |
Tree View - show all watches macro | The macro does NOT exist in the Cloud version. |
Status after the using Atlassian’s migration assistant
After you have migrated content the watches on each page are as on Server / Data Center. However a user will not have any active tree watches.
Using Tree Views’s migration support
1. Export the tree watches into JSON
You must have Tree View version 1.13.0 or higher on your Server / Data Center instance
Please navigate to:
<<your server url>>/rest/treeviewrest/1.0/migrationlike
https://example.com/rest/treeviewrest/1.0/migrationand copy the JSON file you get into the clipboard.
2. Open the migration support page
Please navigate to
<<your cloud url>>/plugins/servlet/ac/de.edrup.confluence.plugins.tree-view/tree-view-migrationlike
https://example.atlassian.net/wiki/plugins/servlet/ac/de.edrup.confluence.plugins.tree-view/tree-view-migration3. Paste the JSON content and execute the migration
Paste the JSON content into the text area and simulate or execute the migration.
In case the migration of some Tree Watches fails the rest will be migrated anyhow => just repeat step #3 multiple times in case you are migrating space by space.
The Confluence Cloud index needs some time to index the newly migrated spaces. In some cases you need to wait 1-2 hours before all pages can be found!