In this page

Migration guide

This section provides a step-by-step guide to help you migrate your self-hosted Confluence instance to the cloud and configure content lifecycle management using the cloud version of our app.

Step 1: Design your workflows

Decide on how you want the lifecycle of the contents of your spaces to be managed (including content statuses, notification emails, automated archiving and deletion):

  1. Review the documentation for the cloud version of the app to understand the available configuration options.
  2. Analyze your current archiving configurations.
    1. Consider the migration as a great opportunity to identify improvements or changes you'd like to make to your workflow!
  3. Plan how to adapt your existing configurations from the self-hosted version to the scheme-based approach of the cloud app. Use the preconfigured schemes as a starting point, and refer to the tutorials and best practices for guidance.
    1. Remember: in the cloud version, content status schemes, notification schemes, and automation schemes are independent. For example, if two configurations differ only in content statuses, but share the same notification settings, you only need one notification scheme for both workflows.

Step 2: Install and initialize the cloud app

Once you've installed the cloud version of the app, follow these initial steps to get started:

  1. Wait for the Initialize content events job to run automatically, which will occur within 5 minutes of installation.
  2. Ensure that all integrity checks pass successfully.
  3. Verify the permissions on the app space permissions screen to ensure proper access.

Step 3: Exclude spaces

Exclude any spaces where lifecycle management is not required. This process works the same way as blacklisting spaces in the self-hosted version of the app.

Step 4: Set up content status schemes

  1. Review the pre-configured content status schemes and content statuses.
  2. Adjust the pre-configured schemes or create new ones to suit your needs.
  3. Set the default scheme.
  4. Apply any non-default schemes to specific spaces as needed.

Step 5: Set up notification schemes

  1. Review the pre-configured notification schemes and notification email templates.
  2. Adjust the pre-configured schemes or create new ones to suit your needs.
    1. Notification email templates in the cloud version use Handlebars syntax instead of Velocity, which was used in the self-hosted version. If you have custom templates, you will need to rewrite them. You can start with the pre-configured templates and refer to our documentation for tips and best practices.
    2. You can disable notifications one by one in a scheme, to save your users from unexpected notification emails during the migration period.
  3. Set the default scheme.
  4. Apply any non-default schemes to specific spaces as needed.

Step 6: Set up automation schemes

  1. Review the pre-configured automation schemes.
  2. Adjust the pre-configured schemes or create new ones to suit your needs.
    1. You can disable automations one by one in a scheme, to avoid unwanted executions during the migration period.
  3. Set the default scheme.
  4. Apply any non-default schemes to specific spaces as needed.

Step 7: Explore new features

Explore the new cloud-only app features, like macros or dashboards. Embrace the full potential of the cloud version!

Limitations

There are a few limitations when migrating existing data to the cloud:

  1. Content view events cannot be migrated. The cloud app initializes these values with sensible defaults, which will update organically as your team interacts with the content.
  2. Archive spaces from the self-hosted version will no longer be treated as archived versions of live spaces. Instead, the app uses Confluence Cloud's built-in content archiving feature, keeping the content in its original space.

Questions?

Ask us any time.