Movepasswords

Home › Converters › Keeper to Enpass

Keeper to Enpass converter

Keeper and Enpass both use CSV, but the two formats don't line up — so Enpass rejects a raw Keeper export or silently files everything into the wrong fields. Drop your export below and get back a file Enpass accepts.

Convert your Keeper export

Drop your Keeper 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 Keeper 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

Keeper exports without a header row, so the destination has no way to know which column is which.

Keeper columnEnpass columnWhat happens
column 2 Title Renamed and repositioned
column 3 Username Renamed and repositioned
column 4 Password Renamed and repositioned
column 5 URL Renamed and repositioned
— none — TOTP Left empty — Keeper exports nothing for this.
column 6 Notes Renamed and repositioned
column 1 — none — Enpass has no folder field. Written into notes instead of dropped.

What carries over

FieldKeeperEnpassResult
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 No Not in the source file
Custom fields Yes No Flattened into notes as name: value pairs.
Multiple URLs per entry No No Not in the source file
File attachments Yes No No CSV export includes attachments. Download them out of Keeper separately before you close the account — this is the one thing people lose permanently.

Step 1 — Export from Keeper

  1. Sign in to the Keeper Web Vault.
  2. Open the account menu → Settings → Export.
  3. Choose the .csv format and confirm.

Watch out for

Step 2 — Convert it

Drop the file onto the converter above. It parses Keeper's layout, maps each field onto the universal record, then writes Enpass'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 Enpass 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 Enpass

  1. Open Enpass → Menu → File → Import.
  2. Choose "Other" → CSV.
  3. Select the converted file and map the columns.

Watch out for

Step 4 — Verify and clean up

  1. Open ten entries in Enpass at random and check them against Keeper.
  2. Generate a 2FA code for one account in Enpass and confirm it matches Keeper. A TOTP secret that imported wrong fails silently until you're locked out.
  3. Sign in to one real site using Enpass 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 Keeper account — and change any password you suspect was exposed while the plaintext file existed.

Questions

Why won't Enpass import my Keeper file directly?

Keeper exports without a header row, so the destination has no way to know which column is which. The converter rewrites the file into Enpass'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 Keeper to Enpass?

Enpass can't natively store: custom fields, file attachments. Rather than drop that data, the converter writes it into the notes field where Enpass has one, so you can move it back by hand. Keep your Keeper 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 Keeper exported the secrets. Keeper and Enpass 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 Keeper encrypted?

No. A Keeper 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 Keeper's export?

Keeper CSV has no header row. The column order is fixed: folder, title, login, password, website, notes, shared folder, then custom field name/value pairs. Adding a header row makes Keeper import it as an entry.

Anything unusual about importing into Enpass?

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

Related converters

Other routes out of Keeper

Other ways into Enpass

Moving the other way? Enpass → Keeper · All 210 converters