Welcome to the Cloud Migration Documentation for our application in Confluence. This comprehensive guide provides an in-depth overview of the steps and considerations involved in migrating your app to a cloud-based environment. Whether you are an administrator, developer, or a member of the migration team, this documentation is designed to assist you throughout the process.
In this documentation, you will find detailed information about what content will and will not be migrated and therefor also prepared for migration. We will also outline the User Profiles for Confluence content that will be and those that do not. Additionally, we'll explain the steps involved in the preparation process, with a focus on updating macro instances.
Supported Platforms in the Cloud Version
As of the current version, our cloud version exclusively supports Microsoft Entra ID (previously Azure AD) as the Identity Directory. To consider cloud migration, your organization should already use or plan to use Microsoft Entra ID for identity management.
Migration Process and Preparation
How to Perform the Preparation
To prepare your macros for migration, follow these steps:
Go to User Profiles Configuration: Access the User Profiles Configuration in Confluence.
Navigate to the "Cloud Migration" Section: Within the User Profiles Configuration, navigate to the "Cloud Migration" section.
Select the Spaces to Migrate: In the "Cloud Migration" section, select the spaces that you want to migrate. You can specify these spaces as a comma-separated list.
Upload CSV File: Provide a CSV file containing user data from Microsoft Entra ID. Please refer to Microsoft Entra's documentation for guidance on creating this file. Uploading this data is essential for ensuring that your macros continue to function seamlessly after the migration.
Start: Click on the Start button to start the preparation process
What does the app during the preparation process
Update Macro Instances: All instances of Enhanced Profile and Profile Macros will be updated to ensure compatibility with the cloud version. During this process, the names of the macros will be changed, and user mapping to the Entra ID users will be performed to ensure seamless functionality.
New Version History: During the update process, a new version of the content will be created. This new version will be documented in the history of the page or blog post to track changes and revisions.
Migrated content
Confluence
Our app provides a streamlined process for migrating specific content. Please note that while Confluence supports a wide range of content types, our app's migration is specifically designed to migrate and support certain content types. Below is a list of content for which a migration is being prepared.
Prepared
Not prepared
Pages
Blogposts
Comments
History of Pages and Blogposts
Shared Drafts
Custom Templates
User Profiles for Confluence
In general, only macros are migrated as part of the migration process. Currently only the most important macros are migrated as part of the migration process, it's important to be aware that some macros are not currently supported for migration. We are continually working to expand our capabilities, and this documentation will provide insights into the macros that can be migrated successfully.
Prepared
Not prepared
Enhanced Profile macro, always
Profile Macro, if the overriding of the default Profile macro is enabled in the User Profile Configuration (Administration → User Profile Configuration – Advanced Options → Enable Enhanced Profile Macro)