Exporting your entire account and the file structure

With Export entire account you download all data of your organisation in one ZIP file. It contains the settings, gateways, Modbus devices, registers, alarms, automations, dashboards, reports, customers and members, plus the readings within the retention period of 365 days. The export is free and uses open formats that software can read (CSV and JSON).

This page also describes how the files are structured. It is the overview of export formats that the European Data Act asks for when you switch to another provider.

Requesting an export

1. Open the settings

   Open Settings and choose Data export.

2. Request the export

   Click Request export. The Export entire account window opens.

3. Choose what goes in

   Choose the File format (CSV for Excel or JSON), the detail of the Readings (every reading, per 15 minutes, per hour or per day) and the Period (everything within the retention period or your own dates). If you have customers, choose the entire account or one customer under Customers.

4. Start the export

   Click Start export. The file is put together in the background. You get an email as soon as it is ready.

5. Download the file

   The button in the email opens Data export in the portal. Click Download next to the export there.

Contents of the ZIP file

Every file in config/ is a JSON array with one object per row. Ids are UUIDs and link the files. device_id refers to a gateway, modbus_dev_id to a Modbus device and register_id to a register.

Not in the export on purpose are secrets (tokens, API keys and their hash, passwords, the webhook secret and the values of custom headers, the codes of share links and invitations), internal data of the automatic monitoring and IP addresses in the audit log.

Readings as CSV

All CSV files are UTF-8 with a BOM, so Excel shows characters such as °C correctly. In Dutch and German a semicolon separates the columns and numbers use a decimal comma. In English a comma separates the columns and numbers use a dot. Times are local time of the organisation as YYYY-MM-DD HH:MM:SS. Values are converted with the scale factor of the register, as the portal shows them.

Every reading

One row per timestamp and one column per register. The column header is Modbus device / Register (unit), with [removed] for a removed register. manifest.json lists for every file which register is in which column. If a register has two readings at the same timestamp, the file holds the first.

Per 15 minutes, hour or day

One row per bucket per register with these columns.

Buckets of 15 minutes and an hour follow the clock. A day runs from midnight to midnight in the timezone of the organisation, so 23 or 25 hours when daylight saving time changes.

Readings as JSON

JSON files follow the format modbuscloud.readings, version 1. First the details of the export and the registers, then the values. Times in JSON are UTC in ISO 8601.

{
  "format": "modbuscloud.readings",
  "format_version": 1,
  "generated_at": "2026-10-15T09:00:00.000Z",
  "gateway": { "serial": "6008123409", "name": "Cabinet 1" },
  "timezone": "Europe/Amsterdam",
  "resolution": "day",
  "from": "2026-09-30T22:00:00.000Z",
  "to": "2026-10-15T09:00:00.000Z",
  "truncated": false,
  "row_limit": null,
  "complete_from": null,
  "values_scaled": true,
  "registers": [
    { "id": "53e8429e-...", "name": "Energy import", "unit": "kWh", "modbus_device": "kWh meter 1",
      "slave_id": 1, "address": 30001, "data_type": "uint32", "scale_factor": 0.1, "counter": true, "retired": false }
  ],
  "buckets": [
    { "start": "2026-09-30T22:00:00.000Z", "end": "2026-10-01T22:00:00.000Z", "register_id": "53e8429e-...",
      "count": 96, "avg": 1452.3, "min": 1447.1, "max": 1457.6, "first": 1447.1, "last": 1457.6, "delta": 10.5, "delta_reset": false }
  ]
}

Consumption of counters

A register is a counter when it is set up or recognised as one, such as a kWh meter reading, a volume or operating hours. The consumption of a bucket is the last value of that bucket minus the last value of the previous bucket with readings. For the first bucket the last value from the 7 days before counts. If the value drops, because the counter was reset or the meter was replaced, the consumption of that bucket is empty and Counter reset is yes (delta_reset: true in JSON). The bar chart with consumption in a dashboard uses the same rule.

Readings of one gateway

Download readings in the menu of a gateway offers the same formats and the same detail. Such a file holds at most 500,000 readings. If there are more, you get the newest and the first line of the CSV (or complete_from in JSON) says from which moment the file is complete. See Download readings.