This article covers:
-
How the conversion from Scroll Versions or Scroll Translations to Scroll Content Manager works.
-
What gets converted during the process.
The Conversion
If you have Scroll Versions or Scroll Translations installed, a conversion tool is available to space admins in any Scroll-managed space. The tool takes your Scroll Versions or Scroll Translations managed space, copies it, and turns the copy into a new Scroll Content Manager managed space containing a Scroll document.
The document in the new space contains all the versions, variants, and translations you choose to convert.
Update before you convert
We regularly update the conversion tool, so update to the latest version of Scroll Versions and Scroll Translations before starting.
Your original content isn't affected
The conversion creates a copy of your Scroll Versions or Scroll Translations managed space, and the new copy is managed by Scroll Content Manager. You can run a test conversion at any time without affecting the original.
After The Conversion
Once you've created the new Scroll Content Manager managed space, your next steps depend on where you're hosted:
-
Moving to Confluence Cloud: Use the Atlassian Cloud Migration Assistant to migrate the converted space to Cloud.
-
Moving to a new Data Center system: Create an XML export of the converted space and import it into your new system.
Conversion Path
Below you’ll find a visual that shows what the conversion from Scroll Versions or Scroll Translations to Scroll Content Manager looks like if you migrate to Confluence Cloud:
-
Start: A space managed by Scroll Versions and/or Scroll Translations on Confluence Server or Data Center.
-
Step 1 - Convert: Use Scroll Versions and Scroll Translations conversion tool to create a copy of the space, the new space is managed by Scroll Content Manager. The converted space contains your versioned and/or translated Scroll document.
-
Step 2 - Migrate: Use the Atlassian Cloud Migration Assistant to migrate the converted space to Confluence Cloud, where it continues to be managed by Scroll Content Manager.
What is Converted?
As we mentioned before, the conversion tool creates a copy of your original space. The difference is that this new space is now managed by Scroll Content Manager. In the table below, you’ll find information around how different content properties, metadata and macros are migrated to the new space:
Please note
The table below only accounts for content and data that's available in spaces which have been converted via the Scroll Versions and Scroll Translations inbuilt conversion tool.
|
Content |
Conversion status |
Notes |
|---|---|---|
|
Page attachments |
Converted ✅ |
Only the latest attachment version is converted to the new space. |
|
Page comments |
Converted ✅ |
Original authors are preserved. Conversion date is used as the comment date. |
|
Inline comments |
Converted ✅ |
- |
|
Page history |
Not converted ❌ |
Only the latest page revision (Confluence page version) is converted. |
|
Page drafts |
Not converted ❌ |
Only published changes are converted. |
|
Version information |
Converted ✅ |
Descriptions are converted to Scroll Content Manager version descriptions. Release dates are appended to the version description. Creation dates aren't kept in Scroll Versions, so versions are dated to the conversion date. |
|
Space permissions |
Converted ✅ |
The converting user receives space admin permissions in the new space by default. Existing space permissions can optionally be copied. |
|
Restrictions in versions |
Converted ✅ |
Version specific restrictions are converted. See: Conversion Options |
|
Restrictions with Scroll Roles |
|
Scroll Roles aren't available in Scroll Content Manager |
|
Page restrictions |
Converted ✅ |
User-applied page restrictions are converted. |
|
Page keys |
Converted ✅ |
Page Keys are converted to Context Keys in Scroll Content Manager. |
|
Duplicate page titles |
Converted differently 🔄 |
With Scroll Content Manager page titles get a version-name prefix to avoid conflicts between versions. For conflicts within a single version, conversion appends a number to the page title (e.g., "Introduction 1") and adds the original title as a Scroll page title, which is displayed when publishing with Scroll Sites or Scroll Exporters. |
|
Workflow states |
Converted differently 🔄 |
The simple built-in workflow from Scroll Versions is converted to the equivalent Simple workflow in Scroll Content Manager, and existing page statuses are kept. If your workflow is managed through Comala Document Management, the page status of each page's latest revision is copied for audit purposes. |
|
Include Library spaces |
Converted differently 🔄 |
Scroll Content Manager does not support version-aware content reuse across spaces. Any content included from other spaces using the Scroll Versions or Translations Include Library feature will be copied directly into the new document during conversion. We recommend keeping the default conversion settings so the Include Library is copied into the new space outside of your document, this lets you continue reusing content in your Working version, while include macros in saved versions resolve to static content. Include Library pages reused across multiple versioned spaces are duplicated into each document. |
|
SEO feature |
Not converted ❌ |
Scroll Versions' SEO feature allowed to customize the HTML page titles of the versioned space. The HTML title of pages will revert to Confluence default. We recommend looking into Scroll Sites to optimize your content for readability and searchability. |
|
Scroll Versions and Translations macros |
Converted ✅ |
Macros are replaced with native Confluence or Scroll Content Manager equivalents, or preserved as-is. See the macro list below:
|
|
Dynamic links within the same space |
Converted ✅ |
During the conversion process, dynamic page links within the same space will undergo transformation. In the newly managed Scroll Content Manager space, these links will be updated to point to the corresponding pages within the same Scroll Content Manager space. Dynamic links are created using Confluence's built-in Link feature and direct to other pages within the Confluence system. They differ from static web links, which continue to point to the configured URLs. |
|
Incoming links from other spaces |
(Optionally) Converted ✅ |
You can optionally rewrite incoming links from other spaces so they point to the new Scroll Content Manager space. This is one of the final conversion steps. See: Migration of Incoming Links Any page that had its link rewritten during this action will be listed in the Confluence logs with its page ID for reference. |
|
Blog posts |
Converted differently 🔄 |
Blog posts are converted in the following way:
|
Next Steps
Now it’s time to learn more about Scroll Content Manager. Please proceed to the following sections: