Bring your passwords, notes, TOTP codes, passkeys, and attachments from any major password manager. Preview everything before you commit. Nothing gets lost.
Find your current manager below. We auto-detect the file format, parse everything, and preserve as much as the export allows.
Export from the old. Open ZZPass and pick the file. Review the preview list. That's the whole process.
Most managers offer export in Settings → Export. Pick CSV or 1PUX, save the file somewhere you'll find it.
Open Settings → Import in ZZPass and pick the file. The format is auto-detected — Chrome, LastPass, Bitwarden, 1Password, iCloud Keychain — and parsed instantly.
Every item appears in a searchable list. Edit fields, deselect duplicates, remove anything you don't want — then commit. Nothing imports until you say so.
ZZPass catches duplicates before they happen — across your import file and across your existing vault. You decide what to do with each one.
The 1PUX archive carries far more than passwords. ZZPass reads the full structure — data files, attributes, attachments — and preserves it all.
You should own your data. If ZZPass isn't right for you, we make it easy to move on — three ways out, all of them complete.
Standard comma-separated values. Works with every password manager, spreadsheet, or scripting tool. The lowest common denominator — and that's the point.
Full 1Password-compatible bundle — passwords, notes, custom fields, attachments, passkeys, timestamps. Import directly into 1Password or any manager that reads 1PUX.
Use Apple's native credential exchange to transfer to another app. No intermediate file, no plaintext on disk. Stays inside Apple's secure transfer framework.
The trust principle Your data belongs to you. If ZZPass isn't right, we make it easy to move on. No lock-in. No data hostage.
The full data-preservation matrix across every supported import and export path. CSV covers the essentials; 1PUX preserves everything; app-transfer is a modern direct path.
| Data type | CSV import | 1PUX import | CSV export | 1PUX export | App transfer |
|---|---|---|---|---|---|
| Passwords | |||||
| Usernames | |||||
| URLs | |||||
| Notes | |||||
| TOTP codes | |||||
| Passkeys | iOS 26+ | ||||
| Attachments | |||||
| Payment cards | iOS 26+ | ||||
| Custom fields | Partial | ||||
| Timestamps |
CSV COVERS THE ESSENTIALS · 1PUX PRESERVES EVERYTHING · CHOOSE WHAT FITS YOUR NEEDS
Migration files are unencrypted by nature — that's how every manager exports them. Here's how ZZPass protects you while moving.
Export always requires your primary password. Nobody can pull data out of your vault without authenticating first — biometric unlock alone is not enough.
CSV and 1PUX files are unencrypted. ZZPass shows a clear warning before creating one — and reminds you to delete or move it somewhere safe afterward.
During import, files are read into a sandboxed temporary directory and cleaned up immediately after the process ends — even on crash or cancel.
Import and export happen entirely on your device. Files are never sent to ZZPass servers — there are no servers. Your data never leaves your hardware.
On iOS 26+, native credential exchange stays inside Apple's secure transfer framework. No intermediate file ever touches disk in plaintext.
The vault re-locks automatically after import, even if the process took longer than your normal idle timeout. Walk away with confidence.
For the technically curious — here's how ZZPass auto-detects formats based on the column headers in your export file.
Don't see your manager? If it exports to CSV, ZZPass can almost certainly read it — and you can always map columns by hand.