Excel to process map: how the conversion actually works
You have process steps in Excel. You want a diagram. Here is exactly what happens between pasting your rows and getting a swimlane process map — the column mapping, the connection syntax, and the parts Excel alone can't do.
The core idea: rows are steps, columns are diagram semantics
Every process map is built from the same primitives: steps, shapes, connections, and lanes. An Excel sheet describing a process usually has those primitives already — a step description column, an owner column, maybe a "next step" or sequence column. The conversion is a column mapping, not a redraw.
- Step description → Box Text (the label inside the shape)
- Step type → Shape (Start, Process, Decision, End)
- Next step / sequence → Line To (row numbers, comma-separated for branches)
- Owner / department → Horizontal or Vertical Lane (the swimlane)
The paste workflow
Select your rows in Excel, copy, click into the editor's spreadsheet, paste. The editor accepts tabular clipboard data directly — the same way you'd paste between two Excel sheets. From there, adjust the Shape and Line To columns and the diagram assembles itself in real time.
There is no template to match. Unlike Visio Data Visualizer, which requires exact column names in a fixed Excel template, the editor's columns are visible and editable in place — you align your data to them by pasting into the right columns, not by reformatting your workbook.
What about decision branches?
Excel can store a branch ("if approved go to step 5, else step 8") but it can't render one. In the editor, set the row's Shape to Decision and put both targets in Line To: "5,8". Label the branches in Line Text: "Approved,Rejected". The diamond renders with two labelled connectors.
What about swimlanes?
If your Excel sheet has an owner column, that column is your swimlane assignment. Each unique value becomes a lane; each step is placed in its owner's lane automatically. Cross-lane connectors — the handoffs — render without any manual alignment.
Comparison: this workflow vs. Visio Data Visualizer
Visio Data Visualizer did the same conceptual job — Excel rows in, diagram out — but Microsoft retired it: pulled from Excel in January 2026, service shut down March 2, 2026. Its replacement path is a paid Visio Plan 2 subscription with the Visio desktop app. The browser-based workflow needs none of that, and it works on Mac and Chromebook.
If your organization needs .vsdx output for SharePoint pipelines, Visio Plan 2 is the fit. For everyone else — including anyone holding a stranded Data Visualizer Excel table — the browser editor is faster to start and free. The columns map one-for-one; see the migration guide below.
Frequently asked questions
Do I need an Excel add-in to convert Excel to a process map?
No. Copy the rows in Excel and paste them into the editor in your browser. No add-in, no Visio, no Microsoft 365 commercial license.
Does my Excel file need a specific template or column names?
No. You paste data into the editor's visible columns (Box Text, Shape, Line To, lanes). There is no fixed workbook format to match.
Can I go back to Excel afterwards?
The spreadsheet inside the editor stays editable — it is the source of truth for the diagram. You can copy rows back out to Excel at any time.
Try it on your own process
The editor is free and opens with a starter template. One row per step — the swimlane diagram renders as you type. No signup required.
Start Process Mapping Free