Features described on this page

Cloud Migration - Automated Path (CMA) SERVER | DATA CENTER Cloud

|3.55.0-ENTERPRISE / 3.55.0-C10-ENTERPRISE, 3.0.0-CLOUD|

BPMN Modeler Enterprise supports automatic Cloud Migration via Confluence Cloud Migration Assistant.

Open

Make sure BPMN Modeler Enterprise is marked as “needed in cloud” in the app assessment, is installed in Confluence Cloud and “Apps” is included to your migration plan.

Workflow

Once added to the app migration plan, the Confluence Cloud Migration Assistant will perform the following steps:

1. Migrate your selected Confluence Spaces to Cloud

2. Inform BPMN Modeler Enterprise about the migration and start the app migration process

BPMN Modeler Enterprise app migration will consist of two chronological phases:

1. Macro Upgrade: In this phase, legacy “BPMN Modeler” macros on Confluence pages are upgraded to “BPMN Modeler Enterprise” macros.

2. Diagram Migration: In this phase, links within BPMN diagrams, such as links to Confluence pages, other diagrams or attachments are repaired to work seamlessly in your new Confluence Cloud environment. For more details, see [BPMN Modeler] Cloud Migration | Diagram Migration How it worksPreview

Open

Assessing the app migration

Once a migration phase is finalized, an overall status is indicated as either COMPLETE or FAILED. Note that a FAILED migration can be re-run any time. This allows to simply re-run the phase after taking necessary actions on the Cloud instance. To re-run a complete migration, please create a new app migration in Confluence Migration Assistant.

Open

Macro-Upgrade Logs

During the macro-upgrade phase, migrated Confluence pages are checked for the presence of legacy “BPMN Modeler” macros. The procedure will upgrade these macros in Confluence Cloud to “BPMN Modeler Enterprise” macros with a Confluence page update. Thus, the Confluence User “BPMN Modeler Enterprise” needs to have sufficient permissions to:

• VIEW and UPDATE the Confluence page the diagram resides on

Diagram-Migration Logs

The diagram migration will check all Confluence pages with BPMN Modeler Enterprise macros for diagrams with repairable links. To assess and possibly repair a link in a diagram, the Confluence User “BPMN Modeler Enterprise” needs to have sufficient permissions to perform the following steps:

• VIEW and UPDATE the Confluence page the diagram resides on

• VIEW and UPDATE the related diagram’s attachment on this page

• VIEW the linked content, such as pages or attachments

Depending on the different problems that can occur, the overall migration status is determined as follows:

• failed If viewing or updating a Confluence page or its diagram attachment failed (most likely due to insufficient app user permissions)

• COMPLETE If none of the above occurred, but migrating a single link within a diagram failed (most likely due to insufficient app user permissions on the linked resource) → To identify failed link migrations, please inspect the diagram-migration log file for entries with [Status: partial]!

• COMPLETE If no errors occurred

Assessing the Diagram Migration

To assess your diagram migration in detail, the log file includes a more granular migration status for each processed Confluence page.

• [Status: failure] - this outcome led to the overall migration status FAILED . So if your logs include an entry with that status, this is the reason why the migration is considered failed. You now have the possibility to fix potential permission problems and re-run the migration again.

• [Status: partial] - some links within the diagram could not be migrated correctly but there were no issues to inspect or update the diagram itself. It could also be the case that linked resources were not part of your current or any prior migration and thus could not be repaired. Therefore, we do not consider failed link migrations as a failed migration in a broader sense. Please consult the Migration Report in the log file for details and possible solutions. To re-run the partial migration after fixes were applied (most likely app user permissions or migration of linked content), please set-up a new app migration within the Confluence Migration Assistant. All diagrams will be tried to be migrated again.

• [Status: success] - no problems were identified.

Migration Report JSON

All log entries include a Migration Report in JSON format after the [JSON] keyword. This report includes details about occurred problems, drilled down to diagram-link level. To investigate the issues, please review this report and make necessary changes. Afterwards, re-run the migration.

Migration Report Structure

Open

Diagram Migration Report Example

In the Migration Report above, we can see that

• The Confluence Page “Insurance Processes” contained 1 BPMN Diagram “Handle Windshield Claim”

• Two diagram versions were updated (the latest attachment version, and a diverging “currently published” version (see [BPMN Modeler] Cloud Migration | Diagram Migration How it worksPreview).

• The overall migration status is “partial” → There were links in the diagram that could not be repaired

For simplicity, we investigate only problems of the migration of the latest attachment version here:

• One link could not be repaired because the linked page (Data Center page id 63275009) could not be matched in Confluence Cloud. Possible reasons are:

  • The Confluence User “BPMN Modeler Enterprise” has no permission to VIEW the corresponding Cloud page

  • The Data Center page was not part of your current or any prior migration plan

  • The corresponding Cloud page was deleted

• One link could not be repaired because the linked attachment “view-restricted-attachment-1.pdf” could not be found in Confluence Cloud. Possible reasons are

  • The Confluence User “BPMN Modeler Enterprise” has no permission to VIEW the corresponding Cloud attachment

  • The attachment was deleted in Cloud

  • The Data Center page containing the attachment was not part of your current or any prior migration plan (not applicable here, since we were able to map Data Center page 73400375 to Cloud page 42729555)

Diagram Migration - How it works

Our app primarily consists of two components: The macro on the Confluence page (i.e., the diagram you create) and a related Confluence page attachment “.bpmn” file. Essentially, the macro displays a specific version of the related diagram attachment. Every time a diagram is changed and saved, a new attachment version is created in the Confluence page attachments.

The “diagram-migration” phase updates either the latest and/or the currently published diagram attachment version. If the currently published version was updated, the macro is updated as well to now publish the migrated version. This happens through one Confluence page update for all macros on the page.

Note: Due to an arbitrary number of possible diagram versions, only the two versions (latest/published) are migrated. All other diagram versions are not processed.

The table below shows which attachment versions are updated during the “diagram-migration” phase in different scenarios:

Scenario 1: No links to repair in neither latest nor published version

Scenario 2: Published version and latest version have links to repair

Scenario 3: Only latest version has links to repair, published version does not

Scenario 4: Published version has links to repair, latest version does not

In this case, the latest attachment version is still updated to remain the “latest” version.