Import & export your data

Everything lives under Settings → Import & Export.

Exporting

Export everything downloads a single JSON file containing your maps (with every node and edge), assets, notes (decrypted), vaults, and credentials. Credentials stored in end-to-end encrypted vaults are included as encrypted blobs — the server never has those keys, so only your vault passphrase can open them.

Keep an export before any big cleanup. It's also your migration path out — we believe tools that hold your documentation hostage don't deserve it.

Prefer not to think about it? Enable the weekly backup reminder under Settings → Notifications — a Monday email with a snapshot of what you have and a one-click export link.

Importing

There's one import button. Pick any files — the format is detected automatically:

| You give it | It becomes | | --------------------------------------------- | ------------------------------------------------- | | A Layer8 export (.json) | Assets, notes, and credentials restored | | IT Glue Configurations (.csv or API export) | AssetTrakr assets — status and org folded in | | IT Glue Passwords (.csv or API export) | CryptKeepr credentials — category becomes a tag | | Bitwarden export (.json or .csv) | CryptKeepr credentials | | LastPass export (.csv) | CryptKeepr credentials (folders become tags) | | KeePass export (.csv) | CryptKeepr credentials (groups become tags) | | Inventory CSV (Snipe-IT and similar) | AssetTrakr assets | | Markdown / text files | NoteTakr notes (title from the first # heading) |

For live networks there's also the discovery script, which seeds AssetTrakr from a subnet scan instead of a file.

You'll see a preview of what was detected — file by file, with counts per app — before anything is written. Unrecognized files are skipped and say so.

Or just paste

Even lower friction: paste straight into the box on the Import & Export page — a copied spreadsheet range (tab-delimited), a CSV, a password-manager export, or a bare list of IPs and hostnames (which become assets). The format is detected as you type, with the same preview before anything is written.

Asset CSV columns

For inventory CSVs, a name column is required; type, category, status, manufacturer, model, serial, location, warranty, vendor, assigned to, and notes are picked up when present. Header matching is forgiving about case, spaces, and underscores.

Migrating from IT Glue

Two paths, both auto-detected — no column remapping needed:

• CSV. From IT Glue, open Configurations (or Passwords) and use the Export button. Import each file the same way as anything else. Configuration Type maps to the asset's type, Configuration Status maps to online/offline/retired, and Organization, Asset Tag, and Primary IP are folded into the asset's notes since Layer8 doesn't use IT Glue's per-client structure. Passwords keep their category as a tag.
• API. If you're scripting the migration against IT Glue's v1 API, dump a resource's GET response straight to a .json file (one resource type per file) — the JSON:API shape is detected automatically. Note that IT Glue's Passwords list endpoint omits the secret value unless your script calls the reveal endpoint per record; credentials without a password are skipped rather than imported empty.