Complete survey migration walkthrough

1. Migration of spaces/apps, starting from DC/server

1.1 Assess your apps

First select the Atlassian Cloud Migration Assistant and begin assessing your apps:

Next, select that you will need Multivote and Enterprise Survey for Confluence in the cloud, click Done.

Assess your apps - select that you need Multivote and Enterprise Survey in the Cloud

1.2 Assess your apps

Then it is time to prepare your apps.

You will need to connect to your cloud site and will have to install Multivote & Enterprise Survey for Confluence on it (if you haven’t already 😉 )

Select the cloud site you want to migrate your surveys to

Install your apps on your cloud site if necessary

finally, agree to the app migration and click on ‘Done’.

1.3 Review your email domains/Assess and prepare your users

Before you can start a migration, you have to review your email domains and assets and prepare your users. Please follow the Atlassian documentation here.

1.4 Migrate your data

Finally, click on Migrate your data to start a new migration:

This leads you to the migration dashboard. Click on “Create new migration”.

This will guide you through the different steps, as shown below. After having (again) connected to the cloud

Overview of the guide of the different steps in a migration

‘Click on 'choose what to migrate’. Here you can choose your migration options, such as global templates, spaces, users and groups as well as apps, including the Multivote & Enterprise Survey for Confluence.

Finally, you can then check for errors (and correct if necessary), before reviewing your migration and start it by clicking on ‘run now’.

The migration will then appear in your dashboard.

Migration dashboard. Click on ‘view details’ to see more.

By clicking on “View details”, you can follow its progress.

The progress of a migration. The different migration processes will appear sequentially after the previous one has been completed.

Please note that if the app data migration takes longer than 15 minutes, its status will be displayed as TIMED_OUT. The data migration will still continue though. Please check the logs for progress/completion.

If the app migration has timed out, please check the logs

The last log message should contain “App migration settled by Cloud app with status SUCCESS, percent 100 and message : All events processed successfully for transferId: ”.

2. Using the new editor for each page

The Multivote & Enterprise Macro Migration Assistant for Survey contains a handy overview to see all migrated or yet-to-be migrated pages.

You can find it by navigating to ‘general configuration/apps/multivote & enterprise survey’, then select the migration assistant tab:

You can open directly the pages in question from this overview, by clicking on the page. There you can see that the page still uses the legacy editor.

A page with a survey using the legacy editor

Edit the page, and click on ‘preview page’ on the footer on the page. This will convert it to the new editor. Finally, publish a new version of the page.

A page in edit mode with a survey macro using the legacy editor. The page can be converted by clicking on preview page below.

The page now will no longer show a legacy editor, but the macro will still be in legacy mode, and you will see ‘Error loading the extension’.

The page after conversion to the new editor shows an Error loading the extension

3. Migrating legacy macros to cloud macros

Return to the Multivote & Enterprise Macro Migration Assistant for Survey. The page is now ready to be migrated, which will convert all survey legacy macros on that page to the new cloud macros.

Macro Migration Assistant for Survey, showing one page ready to be migrated

Select the pages using the new editor, and then click on “Migrate selected pages”.

Select non-migrated pages ready to be migrated

After a short moment, you should see a success.

Migration assistant showing a successfully migrated page

Navigating to the page will now show you the survey and its data.

For possible error scenarios, please consult the troubleshooting section here.