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)|
We're working hard on extending Scroll Documents' feature set, you can view our plans and progress on the Cloud Roadmap.
What is Migrated
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 can optionally be 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 by default. Optionally the space permissions can be copied.|
|Scroll Versions-applied restrictions|
|Page restrictions||User-applied page restrictions are migrated.|
|Page keys||Page keys (Content keys) will be available for Scroll Documents soon and migration support will be provided.|
|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.|
|Scroll Versions and Translations macros|
Scroll Versions and Translations macros are replaced with their native counterparts or otherwise removed during the migration. This list includes:
Using Scroll Exporters or the Scroll Export Button macro?
Please note that the Scroll Versions Migration Tool will not automatically migrate Scroll PDF/Word Exporter export templates to the newly created space containing the Scroll Document. This means if you use Scroll PDF/Word Exporter apps and have created export templates in your original space with Scroll Versions, you will need to manually download and upload the export templates to the newly created space.
Important: If you use the Scroll Export Button macro on any of your migrated pages, after downloading the copy of the export template(s), you will need to delete the template(s) first in the Scroll Versions space before uploading the export template(s) again to the newly created Scroll Documents space. Following this process will ensure that the unique template ID is preserved. Failing to do this will result in the Scroll Export Button not being able to locate the correct export template once the content is migrated to Confluence Cloud.
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.
Migration Steps on Confluence Server/Data Center
- 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 Next.
Select any number of variants to migrated (only if variants are active).
(optional) Adjust the page labels used to assign pages to variants in Scroll Documents.
- 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.
After the Scroll Document has been generated, it can be migrated to Confluence Cloud. For further instructions, please refer to the Scroll Documents Migration Path.
We are fully committed to enable every Scroll Versions user to migrate to Confluence Cloud and Scroll Documents. We are currently working to improve feature parity between the two apps and to provide an automated migration path, which will be extended as new features are implemented in Scroll Documents. For more details about our plans, please refer to our Cloud Roadmap.
A later migration will give you a more complete feature set to start with and an easier migration path. For this reason we'd like to ask you to delay the migration.
However, some of our users have performed a manual migration from Scroll Versions and Confluence Server to Scroll Documents and Confluence Cloud with help of our product support. So if you're forced to migrate right now, please reach out to us under firstname.lastname@example.org.