The BPMN Converter in BlueDolphin helps you convert BPMN views created in the legacy editor into BPMN diagrams (now called Processes).
It’s easy to use, ensures compliance with BPMN 2.0 standards, and lets you review and adjust diagrams before saving, making it perfect for streamlining your move to the Processes.
For more information about migration approaches for converting BPMN diagrams, roles, and permissions, see the BPMN overview article.
Pre-requisites
The Converter add-on is enabled for the tenant.
You have any of the mentioned roles assigned to you.
You own the legacy BPMN view, or it has been shared with you.
You know which diagrams should be converted first and why.
In the Main menu, click the Processes and select the Converter tab.
Click the Select existing BPMN view to see a list of legacy BPMN views you own or have been shared with you.
The list displays details such as the diagram name, owner, last edit date and time, view type, conversion status, and available actions.
Select the legacy BPMN view you want to convert and click Convert.
The converted view gets displayed as a diagram for you to review. Adjust the layout or alignment of the objects before saving the diagram.
Legacy BPMN diagram
Converted BPMN diagram
BPMN converter also runs BPMN 2.0 validation rules check. Click the icon to see the full list of checks.
: The green icon means validation found no issues
: The error or warning icon means validation found issues that were fixed, and/or there were errors related to BPMN 2.0 compliance. Review the messages carefully before saving and using the converted diagram.
Click the Save as BPMN diagram button to save it as a diagram. The saved diagram is available under the Diagrams tab.
NOTE: In the Processes, each user must use a unique view name. If you see an error message stating that the name already exists, rename your diagram and save it again.
Click the Select existing BPMN view button on the lower right side to continue and convert the next view.
Review the Converted Diagram
After conversion, compare the converted diagram with the original legacy view. Review the following areas:
Layout: Check for misaligned elements, overlapping connectors, unclear labels, or unexpected layout changes.
Validation: Review and resolve any BPMN validation warnings or errors, where applicable.
Naming: Ensure the diagram name is meaningful and unique within Processes.
Pools and Participants: Remove or rename default or automatically generated names if they are not meaningful.
Ownership: Verify that the correct process owner is assigned to the converted diagram.
Related Information: Review any relevant metadata, questionnaires, publication status, and governance information.
Adoption: Inform users that they should continue all BPMN work in Processes and must not update the legacy version.
Example Cleanup Action
If a pool has a default name such as "Pool / Participant", remove or rename it to a meaningful name that reflects its purpose.
For additional questions about the BPMN Converter, see the Processes Frequently Asked Questions article.




