Exporting process maps as Visio (.vsdx)
Export single or bulk process maps as native Microsoft Visio (.vsdx) files. Labs opt-in, the export menu, the bulk export page, the MCP/agent tool, plan limits and troubleshooting.
Written By Jack Finnegan
Last updated About 2 hours ago
BA Copilot: Visio (.vsdx) export
BA Copilot can now export your process maps as native Visio (.vsdx) files that open in Microsoft Visio. Round-trip with Visio import means you can pull a .vsdx in, edit in BA Copilot, and push it back out as .vsdx for stakeholders who still live in Visio.
Visio export is an opt-in Labs feature β your first time using it, BA Copilot asks you to acknowledge it's still being refined.
Quick answer
You want to⦠Use
Export one map you're looking at The single-map Visio (.vsdx) option in the Export menu
Export many maps from a space at once Import / Export β Export β Visio (.vsdx) in the sidebar
Include .vsdx alongside other formats in a bulk export The format checklist on the general bulk export page
Trigger a Visio export from Claude / an agent The
export_process_map_to_visioMCP tool
Turning on the Visio export Labs feature
The first time you click any Visio export entry-point, BA Copilot shows a Labs acknowledgement dialog explaining the feature is experimental β you opt in once and the option stays on for your account. You can revoke it any time from Settings β Labs. The Visio menu items show a small Labs pill (yellow warning colour) so you always know it's a Labs feature.
Single-map export
Open the process map you want to export.
Click Export in the top bar.
Pick Visio (.vsdx).
The file downloads to your machine. The filename uses the map title (e.g.
Order approval process.vsdx).
The exported file preserves pools, lanes, tasks, gateways, events, sequence flows, message flows, data objects, data associations and annotation leaders. Any appearance theme you've baked into the map travels with it.
Bulk export β many maps at once
The Export β Visio (.vsdx) entry under the sidebar Import / Export group opens the dedicated bulk export page.
Open Import / Export β Export β Visio (.vsdx) in the sidebar.
Browse each space (search bar in the header), expand the spaces you want, and tick the maps you want to export. Selecting a folder cascades to its contents.
Click Export selected as Visio.
You get a
.zipcontaining one.vsdxper map. The download starts automatically.
If a map can't be converted (e.g. a process is too unusual for the converter to handle cleanly), BA Copilot skips it instead of failing the whole batch and lists the skipped filenames at the top of the page so you can investigate them individually. A simple BPMN sequence-flow problem usually means the source map has a degenerate element β open it, save once, then re-try.
Including Visio in a general bulk export
If you're already exporting from the general bulk export page (where you pick formats and quality), you can tick Visio (.vsdx) alongside PDF, PNG and BPMN. The Visio files appear in the same .zip next to the other formats.
Visio export from Claude (MCP) and the agent
If you've connected BA Copilot to Claude via MCP, there's now a tool called export_process_map_to_visio that returns a download URL for the .vsdx. Sample prompts:
"Export the Order approval process map as Visio."
"Give me a
.vsdxof every map in the Finance space."
The agent chat inside BA Copilot also gains a matching tool, so agent runs can produce Visio exports on demand. The MCP / agent tool uses the same tier limits as the dashboard β it can't be used to bypass plan caps.
Plan and limits
Org collaborators inherit the owning org's tier β a collaborator in a Pro org has Pro-level Visio export limits even if their personal subscription is Essential.
Troubleshooting
The Visio menu items aren't visible. Visio export is an opt-in Labs feature. Open any Export β Visio entry-point once to see the acknowledgement dialog and turn it on, or enable it from Settings β Labs.
One specific map keeps getting skipped in bulk export. That map probably has a degenerate flow (e.g. a sequence flow into a boundary event source, or duplicate data associations). Open it, fix the warning, save, and re-export. The skipped-files alert at the top of the export page lists the affected filenames.
My .vsdx opens in Visio but some shapes look generic. The converter uses BA Copilot's BPMN stencil. Visio falls back to a generic shape for any BPMN element it doesn't recognise. The export still preserves the topology and labels.
I got a 403 trying to export. Visio export isn't available on the free trial β start a paid plan to use it. If you're on Essential and tried a bulk export, switch to single-map export or upgrade to Pro for batch.
My download was tiny / empty. Bulk exports skip maps that fail conversion rather than failing the whole batch. If every selected map was skipped, the zip will be small. Check the skipped-files alert.
Related
Importing Visio diagrams (.vsdx) β (draft pending; link once the Visio import article is published)
Use BA Copilot inside Claude with MCP β the live MCP article will be updated to add
export_process_map_to_visioto its tool list.