Overview

This document explains how to plan your Scaffolding migration.

Confluence Cloud currently does not support nested macros (See CONFCLOUD-68323).

This means integration with other apps by way of nesting is limited.

This Atlassian documentation lists the Confluence macros that go through changes when converted to the new editor in Confluence Cloud.

On this page:

1 Overview
2 Prerequisites

On this page:

1 Overview
2 Prerequisites

Prerequisites

Review the Feature differences document before starting the migration.

Upgrade the Scaffolding app

Update the Scaffolding app to at least version 8.25.0 through the UPM inside the Confluence administration console.

If your pages contain Repeating Data macros, update the Scaffolding app to at least version 8.30.0 or 9.1.0.

Select Administration ( ) > Manage apps.
Search for Scaffolding.
Ensure the app is updated to the most recent version.

Find the non-migratable Scaffolding macros

Ensure that the site search indexes are current.
Choose one of the options below to assess data compatibility between the Scaffolding Data Center and the Cloud:

Option 1: Use the Macro Usage details page

The Macro Usage page can show you the number of Scaffolding macros on your site and the pages that contain them.

Go to Administration > Macro Usage.

Locate the macros under Scaffolding.
Record the number of Scaffolding macros on your site.
Identify how many Scaffolding macros cannot be migrated.

Click each macro link to show you the pages containing the corresponding macro.

Option 2: Use SQL queries

Use the sample SQL queries below to help you gather all pages and templates that contain unsupported Scaffolding macros.

Relevant page titles SQL

This SQL provides a list of impacted page authors and the relevant page titles that currently contain Scaffolding macros that are unavailable in cloud.

select s.spacekey, s.spacename, c.title as "Page Title", um.username
from content c, spaces s, user_mapping um left join cwd_user cu on um.username = cu.user_name
where c.spaceid = s.spaceid and c.contenttype = 'PAGE' and c.prevver is null and c.content_status = 'current'
and c.creator = um.user_key
and c.title in
(SELECT c.title
FROM CONTENT c
JOIN BODYCONTENT bc
    ON c.contentid = bc.contentid
JOIN SPACES s
    ON c.spaceid = s.spaceid
WHERE c.prevver IS NULL
    AND c.contenttype IN ('PAGE', 'BLOGPOST')
    AND bc.body LIKE '%ac:name="hidden-data"%'
		or bc.body LIKE '%ac:name="get-data"%'
		or bc.body LIKE '%ac:name="excerpt-data"%'
		or bc.body LIKE '%ac:name="eval-data"%'
		or bc.body LIKE '%ac:name="set-data"%'
		or bc.body LIKE '%ac:name="label-options"%'
		or bc.body LIKE '%ac:name="group-data"%')
order by s.spacekey, c.title

Relevant template SQL

This SQL provides a list of impacted page authors and the relevant template titles that currently contain Scaffolding macros that are unavailable in cloud.

select s.spacekey, s.spacename, p.templatename as "Template Title", um.username
from pagetemplates p 
left join spaces s on p.spaceid = s.spaceid
left join user_mapping um on p.creator = um.user_key
--left join 
where p.prevver is null
--and p.creator = um.user_key
and p.content LIKE '%ac:name="hidden-data"%'
        or p.content LIKE '%ac:name="get-data"%'
        or p.content LIKE '%ac:name="excerpt-data"%'
        or p.content LIKE '%ac:name="eval-data"%'
        or p.content LIKE '%ac:name="set-data"%'
        or p.content LIKE '%ac:name="label-options"%'
        or p.content LIKE '%ac:name="group-data"%'
order by s.spacekey, p.templatename ;

Prepare the Scaffolding data for migration

Check the main templates and pages that your users are using and remove the structures that are incompatible with cloud. For information about the unavailable migration scenarios, refer to the Feature differences document.

Create a staging instance and perform a test migration on sample data

Test migration with a staging instance

Create a Staging environment licensed by a developer license.
Create a snapshot of the current Confluence Data Center instance and clone it for the staging instance.

Test data by creating a sample space

Identify a space that contains:
1. Space templates that are widely used in your organization and use Scaffolding macros.
2. Pages with Live Template macros that are using the space templates.
Clone the contents of that space to a new space.
Prepare a migration window as highlighted below.
Go through the Test migration as highlighted in Step 1: Prepare for the Scaffolding migration | Find all the Scaffolding macros and Step 1: Prepare for the Scaffolding migration | Prepare the Scaffolding data in server.

Schedule the migration window

To estimate the time you will need for the migration steps, we recommend reviewing all of the steps before executing.

Depending on the size of the data and the complexity of the existing template configuration, it might take a few hours to complete these steps.

Next Steps

Proceed to with Cloud Migration.

Questions?

Contact us via our support portal.

Scaffolding Forms & Templates for Confluence Cloud

Step 1: Prepare for the Scaffolding migration