Home › Converters › Proton Pass to RoboForm
Proton Pass to RoboForm converter
Proton Pass and RoboForm both use CSV, but Proton Pass writes 11 columns; RoboForm expects 7 in a different order — so RoboForm rejects a raw Proton Pass export or silently files everything into the wrong fields. Drop your export below and get back a file RoboForm accepts.
Convert your Proton Pass 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
Only 3 of 11 column names match (name, url, note), and they're in a different order — enough for RoboForm to accept the file and then put your passwords in the wrong fields.
| Proton Pass column | RoboForm column | What happens |
|---|---|---|
name | Name | Renamed and repositioned |
username | Login | Renamed and repositioned |
password | Pwd | Renamed and repositioned |
url | Url | Renamed and repositioned |
totp | — none — | RoboForm has no 2fa secret field. Written into notes instead of dropped. |
note | Note | Renamed and repositioned |
vault | Folder | Renamed and repositioned |
What carries over
| Field | Proton Pass | RoboForm | 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 | No | Yes | Not in the source file |
| Multiple URLs per entry | No | No | Not in the source file |
| File attachments | Yes | No | No CSV export includes attachments. Download them out of Proton Pass separately before you close the account — this is the one thing people lose permanently. |
Step 1 — Export from Proton Pass
- Open Proton Pass on the web or in the desktop app.
- Go to Settings → Export.
- Choose CSV, confirm with your Proton password.
- Save the file.
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 2 — Convert it
Drop the file onto the converter above. It parses Proton Pass's layout, maps each field onto the universal record, then writes RoboForm'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 RoboForm 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 RoboForm
- Open RoboForm → Options → Account & Data → Import.
- Choose "Other" → CSV file.
- Select the converted file.
Watch out for
- The RfFieldsV2 column packs every extra form field into one delimited blob. It is RoboForm-specific and cannot be read by any other manager — the converter unpacks what it can into notes.
- Export requires the Windows or macOS desktop editor; the extension alone will not do it.
Step 4 — Verify and clean up
- Open ten entries in RoboForm at random and check them against Proton Pass.
- Generate a 2FA code for one account in RoboForm and confirm it matches Proton Pass. A TOTP secret that imported wrong fails silently until you're locked out.
- Sign in to one real site using RoboForm 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 Proton Pass account — and change any password you suspect was exposed while the plaintext file existed.
Questions
Why won't RoboForm import my Proton Pass file directly?
Only 3 of 11 column names match (name, url, note), and they're in a different order — enough for RoboForm to accept the file and then put your passwords in the wrong fields. The converter rewrites the file into RoboForm'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 Proton Pass to RoboForm?
RoboForm can't natively store: file attachments. Rather than drop that data, the converter writes it into the notes field where RoboForm has one, so you can move it back by hand. Keep your Proton Pass 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 Proton Pass exported the secrets. Proton Pass and RoboForm 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 Proton Pass encrypted?
No. A Proton Pass 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 Proton Pass's export?
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.
Anything unusual about importing into RoboForm?
The RfFieldsV2 column packs every extra form field into one delimited blob. It is RoboForm-specific and cannot be read by any other manager — the converter unpacks what it can into notes.
Related converters
Other routes out of Proton Pass
- 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 → Keeper
- Proton Pass → LastPass
- Proton Pass → Microsoft Edge
- Proton Pass → Mozilla Firefox
- Proton Pass → NordPass
- Proton Pass → Safari
Other ways into RoboForm
- 1Password → RoboForm
- Apple Passwords → RoboForm
- Bitwarden → RoboForm
- Dashlane → RoboForm
- Enpass → RoboForm
- Google Chrome → RoboForm
- KeePassXC → RoboForm
- Keeper → RoboForm
- LastPass → RoboForm
- Microsoft Edge → RoboForm
- Mozilla Firefox → RoboForm
- NordPass → RoboForm
- Safari → RoboForm
Moving the other way? RoboForm → Proton Pass · All 210 converters