How to Export Niagara 4 History Data to CSV

Why Export Niagara History Data

Niagara 4 collects trend data from every point configured with a history extension—zone temperatures, damper positions, equipment runtimes, energy consumption, and more. That data lives inside the station's history database in a format that only Niagara can read natively. The problem arises when you need that data outside of Niagara: loading it into Excel for an energy audit, feeding it to a custom reporting tool, sending monthly CSV files to a building owner, or archiving historical records before a station migration.

Niagara does not include a one-click "export all histories to CSV" button. The platform was designed around real-time data visualization, not bulk data extraction. Depending on your situation—one-time pull versus scheduled export, local Workbench access versus remote-only access, single JACE versus a fleet of controllers—the right approach varies. This guide covers every practical method, from the built-in Workbench export to third-party automation modules and direct BQL queries.

Method 1: Manual Export via Niagara Workbench

This is the most straightforward approach and requires no additional modules. It works on any Niagara 4 station (JACE 8000, Niagara Supervisor, SoftJACE, or any third-party hardware running Niagara).

Step 1: Connect to the Station

Open Niagara Workbench and connect to the target station using your platform credentials. You need at least operator-level access to view histories, though admin access is recommended if you need to modify history configurations.

Step 2: Navigate to the History Space

In the Nav tree on the left, expand Station > History. You will see a list of all configured history sources organized by their station path. Each history entry corresponds to a point extension that has been logging data—for example, /AHU_1/DischargeAirTemp/NumericWritable.

Step 3: Open the History Table

Double-click a history entry to open it. Workbench displays the data in a tabular view with columns for Timestamp, Value, and Status. By default, the view shows all records stored for that history. If you need a specific date range, use the Time Range selector at the top of the history table to narrow the results.

Step 4: Export to CSV

With the history table open and your desired time range selected:

1. Go to File > Export in the Workbench menu bar (or right-click the history table and select Export).
2. Choose CSV as the export format.
3. Select a save location on your local machine.
4. Click Save. Workbench writes the history records to a .csv file with timestamp, value, and status columns.

# Example output: DischargeAirTemp_history.csv
# -----------------------------------------------
# Timestamp,Value,Status
# 2024-01-15T08:00:00.000-05:00,55.2,ok
# 2024-01-15T08:05:00.000-05:00,55.4,ok
# 2024-01-15T08:10:00.000-05:00,55.1,ok
# 2024-01-15T08:15:00.000-05:00,55.3,ok
# 2024-01-15T08:20:00.000-05:00,54.9,ok

Step 5: Repeat for Additional Histories

Workbench does not support multi-select export natively. You must repeat Steps 3–4 for each history you want to export. On a JACE with 200+ histories, this gets tedious fast—which is exactly why the third-party modules in Method 3 exist.

Method 2: Web-Based Export via the History Chart Servlet

If you don't have Workbench installed or need to pull data from a browser, Niagara's built-in web UI provides limited history export capability. This method works from any machine that can reach the station's web interface.

Step 1: Access the Station Web UI

Open a browser and navigate to the station's IP address or hostname (e.g., https://192.168.1.100/). Log in with your station credentials.

Step 2: Navigate to a History View

Use the station's navigation to find a history chart or history table view. The exact path depends on how the station's PX pages are configured. Common locations include a dedicated "Trends" or "Histories" page, or history widgets embedded in equipment summary pages.

Step 3: Use the Chart Export Feature

Niagara 4's HistoryChart widget includes a small toolbar. If the station developer enabled the export icon, you can click it to download the currently displayed data as a CSV file. The exported data matches whatever time range the chart is currently showing.

Limitation: Not all station builds expose the export button in the web UI. If the PX pages were built without the export widget, you won't see the option. In that case, you either need Workbench access (Method 1) or a third-party module (Method 3).

Step 4: Direct URL Query (Advanced)

For stations running the default Niagara web server, you can construct a direct URL to pull history data. The history servlet responds to requests at a path like:

https://<station-ip>/history/<history-path>?start=2024-01-01&end=2024-01-31&format=csv

The exact URL syntax depends on the station's servlet configuration and Niagara version. This approach is fragile and undocumented by Tridium, so test it on a non-production station first. It does work well for scripted pulls when you know the exact history ORD path.

Method 3: Third-Party Modules for Automated Export

When you need to export histories on a schedule, pull data from dozens of points at once, or let building owners download their own CSV files without Workbench access, third-party modules are the practical answer.

NiagaraMods CSVexportHistory

CSVexportHistory is a Niagara 4 module that adds a dedicated history-to-CSV export component to any station. Key features:

• Batch export — Select multiple histories and export them to a single CSV or individual CSV files in one operation.
• Scheduled export — Configure a Niagara schedule or trigger to run the export automatically (daily, weekly, monthly).
• File destination — Write CSV files to the station's local file system, a network share, or an FTP/SFTP server.
• Column configuration — Customize which columns appear in the output (timestamp format, value precision, status flags).

Installation follows the standard Niagara module process: copy the .jar file to the station's modules directory, restart the station, and add the CSVexportHistory component from the palette. Configuration is done through Workbench property sheets.

# Typical CSVexportHistory configuration
# -----------------------------------------------
# Component: /Services/CsvExportService
# Properties:
#   Output Directory:     /shared/history_exports/
#   File Name Pattern:    {historyName}_{date}.csv
#   Date Format:          yyyy-MM-dd HH:mm:ss
#   Delimiter:            comma
#   Include Header:       true
#   Schedule:             Weekly - Monday 02:00
#   Histories:            /AHU_1/*, /Boiler/*, /Chiller/*

OneSight ossEasyHistoryExport

