Scroll Content Manager
4.6 4.5 4.4 4.3 4.2 4.1 4.0 3.39 3.38 Cloud Data Center
Scroll Content Manager
4.6 4.5 4.4 4.3 4.2 4.1 4.0 3.39 3.38 Cloud Data Center
Breadcrumbs

Scroll Content Manager Migration Path

To migrate Scroll Content Manager from Server or Data Center to Cloud, follow the steps outlined in this article.

Prerequisites

Before you begin, make sure you have:

  • A Confluence Server or Data Center instance with Scroll Content Manager installed.

  • A Confluence Cloud instance with Scroll Content Manager installed.

  • The Confluence Cloud Migration Assistant (CCMA), version 3.3.3 or higher.

Migration Steps

Step 1: Plan your migration

A good plan saves time and prevents surprises. Before you start:

  1. Review Atlassian’s migration guides to understand the full process.

  2. Evaluate your migration scope, timeline, and dependencies.

Step 2: Assess your apps

Decide which apps you need on Confluence Cloud:

  1. Open the Migration Assistant in the Confluence administration section.

  2. Select View app assessment.

  3. Search for Scroll Content Manager and mark it as Needed on Cloud.

Step 3: Prepare and migrate

Follow Atlassian’s instructions to prepare your apps, users, and email domains, then migrate your content:

  1. In the Migration Assistant, follow Atlassian’s steps to prepare your apps, users, and email domains.

  2. Migrate your data using Atlassian’s guide: Migrate data using the Confluence Cloud Migration Assistant.

When you reach the Choose your migration options step in the Migration Assistant, make sure to select all spaces that contain Scroll Content Manager documents.

After migration

Once the migration completes, verify that your content moved over correctly:

  • Go to your Confluence Cloud instance and open the migrated spaces.

  • Open the Document Library in your most important spaces and confirm that your documents, versions, and languages are present.

  • Open a few pages, switch to another version or language in the page toolbar, and check that you land on the correct page.

  • Check pages that use conditional content inline, for example, inside lists, other macros, or sentences.

  • Before saving the next version, convert any pages that still use the legacy editor.

  • Confirm that your documents have the right owners, and that people who edit pages and metadata still have the access they need.

Need help?

If you run into issues or have questions about the migration process, contact our support.

Last updated: