SCADA Blog › Historian CSV Export

How to Export SCADA Desktop Historian Data to CSV

July 12, 2026  ·  7 min read

SCADA Desktop's historian logs every configured tag to a local SQLite database automatically — but a database file isn't useful for a maintenance report or a compliance audit. This guide walks through exporting that logged data to a clean CSV file in under two minutes.

Before you start: Make sure the tags you want to export already have historian logging enabled (Devices → your device → Enable Historian Logging) and have been running long enough to accumulate the time range you need.

Step 1 — Open the Trend Viewer

Historian → Trend Viewer

From the main SCADA Desktop window, go to Historian → Trend Viewer. This screen lists every tag that has logged data, along with a live trend chart.

Step 2 — Select the Tags to Export

Check one or more tags

Check the box next to each tag you want in the export. You can export a single tag (e.g. "Tank Level") or combine several related tags (e.g. "Tank Level", "Inlet Flow", "Outlet Flow") into one file.

Tip: Group tags that share the same logging interval into one export. Mixing a tag logged every second with one logged every minute still works, but the CSV will have more rows for the faster tag between each slower reading.

Step 3 — Set the Time Range

Pick a preset or custom range

Use a preset — Last 24 Hours, Last 7 Days, Last 30 Days — or set a custom start and end date/time for a specific shift, incident window, or reporting period.

Step 4 — Export to CSV

Click Export CSV

Click the Export CSV button. SCADA Desktop queries the local SQLite database for the selected tags and time range, and writes a CSV file with a timestamp column and one value column per tag.

Large exports: If you're exporting weeks of data at a 1-second logging interval, the resulting file can be very large. Export in smaller date-range batches (e.g. week by week) to keep files manageable and within Excel's row limit.

Step 5 — Open the CSV

The exported file opens directly in Excel, Google Sheets, or any CSV-compatible tool. Column headers use your configured tag names, so there's no renaming needed before you build a report or chart.

Common Use Cases for Historian Export

  • Maintenance reports — export a week of vibration or temperature readings to show a trend to a maintenance manager.
  • Compliance records — export a specific shift or batch window to prove a process stayed within limits.
  • Incident investigation — export the hours before and after an alarm to reconstruct what happened.
  • Offline analysis — export raw data into Excel, Python, or a BI tool for deeper analysis than the built-in trend viewer supports.

Troubleshooting

Export button is greyed out

  • Confirm at least one tag is checked in the Trend Viewer before exporting.
  • Confirm the selected time range actually contains logged data — an empty range disables export.

CSV file is empty or missing rows

  • Check that historian logging was enabled for that tag during the selected time range — logging must be turned on per-tag, and data isn't backfilled for periods before it was enabled.
  • Verify the local SQLite database file hasn't been moved or deleted from its default data folder.

Download SCADA Desktop Free

15-day free trial. Local historian, CSV export, dashboards, and alarms — no internet required.

See SCADA Historian →

Related Articles