In this article, we'll discuss how Scroll Versions and Scroll Content Manager differ, what they have in common and what feature differences you can expect when converting from one to the other.
Why Convert to Scroll Content Manager?
With Atlassian’s end of life for Data Center products, many Confluence users are thinking about migrating to Cloud.
Just like Atlassian, we're placing our focus and future development efforts on Cloud. For this reason, we've marked Scroll Versions and Scroll Translations as legacy apps and don’t intend to bring these specific apps to Cloud. Our primary efforts now and into the future will go into Scroll Content Manager, our Cloud-first app for advanced content management in Confluence. Since its launch in 2019, we've worked hard to make it the more powerful and more user-friendly alternative to our legacy apps.
If you're planning to migrate to Cloud, you will have to convert to Scroll Content Manager. Even if you are staying in Data Center, we also highly recommend a move to Scroll Content Manager as a preparation to migration to cloud. With this app being the focus of our development and updates, your team will be able to benefit from these changes and improvements.
Why Compare the Apps?
It's essential to understand how these apps differ and what features they share, as they are not entirely the same. Scroll Content Manager is not a Cloud version of Scroll Versions. It's a whole new versioning app that was built to work specifically with Confluence Cloud.
It’s important to learn about these differences before you decide to use Scroll Content Manager so you can make the right choice that fits your team’s needs.
Feature Comparison
Below, we've laid out a side-by-side comparison of features between Scroll Versions and Scroll Content Manager:
The current information reflects the feature state as of .
The feature comparison below is updated regularly as we continue to develop Scroll Content Manager.
|
Feature |
Scroll Versions |
Scroll Content Manager |
Notes |
|---|---|---|---|
|
Versioning: Create and manage different versions of your documentation. |
Available ✅ |
Available ✅ |
Both apps support versioning with some fundamental differences. See: Manage Versions |
|
Variants and conditional content: Create and manage variants of your documentation. |
Available ✅ |
Available ✅ |
Both apps support variants with some differences. See: Manage Variants and Conditional Content |
|
Publish in Confluence: Publish documentation from your authoring space to another space. |
Available ✅ |
Available ✅ |
Scroll Versions publishes to:
Scroll Content Manager publishes to:
|
|
Publish to the web: Publish your documentation to a public Help Center using Scroll Sites. |
Available ✅ |
Available ✅ |
Both apps integrate with Scroll Sites on Data Center and Cloud. |
|
Publish to a document: Publish your documentation in different file formats with Scroll Exporters. |
Available ✅ |
Available ✅ |
Both apps integrate with our Scroll Exporters on Data Center and Cloud. |
|
Remote publishing: Publish your content to a different Confluence instance. |
Available ✅ |
Unavailable ❌ |
We are not planning to implement this functionality in Scroll Content Manager. Instead, look into these options:
|
|
Content reuse: Reuse content within and between versioned spaces. |
Available ✅ |
Partially available 🔄 |
Reusing content within the same space is supported. Include Libraries from Scroll Versions are supported by the conversion tool, but reuse works differently in Scroll Content Manager. See: Reuse Versions |
|
Workflows: Manage versioned content with a built-in workflow. |
Available ✅ |
Available ✅ |
Both apps include a built-in workflow. Scroll Versions also integrates with Comala Document Management, Scroll Content Manager does not yet. Track progress in this Jira issue: DOCS-36 See: |
|
Duplicate page titles: Use the same page title more than once. |
Available ✅ |
Partially available 🔄 |
With Scroll Content Manager, you cannot have the same page title twice in one version within Confluence. However, if you use Scroll Sites or the Scroll Exporters to publish your content, this is possible. See: |
|
Context Keys (formerly Page Keys): Assign keys to specific pages for linking and context-sensitive help. |
Available ✅ |
Available ✅ |
Page Keys have been renamed to Context Keys and are available in Scroll Content Manager and Scroll Sites for Cloud. See: Assign Context Keys |
|
Scroll Roles: Apply additional permission control for specific features in Scroll Versions. |
Available ✅ |
Partially available 🔄 |
In Scroll Content Manager, you can manage your author and review workflow by utilizing space and document restrictions. |
|
Scroll Search: Filter for versions or variants in Confluence's advanced search. |
Available ✅ |
Partially available 🔄 |
The Scroll Search feature is not available in Scroll Content Manager. Instead, you can search for specific pages in Confluence using the version and/or language prefixes in your search query to locate a page in a specific version and language. |
|
Java API: Integrate Confluence with other Server apps. |
Available ✅ |
Partially available 🔄 (Data Center only)
|
- |
|
REST API (unofficial): Use REST resources for process automation. |
Available ✅ |
Pending ⏳
|
Scroll Content Manager does not yet have any APIs available for public use. To follow the progress we recommend watching this Jia issue: DOCS-200 |
Next Steps
Dive into the following articles to learn more about what you need to know when converting from Scroll Versions to Scroll Content Manager: