Migrating MultiExcerpt from Server/Data Center to Cloud
Update to 5.6.10
We have released an update so that you no longer need to do the "Prepare Migration" step described below. MultiExcerpt Cloud now recognizes the MultiExcerpt Server macros after following the standard Confluence Cloud Migration Assistant process. You do NOT need to take any special action to migrate your MultiExcerpt macros to Cloud.
This was started in 5.6.7 and then was fully implemented in 5.6.10. In 5.6.7 the tools for migrating MultiExcerpt Server to Cloud were removed and only the 'rollback' migration tool was left in place. In 5.6.10 the removal was completed and the 'rollback' migration tool is now gone too.
If you had previously done the Prepare Migration action to prepare one or more spaces, you can continue migrating your instance to Cloud without finishing your MultiExcerpt migration and without doing a rollback. MultiExcerpt Cloud will accept either unchanged Server markup or it will accept markup that was migrated to Cloud using the pre-5.6.7 migration tools.
Please make sure you review Differences between the Server, Data Center, and Cloud MultiExcerpt App
Note: there is no Cloud equivalent of the Server/Data Center macro for MultiExcerpt Enhanced Permissions so you will need to consider your strategy for Cloud excerpting of restricted resources before you do this migration.
Instructions to use
Instructions for a manual migration (power users)
If Server Was Migrated to Cloud Without Editing Multiexcerpt Macros
Licensing
Atlassian has some guidance on the licensing policies for migrations here: Transfer your self-hosted license to cloud
See the section entitled "App licenses". The policy for app licenses is that there is no transfer or credit from Server/Data Center towards a Cloud license (sorry).
Application vendors rely on Atlassian for licensing and purchasing, for which Atlassian charges a percentage of the license fee. We are always happy to hear feedback on licensing policies but be aware that they are set and controlled by Atlassian and that feedback given directly to them about their policies is probably the best way to get it heard by the folks who set the policies.
Related articles