Breadcrumbs

Migration Path

Before moving your Confluence spaces to Cloud you should migrate any Scroll Exporter macros that are not available on Cloud to their respective Cloud compatible version. This is required if you have used the Scroll Exporter macros with Scroll HTML Exporter before version 3.5.1.

The affected Scroll HTML Exporter specific macros are:

  • Scroll HTML Ignore

  • Scroll HTML Ignore Inline

  • Scroll HTML Only

  • Scroll HTML Only Inline

  • Scroll HTML Indexterm

  • Scroll HTML Title

  • Scroll Export Button

  • Scroll Pagetitle

Prerequisites

Migration Steps

1. Migrate Export Templates

Scroll HTML Exporter v4.0 (or later) 

There remains two ways to migrate created export templates from server/Data Center to cloud:

  • Use the Confluence Cloud Migration Assistant - for Scroll HTML Exporter v4.0 users (and newer) you can use the Confluence Cloud Migration Assistant (CCMA) to migrate space templates automatically to cloud when migrating your chosen space(s). Global export templates will automatically be migrated when using the CCMA.

or

  • Download & Import - depending on where the Scroll HTML Exporter export templates are created (globally and/or in a space) admins will be required to navigate to the respective template list overview and download the individual export template(s) (downloaded as a *.data file type). These templates can then be imported into the equivalent template overview section in the Confluence Cloud instance via the Upload button.

Scroll HTML Exporter v3.10.4 (or earlier)

Older versions of Scroll HTML Exporter v3.x, do not integrate with the Confluence Cloud Migration Assistant. Therefore, it is not possible to migrate Scroll HTML Exporter v3 export templates from on-premise deployment types (server/DC) to cloud - due to technical differences in the templating process.

Subsequently, server/DC templates are not compatible with the cloud version of the app meaning new export templates would need to be created either using Scroll HTML Exporter v4.x on Confluence Data Center, or recreating the templates with Scroll HTML Exporter on Confluence Cloud. You can read more about the template creation process here.

After setting up your export template(s), if you need to make further changes to the hard-coded export output for the template theme, you can use the custom template customization option for post-export changes.

2. Migrate Scroll Exporter-Specific macros

For users of Scroll HTML Exporter 3.9.25 (and later)

 Disabling Collaborative Editing mode is required prior to following the steps below in order to avoid losing any unpublished changes when migrating the pages using the Scroll Macro Migration tool.

You can use the integrated Scroll Macro Migration Tool. This tool will automatically detect any pages in a space that contain deprecated Scroll Exporter app specific macros. When pages containing affected macros are identified by the tool, it is possible to easily migrate these macros to the supported Confluence Cloud format.  To perform this migration in your chosen space please follow these steps:

  1. Navigate to; Space Tools > Apps > Scroll Exporter Extensions

    1.png

  2. Select the Start Migration button

    2 - two.png

  3. After the migration task has finished, a success confirmation message will display:

    4.png

  4. After completing these steps, the Scroll Macro content in the space remains compatible with Confluence Cloud (if imported). An empty state screen will display once all the pages containing the incompatible Scroll Macros have been migrated:

    5.png


Migration Tool Information

Things to be aware of:

  • Scroll Pagetitle Macro - due to the differences between Confluence Cloud and Server, the Scroll Pagetitle macro does not exist in Confluence Cloud as a Scroll macro. Instead, the same functionality of this macro can be achieved in Confluence Cloud via a setting in the Page tools (•••). This means that when running the Scroll Macro Migration Tool, the Scroll Pagetitle macro will be converted into a property that is recognised in Confluence Cloud. As a result the Scroll Pagetitle macro will be removed from the page(s) in Confluence Server and will not function anymore.

  • Scroll Export Button Macro - customized export templates associated with the Scroll Export Button macro in Confluence Server will need to imported into Confluence Cloud for the Scroll Export Button macro to detect the required template again. If the template is not imported into Confluence Cloud, the Scroll Export Button macro will default to a bundled template included with the app. When manually importing the export templates, please ensure you update to the latest server version of the Scroll Exporter app before downloading the templates.

  • Migration Process - after running the migration, it may take several minutes for the affected pages in the space to update within the Scroll Exporter Extensions tab.

Still Unclear? Reach Out to Us

If you need help with any of these migration steps, reach out to us via  help@k15t.com