# Import and export BPMN XML

Processes are real BPMN 2.0 files, which means they move between tools. Import one drawn elsewhere, or export yours to hand to an engine team.

Imported processes are laid out automatically, so a file with no diagram information still arrives readable.

![image-20260907-085926.png](https://help.gocapable.com/images/451e5765-bb35-4c31-9a62-ccfca82c33c1.webp)

---

## What this is for

* Bringing in a process modelled in another tool.
* Handing a process to a team that will deploy it.
* Keeping a process in version control alongside code.

---

## How it works

| **Action**       | **How**                                                                  |
| ---------------- | ------------------------------------------------------------------------ |
| Import           | Attach or paste a .bpmn or .bpmn20.xml file.                             |
| Automatic layout | Runs on import when the file carries no diagram interchange information. |
| Export           | Export the process as BPMN 2.0 XML.                                      |
| Round trip       | Export, edit elsewhere, and import back; the format is standard.         |

---

## A few things that catch people out

* A plain .xml file is read as draw.io. BPMN files need .bpmn or .bpmn20.xml to be detected correctly.
* Import warnings usually mean vendor-specific extensions the editor does not use. The process still works.
* Exported files include Camunda properties if you set any.

---

## Related

[BPMN keyboard shortcutsSelection, editing and undo.](https://help.gocapable.com/diagrams/bpmn-keyboard-shortcuts.html)

[Save a BPMN diagramDebounced changes, flushed on save.](https://help.gocapable.com/diagrams/save-a-bpmn-diagram.html)

[BPMN editorBack to the editor overview.](https://help.gocapable.com/diagrams/bpmn-editor.html)

---

_Simulate it before you publish it._