Changing password managers is less like moving a stack of game cases to a new shelf and more like carrying a master key through a crowded room. The actual migration can be straightforward: export saved logins from the old manager, import them into the new one, verify every important detail, then remove the temporary export and retire the old account. The important catch is that the most portable version of a password vault is often an unencrypted file.

That makes the order of operations matter. A password manager is intended to reduce the burden of remembering complex credentials across many sites and apps. But people may eventually want different features, or simply decide that another service better fits their needs. Switching should not mean abandoning strong, unique passwords or manually resetting every account. It does mean treating the move as a focused security task rather than a file-management errand to leave half-finished until later.

Prepare the destination before exporting anything

Install the new password manager and create its account before making an export from the old one. This is a practical safeguard: the less time a readable credential list exists, the less opportunity there is for it to be exposed, misplaced or forgotten.

Do the migration on one device and plan to finish it in one sitting. Most importantly, do not upload the exported login list to cloud storage. The exported file exists only to bridge the two managers; it should not become a backup or a document kept for convenience.

This is also a useful moment to distinguish the tools involved. A password manager stores and fills account credentials, typically usernames and passwords. An authenticator app is associated with authentication codes and serves a different purpose. The two are not interchangeable categories, even if both can be part of a broader account-security routine. The migration process described here concerns the credentials stored by the password manager, plus the separate question of passkeys.

A pre-export checklist

  • Download the new manager and finish creating its account.
  • Keep the old manager installed and accessible until validation is complete.
  • Use a single device for the transfer.
  • Set aside time to import, inspect and test the result immediately.
  • Do not place the exported file in cloud storage.

The key principle is simple: the old vault remains the reference copy until the new vault has been checked. Deleting first and hoping the import worked is an avoidable way to turn a routine change into a recovery problem.

Export passwords: why CSV is the usual bridge

In the current password manager, look for an Export command. Its exact location varies, but it is commonly found in Settings, Preferences or a File menu. The service may offer more than one export format; CSV is the standard format for moving password lists between managers.

CSV means “comma-separated values.” In this context, it is a simple structured text file containing entries from the vault. Its broad compatibility is why it is useful for imports. Its simplicity is also the danger: the export can be readable without the protections people normally associate with opening their password manager.

That risk does not mean exports should never be used. It means the file should be handled as highly sensitive material for the brief period it is needed. Keep the process local to the device, import promptly, and make deletion part of the migration rather than an optional cleanup step for some future date.

Import, then inspect the new vault

Open the new manager and find its Import option. Upload the CSV file created from the old manager. Once the import finishes, do not treat the presence of a long list as proof that the move was successful. Inspect the imported entries and compare the new list against the old one.

The review should establish three things:

  1. Completeness: the saved logins made the move.
  2. Accuracy: usernames, passwords and other imported information appear correct.
  3. Cleanliness: the import did not create duplicate entries.

This stage is where a migration stops being merely successful on paper and becomes dependable in use. A CSV may be a common standard, but different managers can organize data in different ways. Reviewing the results is therefore more useful than assuming that a completed import screen means every field arrived exactly as expected.

For people who play across PC, console companion apps and mobile services, a password vault can hold credentials for a surprising number of game-adjacent accounts alongside everyday logins. That makes verification especially important: an account that is not needed this afternoon can still be the one that causes trouble weeks later when a purchase, social login or launcher prompt asks for a password that did not migrate properly.

Test autofill before dismantling the old setup

After checking the entries, use the new password manager to visit sites with saved credentials and confirm that login information autofills correctly. This is the operational test. It checks not only whether a login exists in the vault, but whether the new manager works with the sites where those credentials are actually used.

Start with accounts that would be most disruptive to lose access to, then test additional sites as practical. The goal is not to manufacture a complicated ritual; it is to ensure that the new setup can do the job that prompted the move in the first place.

Testing before cleanup is a broader digital-maintenance habit. When moving between devices or changing settings, it is sensible to keep the previous working arrangement available until the new one is proven. The same measured approach helps with other setup tasks, including a device connection change such as setting up Apple CarPlay and troubleshooting connection issues: confirm the new configuration works before removing the fallback.

Only then remove the CSV and old manager

Once the import has been reviewed and the new manager has successfully filled real logins, delete the CSV export. Then remove the old password manager account. This is intentionally the last phase, not the first.

There is a tension here worth stating plainly. Leaving the old account and its export around creates unnecessary copies of sensitive data. Removing them too early risks losing a reliable reference while problems are still undiscovered. The solution is not to preserve every version forever; it is to validate the new vault promptly and clean up immediately afterward.

Export, import, compare, test, delete. Treating that sequence as one task keeps the temporary readable file from becoming a permanent liability.

Passkeys are not password rows

Passkeys require separate planning because they cannot simply be placed into a password CSV export. They rely on authentication from the device, which is why they do not travel as ordinary username-and-password entries.

If an automatic passkey transfer is unavailable for the old and new managers, the manual path is likely to mean creating a new passkey at each site and removing the old one. For someone with many passkey-enabled accounts, that can take substantial time. It is also why a password-only CSV migration should never be assumed to cover every way a person signs in.

The FIDO Alliance is working to standardize transfers of passkeys between password managers, and passkey sharing has already been implemented for some providers. Android and iOS support passkey transfers, but compatibility is currently limited to a small group of managers that includes Bitwarden, 1Password and Dashlane. Compatibility matters more than the platform label alone: a phone may support transfer in principle while a particular old-to-new manager pairing still does not qualify.

What supported passkey transfer looks like

On Android, a supported app can begin importing into the new manager while the old manager remains installed and configured. The device should then prompt the user to begin the automatic transfer process.

On iOS, the process begins through the old manager’s dedicated export flow. Because app layouts and wording differ, the precise steps should come from the documentation for the selected password manager.

These transfer routes can also move passwords automatically, avoiding a CSV file. That can reduce the handling of a readable export, but it does not remove the need to check the result. Confirm that passwords and passkeys work in the destination manager before deleting the older setup.

Practical migration plan

  1. Create the account in the new password manager.
  2. Keep the old manager available while the move is underway.
  3. For password lists, export locally in CSV format and do not upload it to cloud storage.
  4. Import the file into the new manager.
  5. Compare entries, checking for missing information, incorrect details and duplicates.
  6. Use the new manager on real sites to verify autofill and successful sign-in.
  7. Check passkeys separately; use a supported platform-and-manager transfer path where available, or recreate them manually where it is not.
  8. After validation, delete the CSV and delete the old manager account.

The migration may be routine, but the data is not. A compact plan, a single-device workflow and careful verification make it possible to change password managers without trading convenience for an unnecessary exposure of account credentials.