Juggle Dash guide

Excel to dashboard: turn a spreadsheet into one HTML file

An Excel-to-dashboard workflow turns a spreadsheet into a view that reads as an app: organize worksheet data into a clean table, export it as CSV, create a dashboard draft from its fields, and deliver the result as a browser-openable file. It is a useful route when a client or teammate needs to understand a snapshot without learning your workbook or opening a BI workspace. With Juggle Dash, you can import a CSV, refine a generated draft in a visual editor, and export a single HTML snapshot or a DSL JSON definition.

Why copy-pasting charts into slides breaks

A pasted chart is a picture, so its labels, filters, and values stop responding to the person who receives it. When the spreadsheet changes, you have to remember which slides need replacing and repeat the formatting work. Different chart sizes and styles also make a set of client reports harder to maintain. A dashboard file keeps related measures and views together, although a static export still represents one point in time rather than a live spreadsheet.

Prepare the worksheet before you export

Think of the source range as a database table rather than a formatted report. Give every column a clear, unique header such as order_date, region, and revenue; put units in the header or documentation instead of mixing values such as “$200” and “200 dollars” in the same numeric column. Each row should describe the same kind of record, such as one order, one month, or one campaign. If the workbook has a title, notes, or subtotals above or below the table, leave them outside the exported range.

Check for blank header cells, duplicate names, and columns that mix dates with free-form text. Decide how empty values should be represented and remove accidental total rows that would otherwise be counted as ordinary records. These small cleanup steps make it easier for the editor to interpret the fields consistently and make the charts easier to explain. Keep a copy of the workbook unchanged so you can trace the CSV back to its source if a number looks unexpected.

The five-step route

  1. Make one flat table in Excel. Put one record on each row and field names in the first row. Keep each column to one kind of value, avoid merged cells, and remove decorative title rows and subtotal rows from the data range. If the workbook has several sheets, choose the one table that answers the question you need to show.
  2. Save a copy as CSV. Use Excel’s Save As or Export command and choose CSV for the worksheet you prepared. Check the exported file once in a text editor or spreadsheet app: dates, decimal values, and non-English text should remain readable. CSV carries a single flat table, not workbook formulas, formatting, multiple tabs, or charts.
  3. Open the editor and import the CSV. Go to https://app.dash.ashesborn.cloud, choose the CSV import flow, and select your file. The editor reads the headers and rows so it can identify candidate measures, dates, and categories. Start with a manageable export if the workbook contains many records, and review whether the inferred fields match your intent.
  4. Generate a first draft. Use a short prompt describing the audience and question, such as “Show monthly revenue, the best-performing channel, and the top five customers,” or pick an included SaaS preset for a familiar starting layout. A prompt guides the proposal; it does not replace checking whether the selected columns and calculations make sense.
  5. Refine and export. Drag panels to change their order, rename titles for the audience, and adjust the available theme colors. Check units, date labels, and totals against Excel before delivery. Export the finished view as a single-file HTML snapshot, or export DSL JSON when you want to keep a structured dashboard definition for another editing session.

What stays editable after export

The HTML file opens directly in a browser without deploying a Juggle Dash server and can be opened locally. Its chart runtime loads ECharts from a CDN, however, so rendering charts still requires an internet connection. It captures the current layout and data snapshot; opening it does not turn it into the visual editor or make it refresh. Treat the HTML as a delivery artifact and keep the original spreadsheet or CSV if you will need newer figures.

DSL JSON is the portable structured definition rather than a screenshot of the dashboard. Keep it with the project when you want a readable record of the dashboard setup. The current editor exports DSL JSON but does not import an exported definition back into a new session, so it is not a round-trip editing file today. Continue editing the active draft in the editor and export an updated definition when needed; use HTML for someone who needs to view the snapshot.

Before sending either file, open the HTML yourself at its intended viewing size and confirm the most important cards and charts remain legible. Use titles that name the measure and period, and avoid unexplained abbreviations that only make sense inside your team. A small note about the source range or “data through” date can help a recipient understand what the snapshot represents. These finishing checks are especially useful when the file will be viewed without a walkthrough.

What this does not do

This workflow does not connect to your Excel workbook for live refreshes. If the workbook changes, the exported dashboard will not silently update; import the new CSV, review the draft, and export a new snapshot. It also does not provide multi-user collaboration in a shared dashboard workspace, or scheduled email delivery of reports. Those limits matter when you are choosing between a one-time client deliverable and an ongoing reporting system.

Generation is a starting point, not a data audit. Check totals, date ranges, missing values, and category names against the workbook before sharing the result. If your source uses formulas, the CSV contains their saved values rather than the formulas themselves. Similarly, a dashboard can make a measure easier to scan but cannot establish whether the business definition of that measure is correct.

When you should use a BI tool instead

Choose Metabase or Power BI when the reporting requirement is to connect directly to databases, warehouses, or maintained business systems. A connected BI setup can query a source again as data changes and can be part of a broader analytics process. That is a better fit than exporting CSV by hand when people depend on current numbers, recurring refreshes, and a consistent place to explore them.

Power BI may suit organizations already invested in Microsoft tools and an established reporting environment. Metabase can suit teams that want a shared BI product around their data sources, including organizations comfortable operating a self-hosted setup. In either case, check how the product fits your data permissions, refresh needs, and intended viewers; a static file does not replace those operational features.

A file-first workflow is more appropriate when the dataset is already available as a spreadsheet, the report is for a specific client handoff, and the recipient needs a clear view rather than a persistent analytics account. It can also be a practical way to produce a polished first draft before deciding whether a recurring report merits a connected BI implementation. For a live, frequently updated dashboard, invest in a suitable data connection and refresh process instead.

Make a dashboard from your spreadsheet

Prepare a clean CSV and open the editor to create and refine a draft. If you want to compare the available project and export options first, see Juggle Dash pricing.