Home › Converters › KeePassXC to Dashlane
KeePassXC to Dashlane converter
KeePassXC and Dashlane both use CSV, but KeePassXC writes 10 columns; Dashlane expects 9 in a different order — so Dashlane rejects a raw KeePassXC export or silently files everything into the wrong fields. Drop your export below and get back a file Dashlane accepts.
Convert your KeePassXC 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 10 column names match (title, username, password), and they're in a different order — enough for Dashlane to accept the file and then put your passwords in the wrong fields.
| KeePassXC column | Dashlane column | What happens |
|---|---|---|
Title | title | Renamed and repositioned |
Username | username | Renamed and repositioned |
Password | password | Renamed and repositioned |
URL | url | Renamed and repositioned |
TOTP | otpSecret | Renamed and repositioned |
Notes | note | Renamed and repositioned |
Group | category | Renamed and repositioned |
What carries over
| Field | KeePassXC | Dashlane | 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 | 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 KeePassXC separately before you close the account — this is the one thing people lose permanently. |
Step 1 — Export from KeePassXC
- Open your database in KeePassXC and unlock it.
- Choose Database → Export → CSV file.
- Pick a location and save.
Watch out for
- KeePassXC CSV export writes attachments and entry history nowhere — if you need those, keep the .kdbx file as your archive.
- Group paths use a forward slash and include the database root, e.g. Passwords/Work. Strip or keep the root depending on where you want entries to land.
Step 2 — Convert it
Drop the file onto the converter above. It parses KeePassXC's layout, maps each field onto the universal record, then writes Dashlane'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 Dashlane 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 Dashlane
- Open the Dashlane web app and go to My account → Settings → Import data.
- Choose "Other" / CSV file.
- Upload the converted file and confirm the mapping.
Official instructions: Dashlane import 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 4 — Verify and clean up
- Open ten entries in Dashlane at random and check them against KeePassXC.
- Generate a 2FA code for one account in Dashlane and confirm it matches KeePassXC. A TOTP secret that imported wrong fails silently until you're locked out.
- Sign in to one real site using Dashlane 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 KeePassXC account — and change any password you suspect was exposed while the plaintext file existed.
Questions
Why won't Dashlane import my KeePassXC file directly?
Only 4 of 10 column names match (title, username, password), and they're in a different order — enough for Dashlane to accept the file and then put your passwords in the wrong fields. The converter rewrites the file into Dashlane'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 KeePassXC to Dashlane?
Dashlane can't natively store: file attachments. Rather than drop that data, the converter writes it into the notes field where Dashlane has one, so you can move it back by hand. Keep your KeePassXC 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 KeePassXC exported the secrets. KeePassXC and Dashlane 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 KeePassXC encrypted?
No. A KeePassXC 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 KeePassXC's export?
KeePassXC CSV export writes attachments and entry history nowhere — if you need those, keep the .kdbx file as your archive.
Anything unusual about importing into Dashlane?
Dashlane exports a ZIP containing several CSVs (credentials, payments, ids, securenotes). Logins live in credentials.csv — that is the file to convert.
Related converters
Other routes out of KeePassXC
- KeePassXC → 1Password
- KeePassXC → Apple Passwords
- KeePassXC → Bitwarden
- KeePassXC → Enpass
- KeePassXC → Google Chrome
- KeePassXC → Keeper
- KeePassXC → LastPass
- KeePassXC → Microsoft Edge
- KeePassXC → Mozilla Firefox
- KeePassXC → NordPass
- KeePassXC → Proton Pass
- KeePassXC → RoboForm
- KeePassXC → Safari
Other ways into Dashlane
- 1Password → Dashlane
- Apple Passwords → Dashlane
- Bitwarden → Dashlane
- Enpass → Dashlane
- Google Chrome → Dashlane
- Keeper → Dashlane
- LastPass → Dashlane
- Microsoft Edge → Dashlane
- Mozilla Firefox → Dashlane
- NordPass → Dashlane
- Proton Pass → Dashlane
- RoboForm → Dashlane
- Safari → Dashlane
Moving the other way? Dashlane → KeePassXC · All 210 converters