Password Manager Migration: Bitwarden, 1Password, Dashlane

Moving to a different password manager is not simply an import job. Your new vault must work on the devices you use, preserve the information you need and leave you a way back in if a phone or account becomes unavailable. Bitwarden, 1Password and Dashlane document different recovery and export routes; a feature checklist alone will not reveal those differences.

This guide is for individuals and families planning a move, not for administering an employer’s credentials. Start with invented entries, identify the gaps and keep your existing account available. Do not export real secrets merely to compare products.

Correction, October 4, 2026: This article replaces the earlier comparison. Unsupported hands-on testing claims, performance figures, product rankings and deployment/API advice have been removed. The guide is source-based analysis of official documentation checked on this date, not a hands-on review or security audit. It contains no hands-on comparison or security certification. AI assistance was used for research and writing.

A laptop and phone beside two generic vaults, sample transfer cards and a separate recovery envelope.
AI-generated concept illustration of password-manager migration and recovery planning; not a product screenshot, tested workflow or security guarantee.

1. Check device fit before choosing a plan

Write down your actual setup: desktop operating system, everyday browser, phone, tablet and any shared computer. Add the tasks you need to complete on each device, such as filling a login in a mobile app or finding a note while travelling. A supported operating system does not mean every feature works identically everywhere.

For example, 1Password’s system requirements list separate requirements for the apps, passkeys and data transfer. Its current mobile export support is not interchangeable with its desktop export. Dashlane’s supported-device guidance similarly distinguishes stable supported versions from beta environments. Check these pages against your own versions, rather than assuming an older household device can participate.

Read the current Bitwarden plans, 1Password personal plans and Dashlane personal plans for the intended account type. Note the currency, annual charge, renewal terms, number of people and features each person receives. This guide does not freeze prices or assume that a trial includes every paid feature.

Self-hosting is a separate operating decision, not a shortcut to a better score. Bitwarden’s self-host FAQ distinguishes unofficial servers such as Vaultwarden and limits compatibility/support assurances. Our self-hosted migration and recovery guide explains the maintenance and recovery questions to resolve before choosing that route. Do not put real credentials into an improvised installation as a product trial.

2. Map recovery dependencies before moving anything

Write a recovery map without recording secret values in it: which email account, authentication device, saved recovery material or trusted person would be needed if your usual phone were unavailable? Identify circular dependencies. An email password stored only in a locked vault may be difficult to retrieve when that same inbox is needed to recover the vault.

The three products do not use the word “recovery” to mean the same thing. Bitwarden’s forgotten-master-password guidance says the company cannot retrieve or reset your master password; available alternatives depend on what was arranged beforehand. Its two-step login recovery code addresses a missing second factor and still requires the master password. It is not a substitute for a forgotten master password.

1Password’s recovery-code documentation describes a personal/family recovery route that also needs access to the account’s email. Team and business recovery follows a different route. Dashlane’s recovery options also depend on advance setup and account type; an account recovery key requires identity verification through email or an authenticator.

Use each vendor’s current instructions to plan where recovery material belongs outside the account it unlocks, with protection against both theft and loss. Confirm that the relevant email and authentication route remain accessible. Do not trigger recovery on a real account just to rehearse this checklist: it can change account credentials, sessions or authentication settings. A written dependency review is the starting point, not proof of successful recovery.

3. Distinguish migration files from recoverable backups

A downloadable file is not automatically encrypted, complete or readable by another manager. Before any real move, identify the source export, destination import and item types you rely on. Include custom fields, notes, attachments, shared items and passkeys, not just a count of saved logins.

Bitwarden’s export guide distinguishes plaintext JSON/CSV from encrypted exports. An account-restricted encrypted export is tied to its originating account and encryption key; a password-protected export has a different restore scope. Individual exports also do not automatically include organization-owned items. Do not assume the same email address on a different server makes an account-restricted file portable.

1Password’s export instructions warn that desktop 1PUX and CSV files contain unencrypted data. CSV carries a limited set of fields. A filename associated with a password manager does not make its contents private, and a CSV that imports without an error may still omit information you expected.

Dashlane’s CSV export documentation identifies exclusions, including passkeys and Secure Note attachments. Its encrypted DASH format is for restoration into Dashlane, not a general import format for competing products. It also has item and app limitations.

If a later, deliberate migration requires a plaintext file, follow the vendors’ current handling instructions on a private device. Do not send it through email, upload it to an online spreadsheet or include it in a support screenshot. Consider synced folders, shared-device access and backup copies before creating it. Remove temporary files when no longer needed, but do not assume ordinary deletion erases every synchronized or backed-up copy. The pilot below uses dummy data to investigate the route first.

4. Run a small pilot using invented entries

