Import & export¶

Move data in and out of Danbyte with spreadsheets. Export to CSV or Excel, edit in your spreadsheet tool, and re-upload — Danbyte handles each row on its own, so one bad row never sinks the whole batch. You get a clear summary of what was created, updated, and skipped.

Import / Export — round-trip on every table¶

Every list page has an Import / Export button in its header, next to the Add button; every detail page has it next to Edit. It's the round-trip pair:

• Export → CSV, Excel (.xlsx), or JSON. The file carries each row's id plus stable, human-readable keys for its links, tags, and custom fields — so it can be re-imported.
• Import… → upload an edited file. Danbyte first shows a preview (how many rows would be created vs updated, and any errors) before you Apply.

Export only the rows you select: tick rows in any table and the bulk bar at the bottom gains an Export button that exports just the selection.

On a prefix page the Import / Export acts on the IP addresses inside that prefix (the workflow that replaced the old "IPs" dropdown).

Rows are matched by id first; if the id is blank or gone, by the type's natural key (a prefix by its cidr, an IP by its address, a VLAN by its number, a device by name + site); otherwise a new row is created. You need add permission to create rows and change to update them, and you can only touch rows inside your own scope — importing a row outside it is a clean per-row error, never a silent escalation.

Single objects are exportable too: a detail page (an IP, for example) has the same Import / Export button, scoped to just that object.

Exporting prefixes¶

On the Prefixes list, use the export options to download a CSV or Excel (.xlsx) file. Whatever filters you have applied on screen carry into the export, so the downloaded sheet matches what you're looking at.

The prefix and IP sheets below are just the most-used examples; the same round-trip works for every table via its Data menu.

The prefix spreadsheet¶

Importing prefixes¶

1. Prepare a .csv or .xlsx file with the columns above (an export is the easiest starting point).
2. Open the prefix import page and upload your file.
3. Review the result summary.

For each row, Danbyte:

1. Checks the cidr is valid (an invalid one is skipped and reported).
2. Finds an existing prefix — by id if present, otherwise by cidr.
3. Updates it if found, or creates a new one if not.
4. Auto-creates any referenced site, VLAN, or tag that doesn't exist yet.

If a single row fails — a bad network, malformed custom-field JSON — the rows around it still import, and the summary lists exactly which rows had problems.

Importing IP addresses¶

IP imports belong to a single prefix, so the file is tied to the prefix you export it from — you don't manage the parent on each row.

For each row, Danbyte confirms the address falls inside that prefix, then matches it against existing IPs. If the address already exists, its status, role, description, tags, and custom fields are updated in place — and it's moved into this prefix if it was elsewhere. If it doesn't exist, it's created here.

The Import hub (paste a big file)¶

For a large paste or a one-off load, the Integrations → Import hub imports any type without leaving the page — the same round-trip engine as the per-table button.

1. Go to Integrations → Import.
2. Pick the object type and the format (CSV or JSON).
3. Upload your file, or paste its contents.
4. Review the available columns — required ones are marked.
5. Click Validate to preview without saving anything.
6. Click Import — rows are matched by id/natural key, so existing rows update and new ones are created.

Results show how many rows were created vs updated, with a per-row table for any errors.

File formats¶

• CSV, Excel (.xlsx), and JSON are detected by file extension.
• CSV files should be UTF-8 (a byte-order mark is tolerated).
• Excel files are read on the server, so no spreadsheet plugin is needed.

Extending it (for developers / plugins)¶

Every registered, tenant-scoped model gets round-trip export/import automatically. A model with special keys — or a model shipped by a plugin app — customises it by subclassing ModelIOHandler and registering the handler from the app's io.py (auto-imported at startup):

# myplugin/io.py
from api.io import ModelIOHandler, register_io
from auth_api.object_types import register_object_type
from .models import Widget

class WidgetIO(ModelIOHandler):
    model = Widget
    natural_key = ["serial"]          # fallback match key when id is absent
    fk_keys = {"vendor": "name"}      # how each FK is rendered/looked up
    # override to_row / apply for full control

register_object_type("myplugin.Widget", "Widgets", "Plugins")  # RBAC + discovery
register_io(WidgetIO())

Add the app to INSTALLED_APPS and its Widgets type appears in the permission picker and gains a Data menu wherever its table is shown — no core changes.

Related¶

• Exporting tables — quick export of any list.
• Tags & custom fields — the tags and custom_fields columns.
• Permissions & access — who may import.