Microsoft Visio vs draw.io

A Visio Plan 1 or Plan 2 subscription, or a one-time Visio LTSC 2024 licence, covers the right to install and use the desktop application for each licensed user under the terms Microsoft publishes for that product. It does not cover the storage where your diagrams sit, the time spent migrating them, or any internal support. Check which edition includes the features your teams use, such as stencil management and desktop-only tools, and confirm with your Microsoft reseller how renewals, true-ups and admin tooling are priced. The LTSC 2024 licence follows Microsoft's Fixed Lifecycle Policy, with mainstream support listed until October 2029, so compare that date with your planning horizon. The Visio LTSC 2024 lifecycle page shows the current dates.

The draw.io source code is licensed under the Apache License 2.0, so there is no licence fee for the application itself. Your organization pays for the infrastructure that runs the self-hosted Docker image or desktop installs, for the staff who operate it, and for any integrations or export services you add. The Docker image is based on Tomcat and runs on a server you control, so hosting costs depend on your existing virtualization or container platform. Ask your internal platform team to estimate the hours for patching, backups and access control, since those recur every month and are the largest ongoing item.

Visio support is largely handled by Microsoft's licensing and product support channels, with IT handling deployment and user access. Self-hosting draw.io moves some of that work in-house, including running the container, applying updates, managing the storage connections and answering user questions about the tool. Draw.io itself is developed by its core team, and the project does not accept pull requests, so you cannot fix product defects by contributing code upstream. Plan for an owner who can track new releases, test them against your templates, and deploy changes on a schedule you set. Your staff time for this is recurring, not one-time.

A useful quote lists each cost component separately so you can compare it with your current spend. Ask for these items in writing:

• Scope: number of diagrams, stencils and libraries, and which file types are in scope.
• Hosting: the environment, the sizing assumptions and who operates it after handover.
• Conversion: how each .vsdx, .vsd, .vssx and .vss file will be checked for rendering and interactivity.
• Training and documentation for named user groups.
• Recurring items such as updates, backups and support, with their renewal terms.
• Exclusions, including any export server work and any manual rebuilding of diagrams.

DeployOpen plans and implements fixed-scope engagements, and scope, deliverables and timelines are agreed in writing before work starts. DeployOpen does not publish a price list, so a quote follows from that written scope.

Conversion effort grows with the number of files, the variety of their formats, and how much each diagram depends on Visio-specific behavior. draw.io imports .vsdx files directly, converts .vsd and .vst files in the browser, and imports .vssx and .vss stencils as shape libraries. It does not import Visio 2003 to 2010 XML or embedded EMF images, and Visio imports may lose interactive behavior. Each stencil set you carry over needs to be checked and organized as a custom library, so a large stencil count adds review time even when individual files convert cleanly. Start with an inventory of file types, the number of stencil sets, and the diagrams that are used in production, then sample them to estimate the rework.

One-time costs include the initial deployment, the file inventory and export, conversion and checking of diagrams and stencils, and the first round of training. Recurring costs include Visio subscription fees or licence renewals until they stop, hosting capacity, staff time for updates and backups, and any support or maintenance retainer you choose. Ongoing support, upgrades and continuous testing are available from DeployOpen as retainers, which turns part of the recurring work into a defined service. Ask every vendor to separate one-time and recurring amounts so you can model the first three years of spend.

Yes, many teams can move a small diagram library in-house, since draw.io is free to deploy and its import tools are documented. The work that usually takes longer than expected is checking converted diagrams, rebuilding shapes that did not import cleanly, and documenting the new hosting for auditors. If you have an engineer who can run the container, a designer who can review converted diagrams, and a clear owner for the result, an in-house move may cost less in external fees. Compare that staff time with a fixed-scope quote, and confirm that the internal team has capacity during the period when your Visio licences are still active.

