If your team used the Visio Data Visualizer add-in inside Excel, the old instructions are now a trap. Microsoft removed the add-in from AppSource in December 2025 and retired it on March 2, 2026. Existing embedded diagrams can stop loading, although the Excel tables remain. Microsoft advised subscribers to save important diagrams as .vsdx before retirement.
The need did not disappear: operations teams still keep process steps, owners, systems, and next-step IDs in spreadsheets, while customers and auditors still ask for Visio files. This guide compares three current ways to turn Excel or CSV data into an editable Visio diagram.
The useful output is not a screenshot of a spreadsheet. It is a diagram with editable shapes and connectors.
Quick answer
| Workflow | Best for | Main constraint |
|---|---|---|
| Visio Plan 2 desktop Data Visualizer | Data-linked corporate processes | Windows desktop workflow and Plan 2 license |
| CSV or Mermaid through a diagram editor | Simple, technical diagrams | Extra conversion and layout cleanup |
| AI document-to-VSDX workflow | Messy tables plus supporting documents | Generated structure must be reviewed |
The retired Excel add-in and the Visio desktop Data Visualizer are not the same product. Microsoft still documents the desktop templates and Create Diagram from Data wizard for Visio Plan 2. If your organization needs two-way synchronization between Excel and Visio, that remains the strongest native Microsoft route.
Workflow 1: Use Visio Plan 2 Data Visualizer on the desktop
Prepare an Excel table with one row per process step. At minimum, keep these fields separate:
- unique step ID;
- step description;
- next-step ID;
- connector label for decisions;
- function or department for swimlanes;
- phase, if the process has stages.
Open Visio, choose a Data Visualizer template, select the Excel workbook, map the columns, and generate the diagram. Microsoft documents basic flowcharts, cross-functional flowcharts, and audit diagrams in this workflow.
This route is appropriate when the spreadsheet is the system of record. Changes can be synchronized in both directions, and extra spreadsheet columns can become shape data. The trade-off is setup discipline: duplicate IDs, blank next-step fields, and inconsistent labels cause mapping problems. It also requires Visio Plan 2 and the desktop application.
Official reference: Create a Data Visualizer diagram in Visio.
Workflow 2: Convert the table into diagram code first
For a small flowchart, you can ask an AI assistant to convert the rows into Mermaid or another text-based diagram format. Review the code, import it into a compatible editor, fix the layout, and then use a separate conversion step if the final deliverable must be VSDX.
This is useful for developers who prefer text diffs and source control. It becomes awkward when the table contains several owners, exception branches, notes, and nested subprocesses. Diagram code is a representation, not an interpretation layer: it will faithfully draw a badly structured table.
Use a prompt that forces the model to expose uncertainty:
Read this process table. Return a flowchart specification with one node per unique Step ID.
Use Next Step ID only for connections. Treat blank next steps as end states.
For rows with multiple next steps, require one connector label per branch.
List duplicate IDs, missing targets, and ambiguous owners before writing diagram code.
Do not invent missing steps.
Workflow 3: Let AI interpret the workbook and generate editable VSDX
Spreadsheets are rarely clean enough to act as a diagram schema. A process workbook may have one sheet for tasks, another for owners, color fills that imply status, and notes that explain exceptions. In that case, the hard part is understanding the workbook before drawing anything.
VSDXAI accepts Excel or CSV alongside supporting PDF, Word, image, text, or audio sources. It extracts actors, steps, decisions, systems, and relationships, shows a reviewable plan, then creates editable shapes and connectors. The result can be adjusted in the embedded draw.io canvas and exported as a native .vsdx.
A practical request looks like this:
Create a cross-functional swimlane diagram from this workbook.
Use the Owner column for lanes, Phase for stage headers, and Step ID for traceability.
Treat values in Next Step ID as directed connections.
Show approval outcomes as Yes/No connector labels.
Before drawing, list missing owners, duplicate IDs, unreachable steps, and references to rows that do not exist.
Do not infer an owner when the cell is blank.
This route is strongest when the workbook is evidence rather than a perfect schema. The review step matters: an attractive diagram with an invented approval branch is worse than an untidy spreadsheet.
Clean the spreadsheet before any workflow
Run this check before importing or uploading:
- one stable ID per step;
- one action per row;
- owners use consistent names;
- decisions have explicit outcomes;
- every target ID exists;
- start and end states are identifiable;
- merged cells and decorative blank rows are removed;
- notes that change process logic are moved into a real column;
- sensitive columns not needed for the diagram are deleted from the copy.
Which route should you choose?
Choose Visio Plan 2 when bidirectional Excel synchronization is a requirement. Choose diagram code when the flow is small and your team wants a text-controlled artifact. Choose an AI-to-VSDX workflow when the spreadsheet is incomplete, spread across sheets, or needs to be interpreted with other source material.
The retirement notice is useful context, but it should not drive the architecture of your replacement. Start with the deliverable: synchronized data model, editable diagram source, or native VSDX file.
FAQ
Was every version of Data Visualizer retired?
No. The retired product was the add-in that ran inside Excel. Microsoft still documents Data Visualizer templates and the Create Diagram from Data wizard in the Visio desktop app for Plan 2.
Can I create a VSDX without owning Visio?
Third-party tools can generate a .vsdx file without a Visio license. You still need a compatible viewer or editor to inspect it, and complex files should be tested in the Visio environment used by the recipient.
Should I upload the original workbook?
Prefer a diagram-specific copy. Remove unrelated sheets, hidden columns, personal data, formulas that are not needed, and confidential notes. Keep the stable IDs and relationship fields required to verify the diagram.
Microsoft's retirement details are available in its official announcement. To turn a current workbook into a reviewable diagram and native VSDX, open the VSDXAI Studio.
Top comments (0)