Import / Export
OpSee supports bulk import and export of master data across several modules. This page gives a quick-reference overview; each module has its own detailed import/export documentation.
Where import / export is available
| Module | Supported data | Format | Where to find it |
|---|---|---|---|
| Equipment | Equipment hierarchy | XLSX | Equipment grid toolbar |
| OEE Config — Loss Types | Loss types | CSV, XLSX, JSON | Loss Types grid toolbar |
| OEE Config — Reasons | Reasons | CSV, XLSX, JSON | Reasons grid toolbar |
| OEE Config — Reason Trees | Reason tree structure | CSV, XLSX, JSON | Reason Trees grid toolbar |
| Personnel — Schedules | Schedules | CSV, XLSX, JSON | Schedules grid toolbar |
| Administration | All bulk operations | CSV, XLSX, JSON | Admin → Import/Export |
How it works
Every import/export dialog follows the same pattern:
Exporting
- Click the Export button in the toolbar of the relevant grid
- Choose your format (XLSX is recommended for editing; CSV for scripting)
- Optionally configure options (filename, whether to include disabled records)
- Click Export: the file downloads to your browser immediately
The export reflects the current filter state. If you have filtered to a specific equipment group, only those records are exported.
Importing
- Click the Import button in the toolbar
- Download the template (provided in the dialog) to see the expected column format
- Fill in the template with your data
- Upload the file: OpSee validates the data before writing it to the database
- Any validation errors are shown row-by-row before the import is committed
:::warning Use the template Always start from the downloaded template for imports. Column order, headers, and data formats must match exactly. OpSee will reject files with unexpected columns. :::
Supported formats
| Format | Best for |
|---|---|
| XLSX | Manual editing in Excel or LibreOffice |
| CSV | Script-based processing or system integrations |
| JSON | API-style integrations and version-controlled data |
Export language
Exports use the current UI language. If you need localized names (for example, French reason names), switch the UI to French before exporting.
Prerequisites
- Interface Overview — understand the page layout
Next steps
- Equipment Import / Export — equipment hierarchy bulk operations
- Administration Import / Export — full admin bulk operations reference
Related
- Filtering and Searching — filter data before exporting