Effort depends mostly on the volume and type of files, not on the draw.io license, which is none. draw.io imports .vsdx files directly, converts .vsd and .vst files in the browser, and imports .vssx and .vss stencils as shape libraries. The work grows with four factors: how many diagrams and stencils you hold, how much of the content uses custom shapes or interactive behavior, how many diagrams embed EMF images, and how strictly the output must match the original. draw.io warns that Visio imports may look different, may lose interactive behavior and do not import embedded EMF images, so a sample review of each diagram family sets the real scope. Ask any partner for a written inventory and a conversion plan before agreeing on a fixed scope.

Yes, many teams do, because draw.io is a browser-based editor that people already use for diagrams. Running it yourself means operating a Docker container from the official jgraph/drawio image, which is based on Tomcat and kept up to date with the production app, or distributing draw.io Desktop to users. Your team would need to handle updates, access control, backups of the storage location and user guidance on where files are saved. Someone must also own the process for checking converted diagrams. The answer is yes for a team with container and endpoint skills, and a partner can cover the parts you prefer not to own, such as hardening, upgrades and documentation, under a retainer.

IT staff provide access and decisions rather than heavy labor. They need to confirm where existing Visio files live, such as OneDrive, SharePoint, network shares or local desktops, and grant read access for collection. They must choose where draw.io diagrams will be stored, since draw.io saves files where the user chooses on the device or a connected storage service, and it lists integrations with Nextcloud, ONLYOFFICE, GitLab, Google Drive, OneDrive and SharePoint. They also need to approve the hosting target, the container platform, the single sign-on approach if any, and the desktop deployment method. Confirm each item with your own change process, because your network and policy rules decide the details.

The pilot length depends on the number of diagram families you want to test, the number of users who will work in the tool, and the number of approval steps in your organization. A pilot usually covers a representative set of files, such as a few process flows, one network diagram with stencils and one diagram with embedded images, and checks rendering, shape behavior and storage. Each additional stencil library or integration adds review time. No duration is fixed by the product. Ask for the pilot's exit criteria and a written timeline in the scope before work starts, and confirm any date with your own change calendar.

Yes, draw.io can run without internet access through two routes: the self-hosted Docker image or draw.io Desktop. The jgraph/drawio Docker image does not include an export server, and PDF export uses the browser's print dialog unless an export server is configured, so no diagram data leaves the server for an export. Desktop installs run on the device itself. Before relying on offline use, confirm that the chosen build, fonts, icon libraries and any integrations you need work without outbound access, and test the import path for Visio files inside the closed network. Icon sets, stencil libraries and templates carry separate terms from the Apache-licensed source, so check those too.

Whether you need PDF export depends on whether diagrams leave the editor for reports, audits or contracts. draw.io's Docker image has no export server by default, so PDF export uses the browser's print dialog. An export server can be configured if you need a server-side export for embedded diagrams, and that adds a component to install, patch and monitor. Confirm two things with your own users: how often they export, and whether the printed output needs to match Visio's layout exactly. Test the output of your most complex diagrams before deciding, because the export path changes the operating model.

No. draw.io's privacy policy says diagrams are saved where the user chooses, on the device or in a connected storage service, and never on draw.io's servers. The policy also states that features such as hosted export and real-time collaboration process diagrams temporarily on servers run by Cloudflare. If you use the self-hosted Docker image and disable or avoid hosted features, that third-party processing does not apply to your deployment in the same way. Review the trust page with your privacy and security teams, then document which features you enable so your data flow records are accurate.

The supported life of your Visio licenses sets the deadline for a move, so check the version you run. Visio LTSC 2024, the current one-time-purchase edition, follows Microsoft's Fixed Lifecycle Policy with mainstream support listed until October 2029. Visio 2019 reached its extended end date in October 2025. Confirm the dates on Microsoft's lifecycle pages for your exact product, and check whether your agreement includes other terms. Use those dates to plan the file collection and pilot, not to guess a cutover date.