How to export diagrams from Visio without losing the files you need
Your Visio diagrams are the export. draw.io imports the main Visio formats, including .vsdx files, and converts older .vsd and .vst files in the browser, but the gaps are specific: embedded EMF images do not import, interactive behavior may be lost, and Visio 2003 to 2010 XML and .vdx files are not supported directly, so they need to be resaved in a newer Visio first. Those three gaps decide how much testing you need. If your renewal, license change or data residency requirement forces the move, start by sorting your diagram estate into these categories rather than assuming every file will open cleanly. The collection work is mostly something your own team can do. Pull the files from OneDrive, SharePoint and desktops, and keep stencil files (.vssx and .vss) in a separate folder, because draw.io imports them as shape libraries rather than as diagrams. Record which file versions are current, since old copies often sit next to the working one. DeployOpen plans and runs the export as a fixed-scope piece of work when you want an outside team to own the sorting, conversion and checks, and the scope, deliverables and timeline are agreed in writing before work starts. Checking results is where the effort goes. Open a sample from each category in draw.io, compare it with the original in Visio, and look at text wrapping, connector routing, layer visibility and any hyperlinks or action buttons. Any diagram that depends on embedded EMF images or interactive behavior should be rebuilt or flagged for manual review. Confirm with your Visio license administrator which versions are still installed, because the Visio LTSC 2024 mainstream support date in Microsoft's lifecycle page affects how long you can keep the originals open without a deadline.
Which Visio files can move to draw.io and how
This table lists each Visio file type you are likely to hold, where it usually sits, how to get it out, and what draw.io does with it on import. Read the rows as a checklist: anything marked for conversion or library import needs a test file first, and anything that depends on embedded EMF images or older XML needs a separate plan. The main takeaway is that draw.io handles current diagrams and stencils well, but it does not replace every Visio feature.
| File type or location | Export method | Output in draw.io | Import limits to check |
|---|---|---|---|
| Visio .vsdx diagrams | Download the file from its storage location, then open or import it in draw.io | Editable diagram, imported directly | Looks may differ from the original, interactive behavior may be lost, and embedded EMF images are not imported |
| Visio .vsd diagrams | Download the file from its storage location, then import it in draw.io | Editable diagram, converted in the browser | Same visual and interactivity limits as .vsdx, plus embedded EMF images are not imported |
| Visio .vst templates | Download the file from its storage location, then import it in draw.io | Converted in the browser, usable as a diagram starting point | Confirm that template content renders as expected before relying on it |
| Visio .vssx and .vss stencils | Download the stencil file from the storage location, then import it in draw.io | Imported as a shape library | Shapes are added as a custom library, so check each shape's appearance and connection points |
| Visio 2003 to 2010 XML (.vdx) | Open the file in Visio 2013 or later and save it as .vsdx before exporting | Imported only after resaving as .vsdx | draw.io does not import this older XML format directly |
| OneDrive folders | Sign in, select the files, and download them to a local folder before importing | Same as the file type above | Confirm that all versions and sharing settings are retained in your own copy |
| SharePoint document libraries | Select the files in the library and download them, or export through the sync client | Same as the file type above | Check that check-out and version history are handled as expected before deleting originals |
| Desktop and network folders | Copy the files to a working folder, then import them in draw.io Desktop or the self-hosted editor | Same as the file type above | Open each file and compare it against the original in Visio before retiring the source |
What does not carry over from Visio and how to handle it
Visio diagrams rarely move into draw.io without some change. The cards below cover the gaps draw.io documents, the visual and interactive losses that need a manual check, and the older file formats that need a resave or a different route before you start a bulk export.
Embedded EMF images
draw.io does not import embedded EMF images from Visio files. Any screenshot, logo or picture pasted into a Visio shape can disappear or arrive as a blank placeholder. Before you convert, list diagrams that contain pictures, export those pictures from Visio as PNG or SVG, and re-insert them in draw.io. Check each diagram page for missing graphics, since the rest of the shape may still import correctly.
Interactive behavior and hyperlinks
Visio features such as hyperlinks, hover actions and shape-to-shape behavior may not survive the import. draw.io's documentation warns that interactive behavior can be lost. Make an inventory of diagrams that rely on links or navigation, such as process maps used in a published portal. Rebuild those links in draw.io by adding hyperlinks to shapes or by using a page index, then test each link in the target viewer.
Layout and rendering shifts
Imported diagrams may look different from the original. Fonts, line routing, connector endpoints, text wrapping and shape sizes can shift, which can break a layout that was tuned for a Visio page. Compare each converted diagram side by side with the source file, and focus on dense swim lanes, labels near connectors and any page that a reader must print or share with an auditor. Adjust the layout manually where drift matters.
Visio 2003 to 2010 XML and .vdx files
draw.io's documented import list covers .vsdx, .vsd and .vst files, but not Visio 2003 to 2010 XML. Older .vdx files may fail or import incompletely. Open each .vdx file in Visio 2013 or later and save it again as .vsdx before importing. Then confirm the current .vdx handling in the draw.io import documentation and run a test import on a copy of one representative file.
Stencils and custom shape libraries
Visio stencils import as shape libraries, but custom masters, theme colors and shape data fields may not map one to one. Teams that depend on company stencils for network, process or engineering diagrams should keep a list of the stencils in use. Import each stencil file, then check that shape names, sizes and connection points match what drafters expect before you retire the Visio originals.
Where Visio files sit: OneDrive, SharePoint and desktops
OneDrive is personal storage, so Visio files saved there are usually known only to their owner. Files shared by link or with specific colleagues may also be reachable by people outside the original team. Start by identifying which users hold Visio files, then copy them out with each owner's cooperation or through administrator access.
- Find files by type: search the OneDrive web interface for
.vsdx,.vsd,.vst,.vssxand.vssextensions, or ask an administrator to run a content search across accounts. - Download in bulk: select a folder and download it, which typically produces a single archive that you then unpack into a controlled location.
- Review sharing links: note files shared by link, since those links can outlive the owner's role or employment.
- Ask the administrator for: a list of users with Visio files, the sharing settings applied to them, and whether any retention hold applies to departed users' accounts.
draw.io's integrations list includes OneDrive, so a diagram can be opened from there in draw.io. The export itself is a copy of files your organization already controls, so confirm that each owner has placed a copy in your own storage.
SharePoint libraries are usually owned by a team or site rather than an individual, so Visio files tend to accumulate in shared document libraries that outlive the people who created them. Access is typically granted through Microsoft 365 groups or site permission levels, and external guests may have been added to some sites. Identify the sites first, then the libraries within them.
- Locate the sites: use the SharePoint admin center to list sites, or search the tenant for Visio extensions across all sites.
- Filter within libraries: sort or filter each library by file type to isolate
.vsdx,.vsdand stencil files, including subfolders. - Download selected files or folders: download from the library view, and keep the original folder structure so that diagrams can be matched to their owning teams.
- Check version history: older
.vsdcopies may exist as versions of a file, so ask whether those versions must be retained for your records. - Ask the administrator for: a list of sites with Visio files, the site owners for each, the groups and guests with access, and the external sharing settings in place.
Before you start, confirm which site owners are still active, because they will need to approve the copy of their team's diagrams.
Desktops and laptops often hold drafts, personal copies and downloads that were never uploaded to a managed location. These files are the hardest to inventory because no central service knows they exist. Visio may also keep a list of recently opened files, which helps locate some of them but will not find everything.
- Search by extension: use the operating system search on each device for
.vsdx,.vsd,.vstand.vssx, and include Downloads and Desktop folders. - Check synced folders: if a OneDrive or SharePoint library is synced to the device, files may appear locally even when the cloud copy is the authoritative one.
- Check removable media: USB drives and external disks used for transfers can contain the only copy of an older diagram.
- Ask IT for: a device inventory for users who created Visio files, confirmation of which laptops are managed and backed up, and the collection method your policy allows.
Collect files through a managed process rather than by asking each person to email their diagrams, and record which device each file came from. Confirm that no copies remain on personal devices once the export is complete.
Network file shares are often the oldest storage location for diagrams, especially in engineering, operations and architecture teams. Access is usually controlled by directory groups and folder permissions, and ownership may sit with IT or with a department rather than an individual. Because folders can be deep and poorly named, a structured inventory helps.
- Map the share structure: list top-level shares and their subfolders, then search each one for Visio extensions.
- Read the permissions: record which groups can read or change each folder, since this shows who will need to approve the copy.
- Copy with a tool that preserves structure: use a file copy tool that keeps timestamps and folder paths, and log the results for later checks.
- Verify backups: confirm whether snapshots or backups exist for these shares, which matters if a file is damaged during copying.
- Ask the administrator for: a share inventory, a permissions report by folder, and any archival or retention rules that apply to the share.
Keep a copy of the export log with the collected files so that you can show which folders were covered and who approved the copy.
Export sequence for Visio diagrams and stencils, step by step
This sequence gives you a complete, checked inventory of your Visio files and a set of draw.io copies that open correctly, while the originals stay untouched in their current locations. Each step closes with a check you can record for audit or migration sign-off.
Inventory every Visio file and its owner
Search OneDrive, SharePoint sites, file shares and laptops for .vsdx, .vsd, .vst and .vssx or .vss stencil files. Record each file's path, owner, last modified date and whether it is still in use in a process, template or customer document. Ask each team lead to confirm which folders hold diagrams that are not indexed by search. The step is done when the inventory sheet has one row per file and every owner has confirmed their list in writing.
Copy files into one archive, leaving originals in place
Copy the inventoried files into a single working archive folder on a controlled share, keeping the original folder structure so references stay traceable. Do not move or edit the originals, because they remain the record until the migration is signed off. Compare the file count and total size of the archive against the inventory. The step is closed when the counts match and a hash list of the copies has been saved next to the archive.
Sort files by type and import route
Split the archive into groups: .vsdx files that draw.io imports directly, .vsd and .vst files that draw.io converts in the browser, .vssx and .vss stencils that become shape libraries, and older .vdx XML files. Flag anything that is not in these groups, such as Visio 2003 to 2010 XML or files from other tools, for separate handling. The step is done when every file sits in exactly one group and the flagged list has an owner.
Resave older files and set up the draw.io environment
Open .vdx files in a Visio version that supports the format and resave them as .vsdx before import, since draw.io does not import the older XML. Then choose the import environment: draw.io Desktop on an approved device, or the self-hosted draw.io Docker image on your own server, which has no export server. In either case, confirm where the import session will save results. The step is closed when every .vdx file has a .vsdx copy and the chosen environment starts and opens a blank diagram.
Import each group into draw.io
Import the .vsdx and .vsd files and the stencils as custom shape libraries, then import the grouped files in small batches so a failure is easy to trace. Note any file that fails to open, any stencil that does not load and any embedded EMF images that do not come through, because draw.io does not import embedded EMF images. The step is closed when the import log lists every file as imported, failed or flagged, with a reason for each exception.
Check each diagram against the original
Open each imported diagram next to its original in Visio and compare page count, text, connector routing, shape placement and any interactive behavior such as hyperlinks or data-linked shapes. Expect differences in appearance and loss of interactivity, as draw.io documents for Visio imports, and record them rather than silently accepting them. Use a second reviewer for diagrams that carry compliance or architecture content. The step is closed when each diagram has a pass, a pass with noted differences, or a fail that goes back to the import step.
Save results to the storage you choose
Save each approved diagram to the storage the organization selects, such as a local drive, an approved device or a connected service like Nextcloud, OneDrive or SharePoint. draw.io saves diagrams where the user chooses, on the device or in a connected storage service, and does not keep them on its servers. Confirm the saved file opens from the destination and that the file list matches the approved inventory. The step is closed when the destination listing reconciles with the approved list and the Visio originals are kept until the owner signs off.
Checking exported diagrams before the Visio license ends
Verification is the step that proves an export worked, and it should be finished before anyone removes a Visio license or deletes a source file. For each diagram, open the imported file in draw.io and the original .vsdx in Visio side by side, then compare the same things in the same order: every text label, the number of pages, the connectors and whether they still attach to the right shapes, and the layers, which draw.io keeps as its own layer set. Check that every stencil the original used is available as a shape library, since .vssx and .vss files import as libraries and a missing one will show up as placeholder or broken shapes. Note any embedded EMF image, because draw.io does not import these, and list each one for manual replacement with a PNG or SVG export from the original.
Record the results in a simple register with one row per file: source location, draw.io file name, the checks passed or failed, and the name of the person who reviewed it. Be specific about what counts as an acceptable import. Some differences, such as shifted spacing or lost interactive behavior, are documented by draw.io and may be tolerable for a process map but not for a controlled network diagram. Agree on these acceptance criteria in the written scope before the work starts, and confirm which diagrams are regulated or customer-facing, since those usually need a stricter review.
Keep every original .vsdx, .vsd and stencil file untouched until a named reviewer signs off on the converted set. Store the originals in a read-only location with their existing folder structure, and do not resave them in a newer Visio version during review, because that changes the file you are comparing against. Plan for a retention period for the originals that matches your records policy, and confirm with your legal or records team how long they must be kept. Retaining originals also protects you if a diagram needs to be re-imported later with a newer draw.io release.
What to plan before your Visio license or subscription ends
Visio exports are easiest to plan while the license still works. The cards below cover the deadlines, the files to copy, the terms that govern stencils, and the ownership decisions that keep the archive usable after the switch.
Know your lifecycle deadline
Check which Visio edition your organization actually runs before setting a date. Visio LTSC 2024 is listed for mainstream support until October 2029 under Microsoft's Fixed Lifecycle Policy, while Visio 2019 reached its extended end date in October 2025. If you still run Visio 2019 or older, treat the export as overdue and confirm the support status of each installed version on Microsoft's lifecycle pages before scheduling the work.
Copy every file before access ends
Collect a full copy of every diagram while your license and storage access still work. Include files in OneDrive, SharePoint document libraries, shared folders and personal desktops, since diagrams often sit in places nobody on the current team set up. Keep the original folder structure and record where each file came from, because that record is the only way to trace a diagram back to its source after a move.
Check stencil terms before reuse
Visio stencils are often company property, but some may come from third-party vendors or from template packs with their own license terms. draw.io's source code is Apache License 2.0, while its icon sets, stencil libraries and templates have separate terms. Before you import a .vssx or .vss stencil as a shape library, confirm who owns the shapes and whether your license allows reuse in a new tool.
Assign an owner for archived files
Name one accountable person or team for the exported archive before the first file moves. That owner decides which diagrams are migrated, which are archived as read-only, and which are retired. Without a named owner, converted diagrams tend to end up in a shared folder that no one reviews, and reviewers later cannot tell whether a diagram is current or stale.
Set a retention rule for originals
Decide how long the original .vsdx, .vsd and .vdx files stay in storage after the converted copies are checked. Your records policy, audit scope and any regulatory retention rules set that period, so confirm them with your compliance or legal team rather than choosing a number yourself. Keep originals unchanged, since a later question about a diagram often requires the source file, not the converted version.
Decide who keeps draw.io access
Settle who administers the draw.io deployment after the switch, including the Docker image, the storage integrations such as OneDrive, SharePoint or Nextcloud, and any export server you choose to run. The deployment needs an owner for upgrades and backups, and access to the storage holding your diagrams should follow your existing identity controls. Write this decision down before the Visio license lapses so no one is left without access to the files.
Questions buyers ask before exporting Visio diagrams
What does exporting Visio diagrams cost?
The export itself has no license cost for draw.io, so the spend is labor, hosting and review time. Most of the effort comes from the number of files, how many contain embedded EMF images that draw.io does not import, how many stencils need to become shape libraries, and how long reviewers take to check each diagram. Your internal staff are paid for file collection and sign-off, and an outside provider is paid only if you buy scoped work. Ask any quote to itemize file count, image rework, stencil conversion, review rounds and hosting. DeployOpen does not publish prices. It gives a quote from a written scope that sets deliverables and timelines before work starts.
How long does a Visio export take?
The pace depends on the drivers rather than a fixed duration. The main ones are how many .vsdx, .vsd and stencil files you hold, how many diagrams carry embedded EMF images or interactive behavior that will need manual rebuilding, how many stencils must be converted, and how quickly owners can review results. A small, well-organized library moves much faster than a large folder tree spread across personal OneDrive accounts. Start with an inventory of file counts by type and by owner, since that single list tells you most of what the schedule depends on.
What does the organization need to provide for the export?
Three things matter: access to the source files, a named owner who signs off on each diagram, and a place to run draw.io. Source files sit in OneDrive, SharePoint and desktops, so someone needs read access to those locations and permission to copy them out. For the tool, you need a server for the official jgraph/drawio Docker image or desktop installs for draw.io Desktop. The Docker image has no export server, so PDF export uses the browser print dialog unless you configure one. Confirm these points with your IT team before scheduling work.
Can our team export Visio diagrams without outside help?
Yes, a team can do the core work internally if it has the time and the skills to check results. draw.io imports .vsdx files directly, converts .vsd and .vst files in the browser, and imports .vssx and .vss stencils as shape libraries. Teams usually struggle with the exceptions: .vdx files may need resaving in a newer Visio version first, and imports may look different, lose interactive behavior or drop embedded EMF images. Outside help is most useful for a large or regulated library, where a fixed-scope engagement can set the review process and evidence before work starts. Confirm the exception list in your own environment with a test batch.
Does draw.io store our diagrams on its servers?
No, according to draw.io's trust page, diagrams are saved where the user chooses, either on the device or in a connected storage service, and never on draw.io's servers. The same page says that hosted export and real-time collaboration process diagrams temporarily on servers run by Cloudflare. If that temporary processing matters for your policy, you can avoid it by running the self-hosted draw.io Docker image or draw.io Desktop, which keeps the editing workflow inside your network. Have your security and privacy teams read the trust page wording and decide which features you allow.
Which Visio content will not come across cleanly?
Expect manual rework for embedded EMF images, interactive shapes and any .vdx files that were not resaved. draw.io warns that Visio imports may look different from the original, may lose interactive behavior and do not import embedded EMF images. It also does not import Visio 2003 to 2010 XML or LibreOffice Draw files, so those need a conversion step first. Test a representative sample of each diagram type before committing to a full run, and record which diagrams need manual rebuilding so the review plan reflects that work.
How do we check that exported diagrams are correct?
Compare each imported diagram against its source, page by page, using a review checklist. Check shape placement, connector routing, text, layers, stencil shapes and any hyperlinks, and confirm the named owner signs off. Keep a log that lists each source file, its output file, the reviewer and any open issues. That log becomes your evidence if an auditor or internal reviewer asks how diagrams were moved. Keep original Visio files until sign-off is complete and your retention policy allows deletion.
How DeployOpen works on this
DeployOpen plans and delivers the export of Visio diagrams and stencils from your OneDrive, SharePoint and desktop storage into a self-hosted draw.io environment inside your own infrastructure. Every engagement starts with a written scope that names the file inventory, the target environment and the verification method before any file is moved.
How we scope
- Inventory the .vsdx, .vsd, .vdx and stencil files across OneDrive, SharePoint and named desktops.
- Classify files by format, since .vsdx and .vsd import directly while .vdx files need resaving first.
- Agree in writing which diagrams contain embedded EMF images that will need rebuilding or review.
How we build
- Deploy the official jgraph/drawio Docker image or draw.io Desktop on your own servers or devices.
- Convert and import diagrams and stencils, then test rendering, shape alignment and interactive links.
- Configure your chosen storage integration so saved diagrams stay in your own repositories.
How we hand over
- Document the import results per file, listing diagrams that need manual rework after conversion.
- Provide a checklist of checks completed, such as rendering comparisons against the original Visio files.
- Deliver runbooks for updating the draw.io image and for keeping a copy of the source Visio files.
How we support
- Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts.
- Ongoing support, upgrades and continuous testing are available as a retainer after handover.
- Ask for a quote built from the written scope, covering file volume, storage locations and rework effort.
