Migration trouble-shooting

1. Common:

- Timed-out data migration

The data migration is shown as ‘Timed-out’ in step 1 of the migration process. This might only be due to the migration taking longer than 15 minutes. Please revise the migration logs carefully. If the app data migration was successful, 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: ”. If you need help, please open a support request.

- Nested macros

If the Survey or Multivote macro is nested into two or more macros on the server/DC side, you will see an error banner on the page after macro migration. Additionally, the Macro Migration Assistant will show you a warning ( ). In order to fix this problem, you first need to

1. go to edit mode and unnest the macro

2. convert the macro using the Survey macro migration assistant

2. Survey troubleshooting:

- Survey data is not migrated shown on page

If the legacy to cloud macro migration is shown as successful ( ) in the Survey Migration Assistant (step 2), but on the page you see ‘the Survey data is not migrated’, this means there has been an error during data migration in step 1. Please check the logs of step 1 on the server/DC side and retry the app data migration.

- Survey too large

If the Survey (without responses) is larger than 240 kB, it cannot be migrated to the cloud, since it is saved in forge storage and therefore its limits apply. This will be indicated by a banner on the migrated page, and also shown warnings in the pre-migration checks in Server. In order to solve this, you have to reduce the Survey definition size before migration e.g. by using links to images instead of images themselves, and then re-migrate.

- Manually migrate the definition of a single Survey

In the case you want to migrate only a single Survey, you can do this manually. This will only migrate the definition of a Survey, no responses will be migrated!

On server, open the Survey and toggle “Expert mode” to “on”. You can then select the “JSON” tab and download the JSON of the Survey definition. On cloud, create a new Survey. Open this new Survey, toggle again the “Expert mode” to “on” - and paste the JSON into the JSON tab.

3. Multivote trouble-shooting:

- Missing information in Options

If a Multivote option contains content other than plain text, dates, or mentions, that content will be removed during migration.

Remove all styling and non-text content from Multivotes on your DC instance, then run the migration again.