Home › Converters › Apple Passwords to Enpass
Apple Passwords to Enpass converter
Apple Passwords and Enpass both use CSV, but Apple Passwords writes 6 columns; Enpass expects 6 in a different order — so Enpass rejects a raw Apple export or silently files everything into the wrong fields. Drop your export below and get back a file Enpass accepts.
Convert your Apple Passwords 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 5 of 6 column names match (title, url, username), and they're in a different order — enough for Enpass to accept the file and then put your passwords in the wrong fields.
| Apple Passwords column | Enpass column | What happens |
|---|---|---|
Title | Title | Same name, position adjusted |
Username | Username | Same name, position adjusted |
Password | Password | Same name, position adjusted |
URL | URL | Same name, position adjusted |
OTPAuth | TOTP | Renamed and repositioned |
Notes | Notes | Same name, position adjusted |
What carries over
| Field | Apple | Enpass | 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 | No | Yes | Not in the source file |
| Two-factor (TOTP) secrets | Yes | Yes | Carried over |
| Favorites | No | No | Not in the source file |
| Custom fields | No | No | Not in the source file |
| Multiple URLs per entry | No | No | Not in the source file |
| File attachments | No | No | Not in the source file |
Step 1 — Export from Apple Passwords
- Open the Passwords app on macOS Sequoia or later (on older macOS: Safari → Settings → Passwords).
- Choose File → Export All Passwords… from the menu bar.
- Confirm with Touch ID or your Mac login password.
- Save Passwords.csv.
Watch out for
- Export and import are Mac-only. There is no way to do either from iPhone or iPad.
- Apple keeps TOTP codes in the OTPAuth column as full otpauth:// URIs, not bare secrets. Bare secrets will not be recognized.
Step 2 — Convert it
Drop the file onto the converter above. It parses Apple Passwords'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
- Open Enpass → Menu → File → Import.
- Choose "Other" → CSV.
- Select the converted file and map the columns.
Watch out for
- Enpass CSV export flattens custom item templates. Anything beyond title/username/password/URL/notes arrives as note text.
- Enpass exports per-vault. If you use more than one vault, export each separately and convert each file.
Step 4 — Verify and clean up
- Open ten entries in Enpass at random and check them against Apple Passwords.
- Generate a 2FA code for one account in Enpass and confirm it matches Apple. A TOTP secret that imported wrong fails silently until you're locked out.
- Sign in to one real site using Enpass 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 Apple Passwords account — and change any password you suspect was exposed while the plaintext file existed.
Questions
Why won't Enpass import my Apple Passwords file directly?
Only 5 of 6 column names match (title, url, username), and they're in a different order — enough for Enpass to accept the file and then put your passwords in the wrong fields. 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.
Does anything get lost moving from Apple Passwords to Enpass?
Enpass supports every field Apple Passwords exports, so a standard login entry survives intact — name, username, password, URL, notes, folder and 2FA secret. File attachments are the exception: no CSV export from any manager includes them, so download those separately before you close your Apple Passwords account.
Will my two-factor codes still work after the move?
Yes, as long as Apple Passwords exported the secrets. Apple Passwords 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 Apple Passwords encrypted?
No. An Apple Passwords 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 Apple Passwords's export?
Export and import are Mac-only. There is no way to do either from iPhone or iPad.
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 Apple Passwords
- Apple Passwords → 1Password
- Apple Passwords → Bitwarden
- Apple Passwords → Dashlane
- Apple Passwords → Google Chrome
- Apple Passwords → KeePassXC
- Apple Passwords → Keeper
- Apple Passwords → LastPass
- Apple Passwords → Microsoft Edge
- Apple Passwords → Mozilla Firefox
- Apple Passwords → NordPass
- Apple Passwords → Proton Pass
- Apple Passwords → RoboForm
- Apple Passwords → Safari
Other ways into Enpass
- 1Password → Enpass
- Bitwarden → Enpass
- Dashlane → Enpass
- Google Chrome → Enpass
- KeePassXC → Enpass
- Keeper → Enpass
- LastPass → Enpass
- Microsoft Edge → Enpass
- Mozilla Firefox → Enpass
- NordPass → Enpass
- Proton Pass → Enpass
- RoboForm → Enpass
- Safari → Enpass
Moving the other way? Enpass → Apple Passwords · All 210 converters