Migration methods

The Handy Macros for Confluence app supports data migration only through the Confluence Cloud Migration Assistant. Importing the XML file will not migrate the Handy Macros data to the Cloud.

Macro migration specifics

Not all features can be migrated from Server/DC to Cloud. This page shows what macros from the Handy Macros app can be migrated from Server / Data Center to Cloud.

If you need any macros or features from the Server/DC version of Handy Macros, please drop your request at tech-support@stiltsoft.com.

Pre-migration checklist

Please follow these steps to ensure your app data migration is successful.

  1. Handy Macros 3.5.2 or later is installed on your Confluence Server/Data Center. We suggest using the latest app version compatible with your Confluence, as it brings the latest updates and fixes.

  2. The latest version of the Confluence Cloud Migration Assistant compatible with your Confluence is installed.

In Handy Macros 3.5.2, we replaced atlassian-app-cloud-migration-tracker with atlassian-app-cloud-migration-listener to support app migrations, so you can't migrate the app with lower versions.

Starting with app versions 3.13.0, 4.5.0, and 5.2.0 for Confluence 8, 9, and 10, respectively, we have improved the migration process to avoid transferring unused app data. It results in increased migration performance and optimization of migrated status sets, as only those used on Confluence pages will appear in Cloud. As a result of this change, you will experience the following limitations caused by ecosystem architecture:

  1. Handy Statuses used in templates at any level won't be migrated due to the lack of Confluence mappings between the DC and Cloud platforms.
  2. The Handy Status value may be unavailable after page restoration from previous versions in Cloud after migration.

Please keep these limitations in mind when running the migration. If you are sensitive to them, you can stick to previous app versions compatible with your Confluence, which migrate all app data. It will result in the transfer of unused sets and status values, additionally increasing the migration timeline.

Consider that Confluence Cloud page performance with many Handy Macros on it will be lower than on Data Center or Server. We recommend running a test migration in advance.