NT² Vault
EN

CSV import

Last updated: 28 Jun 2026

Optional feature—Settings → Import when enabled.

Who this is for

Anyone migrating from another password manager or spreadsheet who wants a one-way, local import into encrypted NT² items without uploading the CSV to NT² servers.

What you need

TierFree
Vault stateUnlocked
NetworkOffline—the CSV never leaves your device
Feature toggleCSV import enabled under Settings → Vault → Import (or Feature controls)

Steps

Enable import (if needed)

  1. Unlock your vault and open Settings → Vault → Import (https://se.nt2.me/settings/vault/import).
  2. If CSV import is disabled, turn on the Import from CSV feature toggle (see Feature controls).
  3. Select Open CSV import or navigate to https://se.nt2.me/import/csv.

Prepare your CSV

  1. Export a CSV from your old tool (1Password, Bitwarden, etc.) or save a spreadsheet as CSV.
  2. Keep a header row with column names—NT² maps columns in the next step.
  3. Remove rows you do not want migrated before import.

Map columns and preview

  1. Choose Select file and pick your CSV from disk.
  2. Map each NT² field (title, username, password, URL, notes, …) to a CSV column—or leave unmapped columns skipped.
  3. Review the preview table for parsing errors, duplicate titles, or empty required fields.
  4. Adjust mapping and re-parse if the preview shows warnings.

Commit the import

  1. Select which rows to import (or import all valid rows).
  2. Confirm Import. NT² encrypts each row into new asset items locally.
  3. Open https://se.nt2.me/assets and spot-check titles, categories, and copied secrets.
  4. Optional: delete the source CSV from disk after verifying the vault—NT² does not retain the file.

Tips and common mistakes

  • Optional feature—if Import is missing from Settings, enable it first; it is off on some deployments until toggled on.
  • One-way migration—import does not sync back to the old tool; keep a backup until you trust the new vault.
  • Category mapping—imports typically land in Credential or mapped templates; enable packs first if you need Crypto/Bank categories.
  • No cloud upload—the CSV is parsed in your browser; only resulting encrypted items sync if cloud sync is on.
  • Provenance—imported items record csv_import origin internally for support and merge logic.

Related