Data Import
Most factories already have data before UpBlue arrives: Excel sheets with production numbers, CSV exports from old systems, manual logs. Data Import brings that history into UpBlue, so your dashboards and trends don’t start at zero.
Imported data behaves exactly like collected data: it becomes datapoints on tags, with timestamps and labels.
Importing a CSV or Excel file
Upload
Select the file. A preview of the first rows is shown, so you can check that the file is read correctly.
Skip rows
Does the file start with title or header rows above the real column names? Set the number of rows to skip.
Map the columns
Tell UpBlue what each column is:
- Timestamp — the column with the date/time, and its format.
- Value — a column with measurements. The column header becomes the tag name, or map it to a tag yourself.
- Label — a column that describes the row, for example a machine name. The values become labels on the datapoints.
Auto-map columns does a first guess; check and correct it. If the file has no usable column headers, set a Static Tag Name that all values are imported under.
Import
Start the import. The job list shows the progress live. Large files are processed in the background — you can leave the page.
Do a small test first: import a file with a handful of rows and check the result on the tag page. Correct mapping mistakes before importing years of history.
Check the timestamp format carefully, especially day/month order (is 04-05-2026 April or May?). A wrong format puts all datapoints on the wrong moment.
Importing a VictoriaMetrics JSON file
This is the format of the tag Download button. Use it to bring exported UpBlue data back in, for example to move a tag to another organisation. Choose VictoriaMetrics JSON in the New Import menu and upload the file — no mapping needed, the file contains everything.