| Note |
|---|
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 article explains how to migrate from the Server or the migration from Edit Permission Inheritance Server/Data Center to Cloud with respect to the Edit Permission Inheritance app. Please note that there is no automatic migration. The reasons are explained here: Purde Software Cloud migration status
Step-by-step guide
...
Step Number
...
What to do?
...
1
...
Migrate all data from Server / Data Center to Cloud using Atlassian’s standard methods.
| Info |
|---|
The edit permissions on each page are migrated by Confluence itself => nothing to worry about. |
...
2
Execute the following REST command on the your Server / Data Center (requires Edit Permission Inheritance 1.4.0 or later):
...
.
Feature differences
The following notable differences exist:
Element | Major differences |
|---|---|
UI | While the primary user interface elements to control Edit Permission Inheritance Server/Data Center are in the Restrictions dialog the Edit Permission Inheritance Cloud user interface is accessed via a symbol. |
REST interface | Edit Permission Inheritance Cloud does NOT offer a REST interface. |
Option to hide the create button | The option to hide the create button does not exist in the Cloud version. |
Status after the using Atlassian’s migration assistant
After you have migrated content the edit permissions on each page are as on Server / Data Center. However an inheritance is not yet active with the following consequences:
Changes to the edit permissions of the root page will not be transferred to the child pages.
Pages added under the root page will not inherit the edit permissions of the root page.
Using Edit Permission Inheritance’s migration support
1. Export the inheritances into JSON
| Info |
|---|
You must have Edit Permission Inheritance version 1.5.0 or higher on your Server / Data Center instance |
In case you want to export all inheritances please navigate to:
| Code Block |
|---|
<<your server url>>/rest/editinherit/1.0/getAll |
...
like
| Code Block |
|---|
https://example.com/rest/editinherit/1.0/getAll |
and copy the JSON file you get into the clipboard.
In case you only want to export inheritances from some spaces please navigate to:
| Code Block |
|---|
...
<<your |
...
3
...
Install the Edit Permission Inheritance App on Cloud if not already done.
...
4
...
server url>>/rest/editinherit/1.0/getAll?spaceKeys=KEY1,KEY2 |
like
| Code Block |
|---|
https://example.com/rest/editinherit/1.0/getAll?spaceKey=QM,HR |
and copy the JSON file you get into the clipboard.
2. Open the migration support page
Please navigate to
| Code Block |
|---|
<<your cloud url>>/plugins/servlet/ac/de.edrup.confluence.plugins.edit-inherit/edit-inherit-migration |
like
| Code Block |
|---|
https://example.atlassian.net/wiki/plugins/servlet/ac/de.edrup.confluence.plugins.edit-inherit/edit-inherit-migration |
3. Paste the JSON content and execute the migration
Paste the JSON content into the text area and simulate or execute the migration.
| Note |
|---|
Please note that the execution might take very long. In case you close the window migration won’t be complete. |
...
The option “Do not re-apply…” is slightly faster. It assumes that all edit permissions are correct after migration and therefore does not re-apply them.