Migration Guide (Server/Data Center -> Cloud)

This guide explains how to migrate Easy Dropdown Menu configurations and macros to Confluence Cloud.

The migration consists of two independent parts:

1. Configuration migration (sets, permissions, settings)

2. Macro migration (converting page content)

Both steps are required for a complete migration.

1. Preparation

Before starting the migration ensure:

• Easy Dropdown Menu is installed on the Cloud instance with the newest version

• Easy Dropdown Menu version 7.0.8 or higher is installed on Server/Data Center

• Confluence Cloud Migration Assistant (CCMA) is available

2. CCMA

When running the Confluence Cloud Migration Assistant:

1. Select Easy Dropdown Menu in the app migration screen

2. Run the migration

The following data is transferred automatically:

• Global configuration

• Space configurations

• Dropdown sets

• Permissions

When migration, the current Cloud settings will be chosen over the imported Server settings.
If you want to change that behavior, you need to use the manual data migration.
The merge priority can be configured in:

Cloud → Administration → Apps → Easy Dropdown Menu → Migration → Data Migration

3. Manual Data Migration (Optional)

Export (Server/Data Center)

1. Open Easy Dropdown Menu global configuration

2. Click Export / Import

3. Select spaces

4. Download the JSON file

Import (Cloud)

1. Open Administration → Apps → Easy Dropdown Menu → Migration → Data Migration

2. Upload the JSON file

3. Click Merge Settings

Data Migration | Image

4. Macro Migration (Required)

After the Confluence Cloud Migration Assistant is finished, the EDM macros on your migrated pages as well as the Page Property Reports with EDM filters won’t work yet, because they have a different schema on cloud. The following message will appear due to the macros still using the storage-format that the server plugin uses, which can’t be read by our cloud plugin.

Unknown Macro | Image

When EDM-macros get displayed like this, you will have to execute the next steps regardless of the CCMA status as this is not part of the automatic migration process. There is a tool that ships with EDM called Macro Migration that converts macros from the server-format to the cloud-format.

1. To access it, go to Administration → Apps -> Easy Dropdown Menu -> Migration -> Macro Migration.

Macro Migration | Image

2. On this screen you should see all the spaces and their current macro migration status. The stats can be one of the following: READY MIGRATED PARTIALLY Migrated FAILED

Space Selection | Image

3. Select the spaces you want to migrate by clicking on the checkbox on the left side. Migrating spaces separately makes no difference.

4. If you’re done with your selection, click on Migrate Spaces. You should be redirected to the progress screen.

Progress screen | Image

5. After the migration has concluded, you should see the Migration progress at 100% above the progress bar. Here is a list of what each status means:

• READY : No attempt to migrate this space has been made. Execute a migration which includes this space.

• FAILED : The whole space is either archived or restricted.
  If the space is archived, first restore it in Space Settings > General > Archive space and then migrate it.
  If the space is restricted, grant view and edit permissions for the space to the user that executes the migration.

• PARTIALLY migrated :
  Grant view and edit permissions for each restricted page to the user that executes the reindexing. The migration logs will contain the IDs and title of the pages that failed.
  The Page Property Report contains too many && operators in an EDM filter.
  You don’t have a status option defined and therefore it can’t migrate the macro.

• MIGRATED : All pages that were visible to the Easy Dropdown Menu user were successfully migrated.

Known Limitations → KOMPLETT ANPASSEN!!

• Restricted pages where the user doesn’t have view/edit permissions, won’t be found by the migration. Please give the EDM the needed permissions to update them as well. (see step 5)

• In cloud we are only able to chain three EDM Filters with an AND in a query due to confluence cloud limitations. If you have Page Property Reports that chain more than three, you will need to adjust them (set the cloud filters) manually.

• Also due to confluence cloud limitations, it is not possible to nest AND keywords inside an OR structure in Page Property Report Macros. These queries will be migrated to only OR chained filters. E.g. ((“Yes” AND “Maybe”), “No”) → (“Yes”, “Maybe”, “No”)