Import and export

Move tags, devices, alarms, and pages between projects with export and import — and resolve conflicts on the way in.

Rather than rebuild the same configuration in every project, you can export it from one and import it into another. It’s also the fastest way to make bulk edits: export, change many rows in a spreadsheet, and import the result back.

What you can move

The formats are symmetric — what you export is exactly what import expects, so a file from one project drops straight into another. Tags, devices, and alarms are plain CSV, so you can open and edit them in any spreadsheet before importing.

Exporting

For tags, devices, or alarms, open the root of that section (Tags or Alarms), then More → Export and choose what to export. You get a CSV named after the project (e.g. My project tags.csv).

Pages are exported one at a time from a page’s menu.

Importing

Importing tags, devices, or alarms runs a short wizard that shows you exactly what will change before anything is written.

1. Start it and upload

Open the section root and choose More → Import (for tags and devices, pick Tags or Devices). Drop in the CSV and Continue — the file is checked against what’s already in the project, sorting rows into new, conflicting, and missing.

Beside Continue there’s an Import button that does the whole thing in one step: it uploads, updates anything that matches, and skips the conflict, delete, and confirmation screens entirely. Use it when you already know the file is right — re-importing a file you just exported and edited, say. Use Continue when you want to see what will change first, which is most of the time. Nothing is deleted either way; the one-click path only creates and updates.

2. Resolve conflicts

If the file has rows that already exist in the project, you choose a conflict strategy:

• Do not update conflicting items (default) — existing items are left as they are; only genuinely new rows are added.
• Update all items from the file — existing items are overwritten with the file’s values.

This step only appears when there are conflicts. More info lists exactly which items conflict.

3. Decide on what’s missing

If the project contains items that aren’t in the file, you choose a delete strategy:

• Do not delete (default) — extra items are kept.
• Delete a selection — pick, item by item, which of the unmatched items to remove.

Use this when the file is meant to be the full, authoritative set. Like the conflict step, it only appears when it applies.

4. Confirm

A summary spells out the outcome — Create N, update N, delete N — before you commit. Import runs in the background (it can take a couple of minutes for large files), and when it finishes you get a matching Created / updated / deleted summary and a Download log for your records.

Tag values

The CSV above carries a project’s tag configuration. Tag values — what each tag actually read — are exported and imported separately, at a point in time you choose. See Export and update tag values.

Good to know

• Import is all-or-nothing per type. If the file has invalid rows (missing path, wrong type, duplicates), the whole import is rejected with an error — nothing is half-applied. Fix the file and try again.
• Editing in a spreadsheet is expected. The CSV round-trips cleanly, so exporting, adjusting many rows, and re-importing with Update all items from the file is a supported way to bulk-edit.
• Importing needs a configuring role. It changes the project’s content, so it’s a Manager (or Admin) action — see the roles matrix.