Visio Flowchart from a Spreadsheet: Prepare and Check the Table
Prepare a spreadsheet table for a Visio flowchart: inspect step IDs, required columns, blank rows and connections before generating the diagram.
Visio generates flowcharts from Excel workbooks only, so a list of steps that lives anywhere else has to be saved as .xlsx and made into an Excel table before the Create Diagram from Data wizard will read it.
The short version
- The wizard asks you to select an Excel workbook and then a table inside it, so a Sheet or CSV has to become .xlsx first.
- Google Sheets is not one of the six sources the Data Selector Wizard documents for Link Data to Shapes.
- Make the exported data an Excel table, not a custom range: Microsoft ties keeping the diagram synchronized to using a table.
- The Organization Chart Wizard is the one place delimited text goes in directly: it reads tab- or comma-delimited .txt.
- After export the diagram is linked to the copy, and nothing keeps the copy in step with the original list.
Related spreadsheet tasks
Every door into Visio is an Excel door
Every route Visio offers to a generated flowchart asks for an Excel workbook. The first page of the Create Diagram from Data wizard asks you to "Select the Excel workbook" and then to "Select a table or a custom range in the workbook". The Data Selector Wizard behind Link Data to Shapes lists six sources (an Excel workbook, an Access database, a SharePoint list, SQL Server, another OLEDB or ODBC source, or a previously created connection), and a Google Sheet is not among them. So if your steps live in a Sheet, a CSV export, a shared tracker, Airtable or a Jira export, the practical answer is that you convert the list to .xlsx first and then follow the Excel route. That conversion is the whole job, and it repays doing deliberately.
The moment you land in Excel, Microsoft's own guidance applies: "Use an Excel table and not a custom range if you want to keep your diagram and data synchronized." The wizard will accept a range, nothing warns you, and the diagram comes out looking correct, but a range quietly opts you out of Refresh Diagram, which is the only reason to generate a diagram from data rather than draw it. Two further constraints come with the route. Microsoft documents the Data Visualizer templates and the Create Diagram from Data wizard as available with Visio Plan 2 only, list price US$15 per user per month paid yearly at the time of writing, and Plan 2 is the one subscription tier that includes the Windows desktop app. There is no Visio desktop app for macOS.
Then there is the part nobody mentions in the export instructions. Once you export, the diagram is linked to the copy, not to the list people actually keep editing. If the real backlog lives in a Sheet that four colleagues update, or in a tracker fed by a form, you now hold two versions of the process and one of them starts going stale the minute you save it. Refresh Diagram pulls from the workbook you selected, so a refresh keeps the diagram honest about the copy and says nothing at all about the original. Update Source Data writes the other way, into that same copy, and Microsoft is explicit that you should not use formulas in a Data Visualizer source, because Overwrite converts each formula to its result.
Deciding which of the two copies is the master is therefore the real decision on this route, and it is better made on purpose than discovered three months later. The example below builds a customer-feedback-to-improvement process in QueryChart, where the rows are the chart: one row per step, a column holding the row number each step leads to, and lane columns for the phase and the owner. Nothing is exported and nothing is linked, so there is no second copy to drift. Step through the four stages and watch which spreadsheet column each one fills in: it is the same column order you will need in an .xlsx before the Visio wizard does anything useful. None of this makes the Visio route wrong; it makes it a route with a hand-off in it, and the hand-off is where accuracy leaks.
The same rows, built up one column at a time
A customer-feedback-to-improvement process assembled from a flat list of steps, in the column order an Excel export needs before Visio will read it.
The exported list, labels only
"Send feedback through any channel", "Log the feedback in the tracker", "Categorise the item and set severity": three rows with shapes and no relationships, which is exactly what a tracker export gives you. Every step is present and the process is still invisible.
The column that makes it a process
Filling in the row number each step leads to draws the arrows, and the fork appears at "Does the customer need an individual reply?". This is the column no exported tracker contains, because a spreadsheet has never needed to say what happens next.
Naming the branches
"Is the cause inside our own process?" now carries "Inside our process" and "Outside our control" on its two exits, and the recurrence test below it separates "Yes" from "One-off, low impact". Unlabelled exits are the commonest reason a generated diagram cannot be read back.
Lanes, the loop and both endings
The lane columns place each step under Customer, Support, Process owner or Quality across the five phases, and "Did the change fix the problem?" routes back to "Agree the action, the owner and the check" when it did not. Two endings: closed with the change confirmed, and closed with no process change and the reason recorded.
How it works
Export the list from wherever it lives
Get the steps out of the Sheet, tracker, Airtable base or Jira view as tabular data, one row per step and one header row. CSV is a perfectly good intermediate format at this stage: it is only unacceptable as the thing you eventually hand to Visio. Strip merged cells, grouped headers and blank separator rows now, while you are still in the tool that produced them.
Open it in Excel and save it as .xlsx
The wizard's Excel page asks you to "Select the Excel workbook", so the file has to be a workbook. Open the CSV in Excel and save it in the .xlsx format. Put the data on one sheet with nothing above the header row, and check that the columns landed in separate cells rather than one comma-filled column, which is what a mismatched delimiter produces.
Convert the data to an Excel table
Do not leave it as a range. Microsoft's guidance is plain ("Use an Excel table and not a custom range if you want to keep your diagram and data synchronized"), and the wizard's second prompt, "Select a table or a custom range in the workbook", is where the choice is made. A range works once and then never refreshes, with no error to tell you why.
Add the columns the wizard maps
The wizard needs a unique, never-blank Process Step ID, a description, the Next Step ID of the following step, connector labels for branching shapes, and a shape type; the function and phase columns matter only for a cross-functional flowchart. Rewriting your existing IDs into that shape is the fiddly part, and /guides/how-to-turn-excel-data-into-visio-flowchart covers the schema cell by cell.
Start the Data Visualizer template in Visio desktop
Open Visio, or select File > New if you are already editing, then select TEMPLATES and Select Flowchart, and choose "Basic Flowchart - Data Visualizer" or "Cross-Functional Flowchart - Data Visualizer". Choose a unit of measurement, select Create, and the Create Diagram from Data wizard opens; point its Excel page at your workbook and at your table. The five wizard pages are walked through in /guides/how-to-create-a-flowchart-from-excel-in-visio.
Decide which copy is the master, then keep them in step
Click in the diagram container to enable the Data Tools Design tab. Refresh Diagram re-reads the workbook; Update Source Data writes the diagram's changes back into it, and the workbook must be saved and closed if it sits on a desktop machine or a network file server. Neither command touches the Sheet or tracker you exported from, so pick one home for the process and tell people which it is.
Mistakes to avoid
Handing the wizard a CSV
The Excel page asks for a workbook and then for a table or custom range inside it; a .csv is neither, and no amount of renaming the extension changes that. Save as .xlsx first. The exception people remember and then over-generalise is the Organization Chart Wizard, which genuinely does read tab- and comma-delimited .txt files, but it builds org charts, not process flows.
Selecting a custom range instead of a table
The wizard accepts a range, generates a diagram that looks right, and leaves you with no working sync. Microsoft's own instruction is to use an Excel table if you want the diagram and the data to stay synchronised. Fix it by converting the data to a table and re-running the wizard; there is no dialog that will tell you this is why Refresh Diagram achieved nothing.
Letting the exported copy drift from the original
Refresh Diagram reads the workbook you selected, and nothing keeps that workbook in step with the Sheet or tracker it came from. Two weeks later the diagram is a faithful rendering of a stale export. Either promote the .xlsx to the master and stop editing the original, or re-export over it as a deliberate step before every refresh.
Losing the export's formulas
Exports often arrive with formulas, and building a Next Step ID column usually tempts you into a lookup. Microsoft's warning is unambiguous: do not use formulas in the Excel data source, because after you select Overwrite in the Update Source Data dialog box Visio converts the formula to the formula result. The first write-back flattens the column that was doing your bookkeeping.
Build this process from rows instead
Open the customer-feedback example as your own chart and paste your exported rows over it: no workbook, no wizard and no second copy to keep in step.
Related guides
Frequently asked questions
Can Visio import a Google Sheet directly?
Not by any documented route. The Data Selector Wizard behind Link Data to Shapes offers six sources (an Excel workbook, an Access database, a SharePoint list, a SQL Server database, another OLEDB or ODBC source, and a previously created connection), and Google Sheets is not one of them. The Create Diagram from Data wizard is narrower still: it asks for an Excel workbook and then for a table or a custom range within it. The practical path is to download the Sheet as an .xlsx, convert the data to an Excel table, and treat that workbook as the file Visio is linked to from then on.
Can I create a Visio flowchart from a CSV file?
Not with the Data Visualizer route. Its wizard asks you to select an Excel workbook and then a table or custom range inside it, and a CSV contains neither, so the conversion to .xlsx is unavoidable. Delimited text does go into Visio in one place: the Organization Chart Wizard reads tab-delimited and comma-delimited .txt files alongside Excel workbooks, Org Plus text, Exchange Server directories and ODBC sources. That is an org chart rather than a process flow, and /guides/how-to-create-org-chart-from-excel-in-visio covers it. For a flowchart, open the CSV in Excel and save it properly first.
Which file formats can Visio actually read a process out of?
Narrower than the export menu of whatever tool you are leaving. For a generated flowchart, one: an Excel workbook, with the steps inside a table or a named range. For linking data to shapes you have drawn, the Data Selector Wizard documents six sources: an Excel workbook, an Access database, a SharePoint list, a SQL Server database, another OLEDB or ODBC source, and a previously created connection. The Organization Chart Wizard is the broadest reader of the three, taking .xls, .xlsx, .xlsm and .xlsb alongside tab-delimited, comma-delimited and Org Plus text files, an Exchange Server directory and ODBC sources. Nothing in that list is a Google Sheet, a CSV, or an export from a tracker, so .xlsx is the format to convert to.
How do I keep a diagram in step with a spreadsheet other people are editing?
On the Visio route you cannot, not directly: the diagram is bound to the workbook you selected, so somebody has to re-export and re-refresh, and that person is the single point of failure. Two options remove the hand-off. Make the .xlsx itself the working document, so there is only one copy, and accept that the original tracker is now a dead artefact. Or keep the process in a tool where the rows are the diagram: in QueryChart everyone edits the same rows at the same URL and the chart re-renders, so there is no export step to forget and no copy to compare against.
