Please go through our step-by-step instructions to migrate the Handy Macros app's data to Confluence Cloud. Please address your questions or issues to our support.

Please consider that update of the migration progress may be stuck for a while with no percentage update.

The expected migration duration depends on the following factors:

  1. amount of migrated data
  2. load on the Handy Macros Cloud app

In large instances, migration of all Handy Macros data can take from 24 to 48 hours.

You should run only one migration at a time. Running multiple migrations simultaneously across different spaces causes the system to cancel the extra processes. As a result, some data may not be transferred, leading to non-clickable statuses on pages.

Checking pre-requisites

Before proceeding to migration of the Handy Macros app from Confluence Server/Data Center to Confluence Cloud, please check our Pre-Migration Assessment Checklist.

Assessing the app for Cloud migration

  1. Navigate to the Confluence administration console.
  2. On the navigation sidebar, select Migration Assistant.
  3. On the opened page, in the Assess your apps box, click Begin assessing. 

  4. On the Assess your apps page, select Needed in cloud for the Handy Macros app. Choose the status for the rest of the apps if you plan to migrate multiple apps.

  5. Click Done. 

Prepare the app for Cloud migration

  1. Navigate to the Confluence administration console.
  2. On the navigation sidebar, select Migration Assistant.
  3. On the opened page, in the Prepare your apps box, click Begin preparing. 

  4. In the Connect to cloud window, click Choose cloud site. 

  5. In the pop-up window, click Continue. 

  6. In the Migrate from field, enter the base URL of your Server/Data Center instance.

  7. In the Migrate to field, choose from the dropdown menu the Cloud site to which you want to migrate. 

  8. Tick the Allow Atlassian to access migrations data and click Confirm.

  9. You will be redirected back to the Connect to cloud page. Click Continue. 

  10.  If you have not yet installed the app, click Install the app. 

  11. Once the app is installed, click Continue. 

  12. Click View policy. 

  13. Review the policy and click Confirm. 

  14. Click Done. 

Migrate your data

  1. Navigate to the Confluence administration console.
  2. On the navigation sidebar, select Migration Assistant.
  3. On the opened page, click on the Migrate your data box. 

  4. Click Create new migration. 

  5. Click Connect to cloud. 
  6. Name your migration.
  7. Choose the migration stage from the dropdown menu. 
  8. Choose your destination cloud site from the dropdown menu.
  9. Click Choose what to migrate.

  10. In the Apps box, click Select after selecting Global templates, Spaces, Users and groups. 

  11. Select All and click Add to migration. 

  12. Click Check for errors.
  13. Evaluate errors and warnings. If everything looks good, click Review Migration.

  14. Click Run now. 
  15. Wait for the migration to end. 
  16. Migration is complete. 

Migrated status sets in Confluence Cloud

Note that Handy Status in Cloud doesn't have the distribution between individual, space, and global sets. That means that after successful migration all your statuses will be visible and editable on Confluence pages, but they all will appear at the same level. You can see the indication of their level in Handy Status in Server/DC in the names that they get after migration. The naming rules are the following:

  • global sets will retain their name as in Server/DC

  • space sets will be named after the "SET_NAME space(SPACE_KEY)" pattern

  • individual sets will be named after the"SET_NAME personal (ATLASSIAN_USER_ACCOUNT_ID)" pattern.

If you copied status sets from the space or global level to the personal level before migration, these status sets would appear with global: or personal: prefix. You can get an error in the log for when CCMA is migrating Handy Macros to the Cloud site similar to the one below:

[handy.macros.migration.LocalCloudMigrationListener] lambda$null$15 HANDY MACROS - MIGRATION. Could not get CONFLUENCE user BY USERKEY key=confluence.userkey/2c94a8c75bd6da67015bd6dbc8640007, selectorUserKey=confluence.userkey/
CODE

The migrated status will appear in your Handy Status admin section with a notice about an unknown accountID. 

There's no need to worry about the unknown accountID. The Server app could not find a user with a particular key at your Confluence Cloud instance while performing the migration. There is no impact. It's just a name. We implemented this approach to separate different status sets and help users find their status sets. You can always change the status set name as you wish  to avoid users' distraction.

If you have any doubts or questions about migration, contact us. We're always happy to help you.

Additionally, we have the FAQ section that can be helpful.