For swimlanes: Swimlane diagrams.
Visio Data Visualizer template (TSV + Excel)
Data Visualizer imports are strict. This page provides a clean template you can copy, import, and adapt without guessing headers or structure. Start with a known-good dataset, then replace the rows with your real process steps.
Format rules: dataset format. Known-good examples: basic and cross functional.
How to use these templates
- Copy the TSV template into a plain text file.
- Save it as .tsv (tab-separated values).
- Import it into the correct Data Visualizer diagram template in Visio.
- Confirm it renders cleanly.
- Replace the rows with your real process steps, then re-import to regenerate.
If the goal is converting an existing .vsdx diagram into a dataset, start here: Visio diagram to Excel.
Which template should be used?
- Basic flowchart – 1 owner, simple logic, fastest validation.
- Cross functional flowchart – multiple teams, swimlanes, handoffs, phases.
For swimlane-focused guidance and internal linking: Swimlane diagrams hub.
Basic flowchart template (TSV)
Copy, paste, save as .tsv, then import into Basic Flowchart (Data Visualizer).
Process Step ID Process Step Description Next Step ID Connector Label Shape Type
010 Start – Begin 020 Start
020 Process step goes here 030 Process
030 Decision goes here 040,050 Decision
040 Path A step 060 Process
050 Path B step 060 Process
060 End – Done End
Working example with import-ready structure: basic flowchart dataset example.
Cross functional flowchart template (TSV)
Copy, paste, save as .tsv, then import into Cross-Functional Flowchart (Data Visualizer).
Process Step ID Process Step Description Next Step ID Connector Label Shape Type Phase Function
010 Start – Begin 020 Start Intake Requester
020 Process step goes here 030 Process Intake Coordinator
030 Decision goes here 040,050 Decision Review Coordinator
040 Path A step 060 Process Execute Ops Team
050 Path B step 060 Process Execute Ops Team
060 End – Done End Close Requester
Working example with lanes and phases: cross functional dataset example.
Excel version and editing tips
Many teams build the dataset in Excel first, then export to TSV for import. The key is to preserve exact headers and keep Step IDs stable.
| Tip | Why it matters |
|---|---|
| Use a controlled list for Function values (swimlanes). | Prevents lane sprawl (Ops vs Operations vs Ops Team) and keeps counts meaningful. |
| Keep Phase values small and consistent. | Makes diagrams readable and supports stage-based pivots. |
| Do not reuse Step IDs. | IDs are the backbone for versioning, auditing, and re-rendering. |
| Store branching in 1 cell (comma-separated IDs, no spaces). | Prevents broken connectors and import failures. |
| Never leave blank rows in a TSV export. | Blank lines can cause import errors even when the dataset looks correct. |
For deeper analysis after the dataset exists: audit in Excel and AI analysis.
Validation checklist (before import)
- Headers match exactly. Do not rename columns.
- Step IDs are unique. No duplicates.
- Every Next Step ID exists. No missing references.
- No blank rows. Including at the end of the file.
- Branching is stored correctly. Comma-separated IDs, no spaces.
- Shape Type values are valid. Start, Process, Decision, End (and consistent casing).
If Visio rejects the import, start here: import troubleshooting.
Next steps
Conversion path: validate with Lite, then scale with Standard.
FAQ
Is this an official Microsoft template?
No. Microsoft, Visio, and Excel are trademarks of Microsoft. This page provides independent templates and examples designed to match Data Visualizer requirements.
Why does Data Visualizer reject “almost correct” datasets?
The importer is strict. The most common causes are header mismatches, duplicate Step IDs, missing referenced Next Step IDs, blank TSV rows, or invalid Shape Type values.
Should TSV or Excel be used for the dataset?
Either works. Many teams edit in Excel, then export to TSV for import. The key is preserving headers, stable IDs, and clean formatting.
What is the fastest way to validate the workflow?
Run a real diagram through Lite first to validate the first 20 steps. If the workflow fits, Standard removes the limit for full-size conversion and ongoing updates.
Where do swimlane templates live?
Swimlane-specific templates and guidance are organized under the swimlane hub: /visio-data-visualizer/swimlane-diagrams/.
Microsoft, Visio, and Excel are trademarks of Microsoft. This site describes an independent tool and is not affiliated with Microsoft.
