LEAVING DASHLANE
Move out of Dashlane without losing attachments, passkeys, or shared logins.
Dashlane gives you two ways out: a direct transfer with Credential Exchange, or a ZIP of unencrypted CSV files. Either way, check what did not come across before you close the Dashlane account.
START WITH THE SETUP
Before you export anything
- 01
Create the new password-manager account, save its recovery details, and test one low-risk login on each device you use.
- 02
List what a CSV export leaves out, according to Dashlane: attachments on Secure Notes, passkeys, and logins someone shared with you using the Can autofill permission. Two-step codes are not exported as working codes either.
- 03
If you have Dashlane through work, your plan admin decides whether you can export from your Business Space. Dashlane suggests moving personal items to your Personal Space first.
- 04
Keep Dashlane paid up and working until the move is finished. You may need to look something up after the import.
WORK THROUGH THE CHANGE
Transfer or export once, then fill the gaps
- 1
Choose your route. On iOS 26 or macOS 26 or later, in the Dashlane app (not the browser extension), go to Settings → General → Export data → Export data to another app, then choose 1Password or Bitwarden. Dashlane says this Credential Exchange route can move passwords, passkeys, and verification codes. On Android 10 or later, Dashlane lists 1Password, Bitwarden, and Google Password Manager as destinations.
- 2
For a file export, use the Dashlane web app: open the Vault menu → Settings → Export data → Export to CSV. You get a ZIP of separate CSV files for logins (credentials), IDs, payment details, personal information, and Secure Notes. Dashlane says CSV files are not encrypted and others can read them, so save the ZIP to a private local folder outside cloud sync. 1Password also suggests pausing backup software until you delete it.
- 3
Do not choose a DASH file for this move. Dashlane says DASH files are encrypted but can only be imported into Dashlane, not into another password manager.
- 4
Import once, using the destination’s Dashlane option. In Bitwarden, choose Tools → Import and the Dashlane format, and import each CSV file separately. On 1Password.com, choose your name → Import data → Dashlane and upload the ZIP. In the Proton Pass browser extension, go to Settings → Import and choose Dashlane (zip); you do not need to unzip it. Bitwarden warns that importing the same file twice creates duplicates.
- 5
Fill the gaps: add Secure Note attachments by hand, create a new passkey for any account whose passkey did not arrive, set up two-step verification again for accounts whose codes lived in Dashlane, and ask anyone who shared a login with you to share it again in the new manager.
- 6
Sign in to your most important accounts from the new manager on each device. Then delete the ZIP and every CSV file you unpacked from it, empty the Recycle Bin or Trash, and check that no synced or backup copy remains.
- 7
Only then cancel Dashlane or close the account, and remove the Dashlane browser extension so two managers do not both try to fill the same login.
PUT IT INTO PRACTICE
Three things a Dashlane move can miss
Check these items specifically. A matching item count is not proof that everything came across.
- A scanned passport attached to a Secure Note
- Dashlane says Secure Note attachments cannot be exported to CSV, and it lists attachments among the items the Android direct transfer does not export. Download the file from Dashlane and add it to the new vault yourself—or decide it no longer needs to be stored there.
- A login a colleague shared with “Can autofill”
- Dashlane’s credentials file leaves out items shared with you using the Can autofill permission. Ask the person who shared it to share it again from the new manager, and keep Dashlane until they do.
- A two-step code generated inside Dashlane
- Dashlane says it cannot export these codes to a CSV file. The credentials file has an otpSecret column with the setup code, which Dashlane says you can use to move the code; treat that column as sensitive as a password. Our suggestion: set two-step verification up again from the account’s own security settings instead.
Direct transfer or CSV file?
Dashlane describes Credential Exchange as a way to move data without an unencrypted file, and it is the only route Dashlane documents for moving passkeys. It needs iOS 26 or macOS 26 or later in the Dashlane app, or Android 10 or later. Dashlane does not transfer collections this way, and on Android it lists custom fields, attachments, SSH keys, and API keys as not exported. Proton Pass is not among the destinations Dashlane lists, so for Proton Pass use the ZIP file.
Moving from another manager instead? Use the LastPass guide or the Apple Passwords guide. Read Dashlane’s Credential Exchange steps; source checked September 21, 2026.
A GOOD REASON TO WAIT
Stop and fix it before continuing if
- You cannot sign in to your primary email from the new password manager on a second device.
- The ZIP or any CSV file ended up in cloud sync, an email, or a shared folder.
- An account still depends on a passkey or two-step code that only Dashlane holds.
When to use the provider’s instructions
This is a planning guide, not security, legal, or account-recovery advice. Use the provider’s current documentation and your organisation’s policy where they apply.
YOUR NEXT STEP
Not sure where to move yet?
Compare published prices first, then list the devices and people who need access. The pricing pages do not rank products; they show what each plan costs and includes.