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.

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 😉 )

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

‘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 hit the button ‘Check for errors’. This will trigger Atlassian’s pre-migration checks. At this stage, there is also a pre-migration check specific to Multivote & Enterprise Survey for Confluence. It checks whether your Surveys obey the size limitations of the Atlassian Cloud.

This pre-migration check is non-blocking. You could continue with your migration but the Surveys in doubt will not be migrated. You can click on ‘View app vendor checks’ and download a report about this check. The report is a CSV file containing the Survey Title, Survey Id, and Survey Size.

Find out more on how to resolve problems with too large Surveys on our troubleshooting section. After correcting potential errors, you can review your migration clicking on ‘Review Migration’ and then start it by clicking on ‘Run now’.

It may be that Multivote & Enterprise Survey for Confluence is listed in the success rate check with a warning:

You can ignore this warning for now, as our migration assistant for Survey was only recently introduced and therefore has an unknown success rate.

The migration will then appear in your dashboard.

By clicking on ‘View details’, you can follow its progress.

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.

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.

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.

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’.

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.

Select the pages using the new editor, and then click on ‘Migrate selected pages’.

After a short moment, you should see a success.

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

If you Survey data is not migrated you will see this

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