...
Install the latest version of BPMN Modeler Enterprise (>= 3.22.1-ENTERPRISE)
In case you are using the BPMN Modeler Free, get a free trial version of the BPMN Modeler Enterprise at no cost. Since February 2023 Atlassian does not issue new licenses, even trial licenses for Server Apps. You can simply download and install the BPMN Modeler Enterprise for Confluence Data Center as a trial: https://marketplace.atlassian.com/apps/1219284/bpmn-modeler-enterprise?hosting=datacenter&tab=overview
BPMN Modeler Free and Enterprise versions can be installed in parallel. So uninstalling your BPMN Modeler Free beforehand is not required
As Confluence administrator, perform the Upgrade procedure to make sure all of your diagrams are upgraded to ENTERPRISE, as described here: [BPMN Modeler] Features for Confluence Admins
We recommend doing this even if you are already using BPMN Modeler Enterprise. Maybe some old FREE diagrams are hiding somewhere from earlier days!
After completing the upgrade procedure, it is necessary to perform a Re-Indexing of your Confluence pages
After Re-Indexing completion, verify that there do not exist any more FREE diagrams in your Confluence by performing the Analysis again
Go to the App Configuration of BPMN Modeler Enterprise. Find the tab Cloud Migration and trigger the export of page data. Keep this file in a place where you will find it again.
Migrate your pages to Confluence Cloud. Please make sure to carry over all your page attachments for the BPMN diagrams . All ENTERPRISE diagrams (page macros) will be recognized seamlessly after installing the BPMN Modeler Enterprise Cloud app.
In Confluence Cloud: To synchronize BPMN or DMN diagram links, Confluence page and attachment linkslinks, Confluence attachment links, external content links (web URLs) or Jira links, navigate to Manage apps > Configure BPMN Modeler Enterprise. Find the tab Cloud Migration and import page data by uploading the file you downloaded in step 4.
Please note: It can happen that some linked page attachments cannot be uniquely determined and thus . After the link migration is done, you will either get a success message or a warning message with detailed information for every single link migration that has failed so that you might migrate these links by hand if necessary. Links are migrated as follows:BPMN or DMN diagram links will work the same way as they did on your OnPremise Confluence instance.
Confluence page links will be migrated seamlessly and will link to the corresponding migrated Confluence Cloud page.
Confluence attachment links will also link to the corresponding migrated attachment in your Confluence Cloud instance. Unfortunately, due to technical reasons if two attachment with the same name exist in one Confluence space, it can not be uniquely determined to which one of the two a link must be set. Thus, the link must be reset manually if necessary and will be logged in the warning message after the import is completed.
External content links (web URLs) will stay the same way as in your OnPremise instance with one exception: If Confluence page links were not set using the Confluence page link feature but instead have been copied and pasted as URLs into the external content link feature by your users, our migration tool will detect this. It will then reset the URL which previously linked to a Confluence OnPremise instance to your Confluence Cloud instance so that the link is not broken or outdated after the migration.
The Jira link feature is not available at this point in Confluence Cloud due to technical reasons. We thus reset all Jira links as external content links (web URLs) so that your Jira links are not lost. Please note, that web links will link to the Jira instance which was connected to your Confluence OnPremise instance.
Done. All your BPMN diagrams , including diagram and Confluence links, with all of their links are ready to use.
Happy modeling!
...