The problem: Visio cannot open .bpmn files
Camunda Modeler saves diagrams as .bpmn files, which are BPMN 2.0 XML. Microsoft Visio has no native BPMN import. Drag a .bpmn file onto Visio and nothing happens. There is no Microsoft add-in that fixes this, and Camunda treats Visio as a competitor, not a target.
Yet the request is constant: process analysts model in Camunda because the engine executes BPMN directly, but stakeholders, steering committees, and compliance reviews live in Visio and PowerPoint. You need the same diagram on both sides.
The reliable path: BPMN XML to VDX
Visio's interchange format is VDX (Visio 2003-2010 XML). The workflow that works:
- Export from Camunda Modeler — File, Save As is already .bpmn (BPMN 2.0 XML). Keep the
BPMNDiagramsection in the file; it holds your layout (positions, connection routes). Exporting "semantic only" XML loses the visual layout. - Convert the XML to VDX — a converter maps each BPMN element (tasks, gateways, events, pools, sequence flows) to the equivalent Visio shapes and writes a .vdx file. You can do this for free and client-side with the Formatho BPMN to Visio converter: paste your BPMN XML, download the VDX.
- Open in Visio — File, Open, pick the .vdx file. No plugin or stencil installation needed. Every recent Visio version reads VDX natively, and from there you can edit, restyle, and paste into PowerPoint.
The whole path takes under a minute, and because the conversion runs in your browser, the diagram never leaves your machine — relevant if your process models are internal.
Three gotchas that break conversions
1. Missing BPMNDiagram section
BPMN 2.0 separates semantics (what the process does) from diagram (where shapes sit). If your export has no BPMNDiagram element, converters have to auto-layout, and the result rarely resembles your original. Camunda Modeler always includes it; some CI pipelines that generate BPMN do not.
2. Collapsed sub-processes
A collapsed sub-process shows as a single task with a marker. The child process lives in a separate diagram. Convert the child separately if stakeholders need the detail level.
3>Custom namespaces and extensions
Camunda adds its own extension elements (camunda:assignee, camunda:expression and friends). They carry execution config, not visual meaning — converters drop them, which is correct for a Visio deliverable, but do not expect execution properties to survive the round trip back.
Checking the result before you present it
After conversion, open the .vdx in Visio and verify: pools and lanes kept their order, gateways kept their XOR/AND markers, boundary events stayed attached to their tasks, and label positions are sane. A quick render of the original BPMN side by side catches anything the converter misplaced.
Alternatives, ranked
- Rebuild by hand in Visio — exact, and an hour per diagram. Fine once; unsustainable for a process library.
- Screenshot the Camunda canvas — fast, not editable, and pixelated on a projector. Stakeholders ask for changes, and you are back to rebuilding by hand.
- Camunda Play screenshots with the SVG export — SVG imports into Visio as a picture, not shapes. Editable-ish, painful.
- XML to VDX conversion — real Visio shapes, native open, free. This is why the path above is the standard answer.
Round-tripping back to Camunda
One honest warning: treat the Visio copy as a deliverable, not a source of truth. Editing the process in Visio and converting back to executable BPMN is possible in principle but lossy — Camunda extensions and execution semantics do not survive. Model in Camunda, convert to Visio when humans in suits need it, and keep the .bpmn file as the master.
Try it
Paste a Camunda .bpmn export into the BPMN to Visio converter and get a VDX you can open in Visio immediately — free, no account, nothing uploaded. If you only need to view a diagram, the BPMN Viewer renders any BPMN 2.0 XML directly in the browser.