Import and export DMN XML

DMN models are standard DMN files, so they can be imported from and exported to other tools, or kept in version control alongside the code that uses them.

The same extension rule applies as everywhere else: a plain .xml is read as draw.io, so keep the .dmn ending.

#What this is for

Importing a model built in another DMN tool.
Handing a model to an engine team.
Keeping decision logic in version control.

#How it works

Action	How
Import	Attach or paste a .dmn file.
Export	Export the model as DMN XML.
Round trip	The format is standard, so a model can move both ways.
Extension	Keep .dmn. A bare .xml is treated as draw.io.

#A few things that catch people out

Import warnings usually mean vendor extensions the editor does not use.
Exported files include Camunda properties if you set any.
Version the exported file alongside whatever consumes it, so the two cannot drift.

DMN keyboard shortcuts

Mostly table navigation.

Save a DMN decision

Flushed, then written as DMN XML.

DMN editor

Back to the editor overview.

Draw the map before writing the rules.