Home › Converters › Keeper to Proton Pass
Keeper to Proton Pass converter
Keeper and Proton Pass both use CSV, but the two formats don't line up — so Proton Pass rejects a raw Keeper export or silently files everything into the wrong fields. Drop your export below and get back a file Proton Pass accepts.
Convert your Keeper export
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.
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 column | Proton Pass column | What happens |
|---|---|---|
column 2 | name | 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 | note | Renamed and repositioned |
column 1 | vault | Renamed and repositioned |
What carries over
| Field | Keeper | Proton Pass | Result |
|---|---|---|---|
| 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
- Sign in to the Keeper Web Vault.
- Open the account menu → Settings → Export.
- Choose the .csv format and confirm.
Watch out for
- 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.
- Subfolders use a backslash: Work\Clients. Forward slashes stay literal.
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 Proton Pass'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 Proton Pass 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 Proton Pass
- Open Proton Pass → Settings → Import.
- Choose the matching source, or "Generic CSV" if the source is not listed.
- Upload the converted file and pick a destination vault.
Watch out for
- Proton Pass splits identity between email and username. If your source only has one login field, the converter puts an address that looks like an email in the email column and everything else in username.
- The vault column controls which Proton vault an item lands in. Folders from the source map onto it.
Step 4 — Verify and clean up
- Open ten entries in Proton Pass at random and check them against Keeper.
- Generate a 2FA code for one account in Proton Pass and confirm it matches Keeper. A TOTP secret that imported wrong fails silently until you're locked out.
- Sign in to one real site using Proton Pass to confirm autofill works.
- Delete both CSV files and empty your trash. If your Downloads folder syncs to iCloud, OneDrive or Dropbox, confirm the deletion propagated there too.
- Only then close your Keeper account — and change any password you suspect was exposed while the plaintext file existed.
Questions
Why won't Proton Pass 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 Proton Pass'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 Proton Pass?
Proton Pass can't natively store: custom fields, file attachments. Rather than drop that data, the converter writes it into the notes field where Proton Pass 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 Proton Pass 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 Proton Pass?
Proton Pass splits identity between email and username. If your source only has one login field, the converter puts an address that looks like an email in the email column and everything else in username.
Related converters
Other routes out of Keeper
- Keeper → 1Password
- Keeper → Apple Passwords
- Keeper → Bitwarden
- Keeper → Dashlane
- Keeper → Enpass
- Keeper → Google Chrome
- Keeper → KeePassXC
- Keeper → LastPass
- Keeper → Microsoft Edge
- Keeper → Mozilla Firefox
- Keeper → NordPass
- Keeper → RoboForm
- Keeper → Safari
Other ways into Proton Pass
- 1Password → Proton Pass
- Apple Passwords → Proton Pass
- Bitwarden → Proton Pass
- Dashlane → Proton Pass
- Enpass → Proton Pass
- Google Chrome → Proton Pass
- KeePassXC → Proton Pass
- LastPass → Proton Pass
- Microsoft Edge → Proton Pass
- Mozilla Firefox → Proton Pass
- NordPass → Proton Pass
- RoboForm → Proton Pass
- Safari → Proton Pass
Moving the other way? Proton Pass → Keeper · All 210 converters