Update to 5.6.7
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. If you had previously done the Prepare Migration action, you can do a rollback now or continue migrating to cloud without doing the rollback. In both cases your content will work as expected both before and after migration.
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.
|Table of Contents|
Instructions to use
The Server/Data Center to Cloud migration of the MultiExcerpt macro can be performed without any loss of service for your macros on your Server or Cloud instances.
The MultiExcerpt macros have different names on Cloud than they do on Server/Data Center. For example, the "multiexcerpt" macro on Server/Data Center is "multiexcerpt-macro" on Cloud. In addition, the macros have a few parameters whose names need to be changed.
You will perform a migration with no loss of service on your Server/Data Center by enabling app/macro modules (on Server/Data Center) that use the MultiExcerpt macro names for MultiExcerpt-Cloud.
Enabling these app modules will allow you to rename your MultiExcerpt macros (on Server/Data Center) by editing them in your Confluence Storage Format XML (SFXML) representation of your pages. During this renaming process, the MultiExcerpt macros will work on your Server/Data Center while using either the Server/Data Center or the Cloud macro names. After the renaming is completed for all pages you can migrate your pages from Server/Data Center to Cloud. The pages are immediately ready for service on your Cloud instance.
You have two options on how you choose to migrate. You can follow the longer manual process or you can use our migration tool. To use the migration tool you must have version 5.6.0 or newer
Instructions for a manual migration (power users)
If Server Was Migrated to Cloud Without Editing Multiexcerpt Macros
If your Server site was migrated to Cloud without following the above steps to edit your Storage Format markup then the macros will not be recognized in Cloud:
If that has happened and you catch it immediately, before your Cloud site is open for production usage, then you may want to stop and redo your Server → Cloud migration and follow the above steps for editing your macros BEFORE importing to Cloud.
If redoing your migration is not an option then you must edit the Storage Format on your Cloud instance to change the macros so they are recognized:
The "PageWithExcerpt" and "MultiExcerptName" are parameters for the "multiexcerpt-include" macro. You will see those parameters when you find a "multiexcerpt-macro".
Our Storage Editor plugin is an example of a tool that can be used to edit Storage Format in Cloud.
You will need to find all of the pages that contain "multiexcerpt" and "multiexcerpt-include" macros so you can edit the Storage Format on those pages.
The Confluence Cloud search API is not usable for finding the pages with "multiexcerpt" and "multiexcerpt-include" macros. CQL can only find macros that are successfully installed on your instance. It can find "multiexcerpt-macro" macros on Cloud because that is a valid macro that you can and will install on your Cloud instance. However, it cannot find "multiexcerpt" macros that you have imported in your markup from your Server instance. In addition to the limitations of CQL searches, the search API in Cloud is significantly buggy and is not reliable for finding macros in Cloud sites.
If your site is large enough that you cannot find the broken MultiExcerpt macros manually by navigating your site then you may want to consider doing the search on your SERVER instance and then use those results to know which pages need editing on your Cloud instance. The advanced search (using CQL) to find macros is reliable on Server:
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.
|Content by Label|