Movepasswords

HomeConverters › Enpass to Bitwarden

Enpass to Bitwarden converter

Enpass and Bitwarden both use CSV, but Enpass writes 6 columns; Bitwarden expects 11 in a different order — so Bitwarden rejects a raw Enpass export or silently files everything into the wrong fields. Drop your export below and get back a file Bitwarden accepts.

Convert your Enpass export

Drop your Enpass CSV here or click to choose a file — nothing is uploaded

The conversion runs entirely in this tab using JavaScript. Your file is never sent to a server — you can confirm it by opening your browser's Network tab, or by turning off Wi-Fi before you drop the file in. Prefer not to do this in a browser tab at all? Download the converter and run it from your own disk.

Your export file is plaintext. Both the file Enpass gives you and the one you download here contain every password in readable form. Delete them as soon as the import is verified, and empty your trash.

What's actually different between the two formats

Only 1 of 6 column names match (notes), and they're in a different order — enough for Bitwarden to accept the file and then put your passwords in the wrong fields.

Enpass columnBitwarden columnWhat happens
Title name Renamed and repositioned
Username login_username Renamed and repositioned
Password login_password Renamed and repositioned
URL login_uri Renamed and repositioned
TOTP login_totp Renamed and repositioned
Notes notes Renamed and repositioned
— none — folder Left empty — Enpass exports nothing for this.
— none — favorite Left empty — Enpass exports nothing for this.

What carries over

FieldEnpassBitwardenResult
Item name / title Yes Yes Carried over
Username and password Yes Yes Carried over
Website URL Yes Yes Carried over
Notes Yes Yes Carried over
Folders / groups Yes Yes Carried over
Two-factor (TOTP) secrets Yes Yes Carried over
Favorites No Yes Not in the source file
Custom fields No Yes Not in the source file
Multiple URLs per entry No Yes Not in the source file
File attachments Yes No No CSV export includes attachments. Download them out of Enpass separately before you close the account — this is the one thing people lose permanently.

Step 1 — Export from Enpass

  1. Open the Enpass desktop app and unlock your vault.
  2. Go to Menu → File → Export.
  3. Choose the vault and select CSV as the format.
  4. Enter your master password and save.

Watch out for

Step 2 — Convert it

Drop the file onto the converter above. It parses Enpass's layout, maps each field onto the universal record, then writes Bitwarden's exact expected columns — including the empty ones its importer requires and, where the two differ, the right shape for 2FA secrets. You'll see a preview and a list of anything Bitwarden can't hold before you download.

Rather not put this file in a browser tab connected to the internet? The same converter is available as a single HTML file you can download and open with your network switched off.

Step 3 — Import into Bitwarden

  1. Sign in to the Bitwarden web vault at vault.bitwarden.com.
  2. Go to Tools → Import data.
  3. Under "File format", pick Bitwarden (csv).
  4. Choose the converted file and select Import data.

Official instructions: Bitwarden import documentation

Watch out for

Step 4 — Verify and clean up

  1. Open ten entries in Bitwarden at random and check them against Enpass.
  2. Generate a 2FA code for one account in Bitwarden and confirm it matches Enpass. A TOTP secret that imported wrong fails silently until you're locked out.
  3. Sign in to one real site using Bitwarden to confirm autofill works.
  4. Delete both CSV files and empty your trash. If your Downloads folder syncs to iCloud, OneDrive or Dropbox, confirm the deletion propagated there too.
  5. Only then close your Enpass account — and change any password you suspect was exposed while the plaintext file existed.

Questions

Why won't Bitwarden import my Enpass file directly?

Only 1 of 6 column names match (notes), and they're in a different order — enough for Bitwarden to accept the file and then put your passwords in the wrong fields. The converter rewrites the file into Bitwarden's exact expected layout, including the column order and any empty columns its importer requires.

Do my passwords get uploaded anywhere?

No. The conversion is JavaScript running in your own browser tab — the file is read with the FileReader API, transformed in memory, and handed back to you as a download. There is no upload, no server-side processing and no analytics attached to the file. You can verify this by disconnecting from the internet before you drop the file in: the conversion still works.

What gets lost moving from Enpass to Bitwarden?

Bitwarden can't natively store: file attachments. Rather than drop that data, the converter writes it into the notes field where Bitwarden has one, so you can move it back by hand. Keep your Enpass account active until you've confirmed everything you need made it across.

Will my two-factor codes still work after the move?

Yes, as long as Enpass exported the secrets. Enpass and Bitwarden store them in different shapes — one uses a bare Base32 secret, the other a full otpauth:// URI — and the converter translates between them, which is the step most manual migrations get wrong. Check a couple of codes against your old vault before you delete it, since a TOTP secret that fails to import is silent until you're locked out.

Is the export file from Enpass encrypted?

No. An Enpass CSV export is plaintext — every password in it is readable by anything that can open the file, including other apps on your machine and anything that syncs your Downloads folder to the cloud. Convert it, import it, then delete both files and empty your trash. If your Downloads folder syncs to iCloud, OneDrive or Dropbox, check that the deletion propagated.

Anything unusual about Enpass's export?

Enpass CSV export flattens custom item templates. Anything beyond title/username/password/URL/notes arrives as note text.

Anything unusual about importing into Bitwarden?

Bitwarden prefixes bare domains with http:// on import. If you care about https, put the full URL in the login_uri column.

Related converters

Other routes out of Enpass

Other ways into Bitwarden

Moving the other way? Bitwarden Enpass · All 210 converters