ossEasyHistoryExport from the OneSight platform provides a web-based interface for history export, making it accessible to facility staff who don't have Workbench installed. Key features:

• Browser-based UI — Operators access the export page through the station's web interface. No Workbench required.
• Point picker — A graphical point selection tool lets users choose which histories to include in the export.
• Flexible time ranges — Preset ranges (last 24 hours, last 7 days, last month) and custom date pickers.
• Merged output — Combine multiple histories into a single CSV file with aligned timestamps, which saves significant post-processing time in Excel.

This module is particularly useful in managed services scenarios where a controls contractor needs to give a facility manager self-service access to trend data without exposing Workbench or granting admin-level station access.

Building Systems LLC Export Guide

Building Systems LLC has published a step-by-step walkthrough covering the manual Workbench export process with screenshots and tips for large-volume exports. Their guide addresses common pitfalls like timezone handling in exported timestamps and dealing with history rollover on memory-constrained JACEs. It is a useful companion reference for teams standardizing their export procedures.

Method 4: BQL and Fox Protocol Queries

For integrators comfortable with Niagara's query mechanisms, BQL (Baja Query Language) and the Fox protocol offer programmatic access to history data. This is the most flexible approach but requires deeper platform knowledge.

BQL Queries in Workbench

BQL lets you query history records directly from the Workbench BQL console or from a Px page. A basic history query looks like this:

# BQL query to retrieve history records
# Open: Station > Spy Pages > BQL Query
# -----------------------------------------------

# List all histories on the station:
history:

# Query a specific history with a time range:
history:/AHU_1/DischargeAirTemp?period=last7Days

# Query with a custom absolute time range:
history:/AHU_1/DischargeAirTemp?period=2024-01-01..2024-01-31

# Query with rollup (e.g., hourly averages):
history:/AHU_1/DischargeAirTemp?period=last30Days;rollup=avg;rollupInterval=1hr

BQL results display in Workbench as a table. You can then use the File > Export method from Method 1 to save the filtered results to CSV. The advantage over the standard History pane is that BQL supports rollups (average, min, max, sum) and interpolation, letting you pre-process the data before export.

Fox Protocol for Remote Access

The Fox protocol is Niagara's native binary communication protocol. External applications that implement a Fox client can connect to a station and pull history data programmatically. This approach is used by enterprise integration platforms and custom reporting applications that need automated, scheduled data extraction without human interaction.

Writing a Fox client from scratch is non-trivial—it requires the Niagara SDK and a solid understanding of the Baja object model. Most teams that need this level of automation are better served by the third-party modules in Method 3 unless they already have Niagara development resources in-house.

# Pseudocode: Fox client history export
# -----------------------------------------------
# 1. Establish Fox session to station
# 2. Resolve history ORD: slot:/History/AHU_1/DischargeAirTemp
# 3. Create BHistoryTimeQuery with start/end timestamps
# 4. Execute query -> returns BIHistory cursor
# 5. Iterate cursor, write each record to CSV:
#      timestamp, value, status
# 6. Close session
#
# Note: Requires bajaux and baja-history JAR dependencies

Common Mistakes When Exporting Niagara History Data

• Forgetting to set the time range before exporting. Workbench defaults to showing all stored records. On a JACE that has been logging a point every 60 seconds for two years, that's over a million rows per history. Exporting without narrowing the date range produces massive files and can take several minutes per history. Always set your time range first.
• Ignoring timezone offsets in timestamps. Niagara stores history timestamps in the station's configured timezone. When you export to CSV, the timestamps include the UTC offset (e.g., -05:00 for Eastern). If you import these into Excel without accounting for the offset, your data will appear time-shifted when compared against other data sources. Standardize on UTC or your local timezone before analysis.
• Exporting from a memory-constrained JACE during business hours. Pulling large history datasets from a JACE 8000 or similar edge controller consumes RAM and CPU. On a controller that is already running near its memory ceiling, a bulk history export can trigger garbage collection pauses or, in extreme cases, a station restart. Schedule large exports during off-hours or pull from the Supervisor if one exists in the architecture.
• Not checking history capacity and rollover settings. Niagara histories have a configurable record capacity (e.g., 5,000 or 50,000 records). When the capacity is reached, the oldest records are overwritten. If you're exporting data for archival purposes, you need to export before the rollover cycle overwrites the records you need. Check the Capacity and Full Policy properties on each history extension.
• Assuming all histories use the same interval. Different points may log at different intervals—a zone temp might log every 5 minutes while an equipment status logs on change-of-value (COV). When you merge multiple histories into a single CSV for analysis, the timestamps won't align unless you use BQL rollups or post-process the data in Excel with interpolation.

Platform Compatibility

The methods described in this guide apply across Niagara 4.x stations regardless of the underlying hardware. Here is a compatibility summary:

Niagara AX (3.x) note: The manual Workbench export process is similar on Niagara AX, but the BQL syntax and web servlet paths differ. Third-party modules built for Niagara 4 are not backward-compatible with AX stations. If you're still running AX, check with the module vendor for an AX-compatible version or plan a migration to N4.

Sources and Attribution

The technical guidance in this entry is informed by the following sources:

• Building Systems LLC — Step-by-step guide for Niagara 4 history export procedures, including Workbench navigation and large-dataset handling considerations.
• OneSight ossEasyHistoryExport Documentation — Product documentation for the ossEasyHistoryExport module, covering web-based history export configuration and multi-history merged CSV output.
• NiagaraMods CSVexportHistory — Module documentation for CSVexportHistory, including scheduled export setup, file naming conventions, and FTP/SFTP destination configuration.
• Tridium Niagara 4 Technical Documentation — Official platform documentation covering the History service, BQL query syntax, history extensions, and the Fox protocol specification.