Home › Converters › Dashlane to 1Password
Dashlane to 1Password converter
Dashlane and 1Password both use CSV, but Dashlane writes 9 columns; 1Password expects 9 in a different order — so 1Password rejects a raw Dashlane export or silently files everything into the wrong fields. Drop your export below and get back a file 1Password accepts.
Convert your Dashlane 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 4 of 9 column names match (username, title, password), and they're in a different order — enough for 1Password to accept the file and then put your passwords in the wrong fields.
| Dashlane column | 1Password column | What happens |
|---|---|---|
title | Title | Renamed and repositioned |
username | Username | Renamed and repositioned |
password | Password | Renamed and repositioned |
url | Url | Renamed and repositioned |
otpSecret | OTPAuth | Renamed and repositioned |
note | Notes | Renamed and repositioned |
category | Tags | Renamed and repositioned |
— none — | Favorite | Left empty — Dashlane exports nothing for this. |
What carries over
| Field | Dashlane | 1Password | 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 | Yes | 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 | Yes | No | No CSV export includes attachments. Download them out of Dashlane separately before you close the account — this is the one thing people lose permanently. |
Step 1 — Export from Dashlane
- Sign in to the Dashlane web app at app.dashlane.com.
- Open My account → Settings → Export data.
- Choose "Export as CSV" and confirm with your Master Password.
- Dashlane downloads a ZIP — unzip it and use credentials.csv.
Official instructions: Dashlane export documentation
Watch out for
- Dashlane exports a ZIP containing several CSVs (credentials, payments, ids, securenotes). Logins live in credentials.csv — that is the file to convert.
- Dashlane has three username columns. The alternates hold secondary logins for the same site; most targets only have one username field, so the extras belong in notes.
Step 2 — Convert it
Drop the file onto the converter above. It parses Dashlane's layout, maps each field onto the universal record, then writes 1Password'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 1Password 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 1Password
- Open the 1Password desktop app and choose File → Import.
- Select "Other" or the matching source, then choose CSV.
- Pick the converted file and map columns if prompted.
- Confirm the destination vault and import.
Official instructions: 1Password import documentation
Watch out for
- 1Password CSV export only covers Login and Password items — secure notes, documents, custom fields and linked items stay behind. Use .1pux if you need those.
- Exports come out of the desktop app only; there is no CSV export in the 1Password browser extension or web app.
Step 4 — Verify and clean up
- Open ten entries in 1Password at random and check them against Dashlane.
- Generate a 2FA code for one account in 1Password and confirm it matches Dashlane. A TOTP secret that imported wrong fails silently until you're locked out.
- Sign in to one real site using 1Password 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 Dashlane account — and change any password you suspect was exposed while the plaintext file existed.
Questions
Why won't 1Password import my Dashlane file directly?
Only 4 of 9 column names match (username, title, password), and they're in a different order — enough for 1Password to accept the file and then put your passwords in the wrong fields. The converter rewrites the file into 1Password'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 Dashlane to 1Password?
1Password can't natively store: file attachments. Rather than drop that data, the converter writes it into the notes field where 1Password has one, so you can move it back by hand. Keep your Dashlane 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 Dashlane exported the secrets. Dashlane and 1Password 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 Dashlane encrypted?
No. A Dashlane 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 Dashlane's export?
Dashlane exports a ZIP containing several CSVs (credentials, payments, ids, securenotes). Logins live in credentials.csv — that is the file to convert.
Anything unusual about importing into 1Password?
1Password CSV export only covers Login and Password items — secure notes, documents, custom fields and linked items stay behind. Use .1pux if you need those.
Related converters
Other routes out of Dashlane
- Dashlane → Apple Passwords
- Dashlane → Bitwarden
- Dashlane → Enpass
- Dashlane → Google Chrome
- Dashlane → KeePassXC
- Dashlane → Keeper
- Dashlane → LastPass
- Dashlane → Microsoft Edge
- Dashlane → Mozilla Firefox
- Dashlane → NordPass
- Dashlane → Proton Pass
- Dashlane → RoboForm
- Dashlane → Safari
Other ways into 1Password
- Apple Passwords → 1Password
- Bitwarden → 1Password
- Enpass → 1Password
- Google Chrome → 1Password
- KeePassXC → 1Password
- Keeper → 1Password
- LastPass → 1Password
- Microsoft Edge → 1Password
- Mozilla Firefox → 1Password
- NordPass → 1Password
- Proton Pass → 1Password
- RoboForm → 1Password
- Safari → 1Password
Moving the other way? 1Password → Dashlane · All 210 converters