Export and re-import
What survives a round-trip.
Generating a report (.docx)
The first item in the Export menu. It gathers everything the tool computed into one Word file you can just open and read, with no need to come back to the page:
- The headline metrics — expected time and cost, the fastest → slowest range, P50/P90, the size of the process.
- The overall assessment — bottlenecks, where cost piles up, the extra time caused by rework, the variability, and where data is still missing.
- The BPMN diagram and the analysis chart — real images, with the critical path and loop-back flows marked.
- The step table (with expected run counts), the detailed line items if there is a breakdown, the flows and conditions, and the scenarios.
- How the numbers are calculated — so whoever receives the report knows where they come from.
Every statement comes with the number it was derived from — for example “this step accounts for 30,5% of total processing time (2 hours out of 6 hours 34 minutes)” — so you can verify it against the step table in the very same file. A version that uses AI for deeper commentary and action recommendations is being prepared; it will sit alongside this section rather than replace it.
A twenty-step diagram shrunk to fit one page has very small text. The images in the file are drawn at high resolution, so they stay sharp when you enlarge them in Word; the full figures are in the step table.
The export formats
| Format | Used for | What it preserves |
|---|---|---|
.drawio | Reopening in diagrams.net, carrying on editing | Layout, time, cost, probability, gateway type |
.bpmn | Loading into Camunda, Bizagi… | Structure, names, time; cost lives in the documentation element |
.mmd (Mermaid) | Pasting into docs, Confluence, GitLab, a README | Structure and labels |
Step table .csv | Excel, Power BI | Every step attribute |
Flow table .csv | Excel | Connections and probabilities |
Scenarios .csv | Reports, charts | Every scenario with its formulas |
Detailed line items .csv | Excel | Each line item within the steps that were broken down |
Report .docx | Sending to your boss, filing, printing for a meeting | Metrics, assessment, both diagrams and every data table |
| The original file | Getting back the original you uploaded | Exactly as uploaded |
Does exporting and re-importing lose anything
With .drawio, no. Time and cost are written into the label using the convention
name 30 minutes · 120k, probability goes into the flow label, and the gateway type goes into
the style attribute:
elif node.type == "gateway":
# gwType giữ lại loại cổng: thiếu nó thì import lại sẽ thành XOR hết
style = f"rhombus;whiteSpace=wrap;html=1;gwType={node.subtype or 'exclusive'};"The first version did not write
gwType. Export and re-import, and every parallel gateway
turned into an exclusive one — time went from max(120, 20) to a weighted
average, off by tens of minutes, with nothing looking wrong on the diagram. The test suite
now has a dedicated case locking this bug down.
Exporting the diagram as an image
Both diagrams are SVG. Right-click the picture to save the image, or export .drawio and
use diagrams.net to export PNG/PDF at whatever resolution you want.
Importing from another tool
In the other direction, you can draw anywhere as long as it exports draw.io or BPMN 2.0. See Supported file formats for how to write the labels so the tool reads the time and cost right from the first upload.