Use a separate, empty evaluation account at both the source and destination, containing only invented data. Do not add sample entries to your real vault or connect an employer’s account or shared vault to the pilot: some export routes include an entire account rather than selected items. Before any transfer, verify the documented export scope contains no real credentials, personal records or shared items. If you cannot isolate the data, stop and use the documentation-only checklist instead.

In those isolated accounts, create a short set of clearly labelled sample entries that contain no usable credentials: a login with a long invented password, a second login for a different address, a note with line breaks, a custom field and a harmless text attachment if your chosen plan supports it. These are proposed checks, not a test TechPulse has performed.

Record what each entry should contain. Use the documented transfer route for those dummy entries only, then inspect the destination. Look for lost fields, duplicate records, changed formatting and missing attachments. Matching item totals cannot establish that the contents match.

Next, examine how the destination feels on your actual devices. Can you search for the right entry, distinguish two similar accounts, unlock the vault and find its lock control? If checking autofill, use only an authorized dummy account or a login form you control. Check the address and account selected before filling; do not treat a successful demonstration as protection against every phishing page.

Keep a simple worksheet with columns for “needed,” “documented support,” “dummy check” and “unresolved.” Write down the app/browser version alongside observations. An unresolved requirement should stay visible rather than becoming a guessed pass. You are looking for obstacles that matter to your household, not calculating a universal winner from a few examples.

5. Plan passkeys and two-factor access separately

Do not expect password export to carry every sign-in method. A vault may contain the login password, an authenticator secret, a passkey and a note about a recovery code, but those items can follow different transfer rules. Keep an inventory of which services depend on which methods, without copying their secret values into the worksheet.

The checked 1Password export guidance limits passkey export to its supported mobile credential-exchange routes; a desktop export is not a passkey transfer. Dashlane’s transfer overview describes credential exchange for participating apps and supported platforms, alongside CSV and DASH exports. That does not establish that every source/destination combination transfers all your items.

Before a real migration, consult both managers’ current instructions and the sign-in service’s own account guidance. Confirm what alternate sign-in or recovery path exists if transfer is unavailable. Do not remove an existing passkey, authentication device or fallback simply because an import finished. Changing an important account’s authentication should be a separate, deliberate step, not part of this dummy-data evaluation.

Check the password manager’s own second factor as well as the factors for accounts stored inside it. These are different recovery problems. A working vault on an already-unlocked phone does not prove you can authenticate from another device after losing that phone.

6. Treat family membership and shared access as different things

Decide which entries genuinely need sharing and which should remain personal. Joining a household subscription is not the same action as handing over every item. Dashlane’s Friends & Family guidance, for example, describes independent member accounts and optional sharing. Read the equivalent rules for whichever plan you select rather than assuming one family model applies everywhere.

For a proposed shared item, write down who owns it, who needs access and who would maintain it if the organizer were unavailable. Use only a made-up note to investigate sharing controls initially. Confirm what the recipient can see or do and whether each person’s own device works. Do not use a real banking or primary-email credential as the household demonstration.

Business credentials are a different boundary. An employer may restrict exports or personal storage; the vendor export guides document some organizational limitations. Follow the employer’s policy and contact its administrator before moving anything. A personal family plan, a shared login and a production secrets system are not interchangeable just because each can store text.

7. Keep the old route available until the gaps are resolved

Use the pilot to make a decision: continue planning, choose another route or stay with the current manager. There is no obligation to migrate because you started a trial. Convenience, recovery dependencies and household participation can matter more than a longer feature list.

Before considering a real transfer, check that:

  • Every essential device and browser has a documented, usable route.
  • Recovery dependencies and access to the relevant email/authenticator are understood.
  • The selected transfer format supports the required item types, with gaps recorded.
  • Dummy entries retain their expected contents, not merely the same item count.
  • Passkey, two-factor and sharing exceptions have a separate plan.
  • Temporary-file handling and any subscription deadlines are understood.

If you later proceed, follow the current source and destination instructions, keep the existing account and access methods available, and reconcile information before relying on the new vault. Do not delete the old account or cancel access as a shortcut to finishing. Keep track of which vault receives changes during the transition so you do not mistake two diverging copies for a backup.

The useful question is not “Which manager wins?” It is “Can my household use this one and retain a documented way to recover and move again?” This guide supplies questions and checks, not assurance that a migration, account recovery or security outcome will succeed.

MD Rafikul Islam

Written by

MD Rafikul Islam is a software developer and editor of TechPulse. He writes about developer tools, hardware, AI, and practical technology decisions. Some articles are based on cited documentation and analysis rather than hands-on testing; readers should check each article for sources and testing disclosures. Corrections are welcome at rony.yf25@gmail.com.

✍️ Leave a Comment

Your email address will not be published. Required fields are marked *