The MultiExcerpt macros have different names on the Server than on the Cloud. For example, the "multiexcerpt-macro" macro on Cloud is "multiexcerpt" on Server. In addition, the macros have a few parameters whose names are different. You will perform a migration with no loss of service by enabling app/macro modules (on the Server) that use the MultiExcerpt macro names for MultiExcerpt-Cloud.
Migrate your content from the Cloud to the Server.
Export Confluence pages from Confluence Cloud and import into Confluence Server
On your SERVER: enable the MultiExcerpt modules for MultiExcerpt macros with Cloud names
Navigate to 'Manage apps'
Confluence Admin > Manage apps
Expand the section for your Multiexcerpt plugin
Expand the 'modules' section within the Multiexcerpt plugin section
Disable these two modules:
Enable these modules:
For future support:
Please alert Artemis Support that you are using migrated macros so that they know why your Server macro names are not the default.
When migrating Server Multiexcerpt macros to the Cloud, they appear as legacy macros. Those macros will have the same functionality as macros created in the fabric editor.
Is the “legacy” notation indicating that we need to do something active for the app to have full functionality? No, legacy macros have the same functionality as new-style macros. After migrating server macros to the cloud, they will be fully functional.
Is the “legacy” notation an indication that the migrated data in MultiExerpt will become deprecated at some point in the future? We will continue to support the legacy macros. There is no need to worry that we will deprecate these macros.