Migration Path - Ideation App

Below is a step-by-step guide to help you migrate your Ideation app data to Confluence Cloud.

Before you start, please read carefully this checklist

We recommend reading this Atlassian article to plan your migration.

Please check that you have Ideation latest version for both Server and Cloud" installed in both Confluence instances (having previous versions in any of them won't trigger the Ideation migration; it will just migrate a Confluence space without Ideation data).

Make sure that Confluence users have valid email addresses that are the same in their cloud counterparts.

Ideally perform the migration with user that have admin site privileges on your Confluence Cloud site.

Update the Confluence Cloud Migration Assistant to the latest version.

Running a migration of Ideation Data

Step 1

Start by making sure that your Ideation App is tagged as needed in Cloud in order to trigger the right event once a space is migrated via the Migration Assistant.

Navigate to Confluence Administration and choose Migration Assistant. Choose the Assess your apps option and select our Ideation app to be needed in Cloud :

Select the Assess your Apps Option

Set Ideation App to be needed in Cloud. You do not need Spectrum API App

Step 2

Select your Cloud site where your data will be migrated.

To do so:

Enter the site from which you want to migrate data and select the cloud site which data will be migrated to
Make sure the admin’s email address is the same on both cloud and server environment
Check “Allow Atlassian” to access migrations data
Confirm

Now that your pre-configuration is done, you can proceed to creating a new migration plan.

Step 3

Navigate to home page and create a new migration.

You will be redirect to the interface to confirm your cloud site selection and will be asked to choose what to migrate as following:

Select Migrate spaces to choose after what spaces to migrate
Select the users policy. Please note that you must sure that users that have created Ideation content within your Confluence server are existing in your Confluence Cloud site. If not, that that user has created Ideation content in server and can’t be found during migration, he will be replaced by the user who is performing the migration in order to don’t break data or highlight feature.

Proceed to space select to migrate content from and migrate Ideation data from as following:

After confirming the action, the migration assist will provide you with a list of checks and errors to fix before migration.

You will get a recap of your migration before to run it: Details about your spaces, number of pages, what apps are impacted, etc.

You simply need to run the migration. You will be redirected to the home page where you can select the migration that you just launched to follow its state.

Please note that app migration progress will take time before displaying the feedback.

Two types of feedback are handled based on Atlassian API:

Migration App data state

Migration App data state

COMPLETE

Your data are successfully migrated after space content and users migration.

INCOMPLETE

Something happened that may have broken the migration.

Some common cases for migration data errors:

Non existing users in cloud
Space data not found during migration due to latencies within cloud instance or internet

We found out that due to Atlassian API restrictions, migrating Restricted pages content (votes, sponsors information, feedback) is impossible on restricted pages.

A message will indicate that migration is incomplete due to this and provide the page id of the possible restricted page like the following screenshot:

Until now Atlassian did not provide any workaround to saving properties on restricted pages during migration. We are continually checking for any possible solution with Atlassian and document will be updated if needed.