We recommend you migrate your Scroll Documents using the Space Export and Space Import feature in Confluence.
Note that using Confluence's Cloud Migration Assistant to migrate your Scroll Documents will NOT work as custom content objects are currently not imported during a Server to Cloud migration. You will be able to use the Cloud Migration Assistant as soon as the bug is fixed.
This bug is known to Atlassian and we encourage you to watch and vote for the reported issue.
- Confluence Server instance (contains the Scroll Documents you want to migrate)
- Confluence Cloud instance with Scroll Documents installed
- On the Server instance: Export space permissions (only needed for the spaces that contain Scroll Documents that you want to migrate)
- On the Cloud instance: Confluence admin permissions (needed in order to import a space)
- XML editor installed
Things to Keep in Mind
- Space imports will not work if you are importing from Confluence Server version 6.13 or earlier.
- The history of Read Confirmations for your documents will not be available on Cloud after a manual migration.
- This approach will migrate all of the content in your space, not just your Scroll Documents. If you want to migrate only Scroll Documents (and its related pages), we recommend you copy all of your Scroll Documents to a dedicated, new space. Alternatively, when doing the space export select Custom Export to select only pages that are part of your Scroll Documents.
- Make sure that the source spaces you select for migration don't have space keys that already exists in your Confluence Cloud destination site.
Step-1: Export all spaces that contain Scroll Documents
To start, in your Server instance, find all the spaces containing the Scroll Documents that you want to migrate. For each of your spaces:
- Go to Space Tools → Content Tools → Export
- Select Export to XML
- Select Full Export or Custom Export
- Click Export
- Download the XML file
Step-2: Edit the exported files
- Unpack the .zip file that you just downloaded
- Find the file entities.xml
- Open the file in an XML editor
Using the editor find the following custom content keys:
In front of the each of the custom content keys, add the prefix:
For the custom content key 'k15t-scroll-document-versions-for-confluence:document' the result will be:
- Save the file
- Zip the folder
Step-3: Import all spaces that contain Scroll Documents
Switch to your Confluence Cloud instance:
- Select Settings in the Confluence navigation (top right corner next to your user icon)
- From the left-hand sidebar, select Import Spaces under 'Administration'
- Click Browse to find your zip file
- Select Import
- Select Import another space if you want to add more spaces
- Click Next
- Optional: Allow the Jira macro repair to fix any broken Jira macros
- Go to your space directory to find and open your new space
- Open the Document library from the space sidebar to view your documents
Step-4: Assign space and app permissions
Users of your Confluence destination site need sufficient space permissions to be able view, create and/or edit documents, as well as create read requests. You might need to assign any missing permissions to Confluence users and user groups. To check and assign permissions:
- For each imported space, go to Space Settings
- Select the tab Permissions
- For all users and user groups, assign any missing view space, add page and delete page permissions by clicking edit permissions
- Click save all
- Select the sub-tab Add-on
- For all users and user groups, assign any missing read confirmations and read requests permissions by clicking edit permissions
- Click save all
If you plan to use Scroll Documents' read request feature on Cloud, note that only users who have made their email accessible to the app will receive email notifications when they are added as readers to a request.
|Space import fails: “Could not locate exportDescriptor.properties in the archive”|
If you're on macOS, use the Terminal app to zip your folder. Use the 'cd' command to navigate to the directory where your zipped file is located, then enter the following command:
Still Unclear? Reach Out to Us
If you need help with any of these migration steps, reach out to us via firstname.lastname@example.org.