Scroll Versions provides an automated Migration Tool that can be used to migrate a versioned space to a versioned Scroll Document. After completion, the newly created Scroll Document can be used on Confluence Server or Data Center or it can be migrated to Confluence Cloud using the Atlassian Cloud Migration Assistant.
A new space is created in every migration, while the original space remains unaffected, so don't be afraid to break anything!
Currently, Scroll Versions does not support the migration of all possible setups that are in use by our customers. To make sure the migrated document represents the versioned space well, we are checking for the following issues that would block a migration:
|Migration Blocker||Resolvable by user||Resolution / Comments|
|Scroll Documents 3.0+ not installed||Install or update Scroll Documents|
|Multiple top-level pages||Reorder pages in the hierarchy to be below one root page (ideally the space home page)|
|Scroll Translations is active in the space||Migration of multiple languages will be added once Scroll Documents supports multiple languages.|
|Variants are active in the space||Migration of variants and conditional content will be added once Scroll Documents supports content variants.|
We're working hard on extending Scroll Documents' feature set, you can view our plans and progress on the Cloud Roadmap.
In addition to the blockers above, there are a number of content properties and metadata that do not block the migration, but might be left out or migrated in unexpected ways. Please note, that the table below only accounts for content and data that's available in spaces that meet the prerequisites listed above.
Legend: – Migrated, – Not migrated, – Migrated differently
|Inline comments||Inline comments are not migrated.|
|Page history||Only the latest page revision (Confluence page version) is migrated|
|Space permissions||The migrating user will receive space admin permissions in the created space.|
|Scroll Versions-applied restrictions|
|Page restrictions||User-applied page restrictions are migrated.|
|Page keys||Page keys (Content key) are not available in Scroll Documents and are thus not migrated.|
|Duplicate Page Titles||In Scroll Documents, page names are prefixed with their version name, which prevent name conflicts between different versions of the same page. For conflicts within a version, the migration will add a number increment to the page name, e.g. "Introduction 1".|
|Workflow states||Scroll Documents does not support page workflows, so any workflow states assigned to pages will not be available after the migration.|
|Include Library Spaces|
Scroll Documents does not support version-aware content reuse across spaces or documents. However, spaces that reuse content from other versioned spaces can be migrated, but the reused pages from other spaces are going to be copied into the document.
The result is a versioned document with versioned includes from within the document. The main downside of this approach is that Include Library pages reused across multiple versioned spaces will be imported into every Scroll Document and thus will duplicated.
|SEO feature||Scroll Versions' SEO feature allowed to customize the HTML page titles of the versioned space. This is not feasible in Confluence Cloud and Scroll Documents, meaning the HTML title of pages will revert to Confluence default.|
If something that's important for your migration is missing in the table above, please don't hesitate to reach out to us by creating a Cloud migration support ticket.
- Navigate to Space tools > Scroll Add-ons > Migrate to Scroll Documents
- (optional) If your space's migration is blocked by any of the migration blockers listed above, you'll be notified here, so please resolve them if possible and proceed.
- Select Start Migration to start the migration wizard.
- Enter a name and space key for your new space.
- Select Next.
- Select one version to be migrated as the Working version, which is a dedicated draft version in Scroll Documents. In most cases, the most recent version is the right choice here.
- Select any number of versions to be migrated as Saved versions. Saved versions are similar to space versions in Scroll Versions, so leaving out old or outdated versions here might help you keep your new Scroll Document lean.
- Click Save.
- Select Start Migration.
- Wait for the migration task to finish.
- A success message will confirm the correct execution of the migration and provide a link to your new versioned Scroll Document.