How to Move Passkeys Between Password Managers Safely

16 min read

,
Android phone showing Google Password Manager's import passwords and passkeys screen, illustrating how to move passkeys between password managers

You can move passkeys between supported password managers without setting them up again on every website. On iOS 26 and later, start in the manager you are leaving. On Android, start in the one you are moving to. Both apps must support Credential Exchange. If they do not, create a new passkey on each site, test it, and only then remove the old one.

Until recently, a passkey was effectively stuck in whichever manager created it. Passwords could always leave in a CSV file, but passkeys usually could not, so switching managers meant visiting every account and enrolling again. That is changing quickly, but unevenly. Desktop apps mostly still cannot export passkeys, Microsoft documents no passkey export for Windows, and some managers have not adopted the new standard yet. Version requirements also differ by app, so check them before you start.

How Credential Exchange lets you move passkeys between password managers

Credential Exchange is a pair of specifications from the FIDO Alliance, the industry group behind passkeys. The editors work at 1Password, Bitwarden and Dashlane, with contributors from Google, NordPass, Okta and Devolutions. There are two parts:

Bitwarden illustration of a computer monitor showing a fingerprint passkey mark beside a cloud, representing portable passkeys
Image: Bitwarden
  • Credential Exchange Format (CXF) defines what the data looks like: logins with usernames and passwords, passkeys, one-time password (TOTP) codes, notes, cards, Wi-Fi details, SSH keys and more. Version 1.0 is a FIDO Proposed Standard, with the current revision dated 9 March 2026.
  • Credential Exchange Protocol (CXP) defines how one app hands that data to another securely, using encryption keys agreed between the two apps so nothing travels in the clear. It is still a Working Draft, dated 3 October 2024.

In practice, the operating system does the plumbing. Apple added transfer support in iOS, iPadOS, macOS and visionOS 26, with developer tools called ASCredentialExportManager and ASCredentialImportManager. Google built the same idea into Android through Google Play services, and its developer documentation describes passing data in the FIDO format between apps on the same device.

Apple describes the result as a user-initiated transfer that goes directly between participating apps and is protected by local authentication such as Face ID. No export file is written to storage, which removes the biggest risk of the old CSV method. Apple also notes that websites and apps do not need to change anything, and that existing passkeys remain unchanged and keep working.

One technical limit matters. CXF says passkeys that use a non-zero signature counter must be left out of an export, and the exporting app should tell you which ones were skipped. Bitwarden notes that its own passkeys created before version 2024.3.1 used such a counter. Any passkey that gets skipped this way has to be recreated on the site.

Which password managers can move passkeys today

Support depends on both the app and the platform. Google says its Android transfer works in Google Password Manager, 1Password, Bitwarden and Dashlane, with more partners to follow. Dashlane lists Apple Passwords, 1Password and Bitwarden as participating managers on iOS, and 1Password, Bitwarden and Google Password Manager on Android.

ManagerMove passkeys directly?Where it worksFallback if not
Apple PasswordsYes, export and importiOS, iPadOS, macOS and visionOS 26 or laterRecreate on each site (Apple’s CSV export is for passwords)
Google Password ManagerYes, export and importAndroid (Google says Android 8 or later)Recreate on each site; CSV download covers passwords
1PasswordYes, export and importiOS and iPadOS 26 or later; Android 14 or laterDesktop exports do not include passkeys; recreate
BitwardenYes, export and importiOS 26 or later; Android 10 or later for export, Android 14 or later for import.json export includes passkeys
DashlaneYes, export and importiOS 26 or macOS 26 or later in the Dashlane app; Android 10 or laterNot available in the browser extension; recreate
Proton PassNo Credential Exchange support documentedFile export from the browser extension, web app and Windows appRecreate unless your new app imports passkeys from Proton’s file
Samsung PassNo passkey transfer documentedNot listed by Google or Dashlane as a participantRecreate on each site
Windows Hello and Microsoft Password ManagerNo export documentedWindows 11 can use 1Password, Bitwarden and other passkey pluginsRecreate in the new manager

Two patterns stand out. First, the move happens on mobile. 1Password says plainly that you can only export passkeys in 1Password for iOS and Android at this time. Second, the starting point differs by platform: on Apple devices you begin in the app you are leaving, while on Android you begin in the app you are joining.

Before you start

  1. Update everything. Install the latest version of both password managers, and update the phone or tablet to the version listed in the table. Dashlane also asks for the latest Google Play services on Android.
  2. Put both apps on the same device. The transfer runs between two apps installed on one phone or tablet. Sign in to the destination app first.
  3. Stay online. Dashlane notes that passkeys need an internet connection to transfer, even though other item types do not.
  4. Set a screen lock. Google Password Manager needs a PIN, pattern or fingerprint before it will import or export.
  5. Have your recovery details ready. Google warns you may need a recovery key when importing passkeys, or your old device’s screen lock or Google Password Manager PIN when exporting from a new device.
  6. Keep the old manager for now. Do not delete your old vault or cancel the subscription until you have checked the move, as covered further down.

It also helps to take a quick count of how many passkeys and logins the old manager holds. Most transfer screens show an item count, and comparing the two numbers is the fastest way to spot a gap.

How to move passkeys out of Apple Passwords on iPhone or iPad

Apple’s transfer works in iOS and iPadOS 26 or later. The destination app must also support Credential Exchange. Bitwarden, Dashlane and 1Password all document this path from the Passwords app:

  1. Open the Passwords app.
  2. Tap the Options button (the three dots in the upper-right corner).
  3. Tap Export Data to Another App.
  4. Select the passwords and passkeys you want to move, or select all, then tap Continue.
  5. On the Export Passwords screen, tap Continue.
  6. On Select a Destination, choose the new app, such as 1Password, Bitwarden or Dashlane, and tap Continue.
  7. Tap Continue in “AppName”. The destination app opens.
  8. Confirm the import in the new app. Bitwarden asks you to tap Continue, while 1Password shows a Start import button.

Apple Passwords also stores Wi-Fi network passwords, but Dashlane notes that Apple does not transfer Wi-Fi items through Credential Exchange. Only logins, passkeys and verification codes come across.

Apple says the same transfer works on macOS 26. The step-by-step paths that password-manager makers publish are for iPhone and iPad, so use one of those if your Mac does not list your new app as a destination.

Apple’s older export route is a CSV file. On iPhone it lives in Settings > Apps > Safari > Export, and on a Mac in the Passwords app under File > Export All Passwords to File. Apple describes it as a password export and warns that the file is not encrypted. Use it only for apps that do not support Credential Exchange.

How to move passkeys into Apple Passwords

To bring passkeys into Apple Passwords, start the export in the other app on your iPhone or iPad and pick Passwords as the destination. Dashlane’s steps show the pattern:

  1. In the Dashlane iPhone app, tap Settings in the bottom menu. On iPad or Mac, select the gear icon above the left menu.
  2. Select General, then Export data, then Export data to another app. You may be asked for your Master Password.
  3. Select the items to move and tap Continue.
  4. On the Export Passwords screen, tap Continue.
  5. On Select a Destination, choose Passwords and tap Continue.
  6. Tap Continue in Passwords, then Done on the Import Finished screen.

From 1Password or Bitwarden, follow their own export steps and choose Passwords as the destination.

How to move passkeys with 1Password

1Password supports Credential Exchange in both directions on iOS and iPadOS 26 or later, and on Android 14 or later. Its desktop apps can export only to its own .1pux format or CSV, and neither includes passkeys.

Export from 1Password on iPhone or iPad

  1. Open and unlock 1Password.
  2. Tap the icon for your account or collection at the top left, then tap Settings.
  3. Tap Advanced, then Start Export.
  4. Enter your account name when asked and tap Approve export.
  5. Tap Continue on the Export Passwords screen, choose the destination on Select a Destination, then follow the prompts in the new app.

Import into 1Password on Android

  1. Install the old password manager on the same phone and make sure you are signed in.
  2. Open and unlock 1Password.
  3. Tap New Item, then Migrate data into 1Password. You may need to scroll down to see it.
  4. Choose the password manager you are leaving, then tap Start import and follow the onscreen instructions.

To leave 1Password on Android, do the reverse: start the import in the new app and pick 1Password as the source. 1Password’s support page says that if you export from its desktop apps, you should also create new passkeys on each site and save them somewhere else, such as your device’s built-in passkey manager.

How to move passkeys with Bitwarden

Bitwarden supports Credential Exchange on iOS 26 or later and Android 10 or later. Its import guide lists Android 14 or later for bringing data into Bitwarden, and says importing Dashlane data this way is not supported on Android yet.

Export from Bitwarden on iPhone or iPad

  1. Tap the Settings icon.
  2. Tap Vault, then Export vault.
  3. Choose Export vault to another app. The other option, Export vault to a file, creates a file instead.
  4. Review the list on the Export items screen and tap Export items.
  5. Tap Continue, pick the destination on Select a Destination, then tap Continue in “AppName”.

Import into Bitwarden on Android

  1. Open the Bitwarden app.
  2. Tap Settings, then Vault, then Import items.
  3. Tap Import from another app.
  4. Select the password manager that holds your data and tap Continue.
  5. Choose which items to import and complete any sign-in or confirmation the other app asks for.
Bitwarden Export vault screen on iPhone and Android with the password-protected .json file format selected
Image: Bitwarden

Bitwarden is unusual in that its file exports can include passkeys. Only the .json formats carry them, and Bitwarden recommends the password-protected .json option. The plain .json and .csv files are unencrypted. Bitwarden also warns that passkeys created before version 2024.3.1 include a counter, so exports of passkeys that old should not be relied on as long-term backups.

Bitwarden web vault Import screen with My vault selected and file format and Choose File fields ready for an import
Image: Bitwarden

How to move passkeys with Dashlane

Dashlane supports Credential Exchange on iOS 26 or macOS 26 or later in its iPhone, iPad and Mac apps, but not in its browser extension. On Android it needs Android 10 or later. Business users should note that Dashlane admins decide whether the feature is available on professional plans.

Export from Dashlane on Apple devices

  1. On iPhone, tap Settings in the bottom menu. On iPad or Mac, select the gear icon above the left menu.
  2. Select General, then Export data, then Export data to another app.
  3. Select the items to move and tap Continue. If anything fails, Dashlane shows a list you can download and check.
  4. Tap Continue on the Export Passwords screen, choose the destination and tap Continue in “AppName”.

Import into Dashlane on Android

  1. In the Dashlane app, open Vault from the side menu.
  2. Select Logins in the top bar, then Add new.
  3. Tap Import multiple items, then From another password manager.
  4. Tap Start import, pick the manager you are leaving and sign in to it.
  5. Select the items you want and tap Import, then Done.

Some items change shape along the way. Coming from Apple devices, bank details land in Dashlane as Secure Notes. On Android, Dashlane says custom fields and file attachments are not included, and Android removes most duplicate items during the import.

How to move passkeys with Google Password Manager on Android

Google rolled out its transfer for Android in September 2026. Google says it works on Android 8 or later, though the other apps in the move may set a higher minimum, as the table shows.

Import into Google Password Manager

  1. Open Google Password Manager on your Android phone.
  2. Tap Settings, then Import passwords and passkeys.
  3. Verify your identity with your screen lock, then tap Next.
  4. Choose the password manager you want to import from.
  5. Sign in to the other password manager. If you are importing passkeys, you may be asked for a recovery key.
  6. Approve the export in the other app, then tap Done.
Google Password Manager on Android importing passwords and passkeys from another password manager in four steps
Image: Google

Google says passwords that already exist in Google Password Manager are not added twice, and the import may fail if the other app has no data or the data is damaged.

Export from Google Password Manager to another app

  1. Open the password manager you are moving to.
  2. Choose its option to import from another app.
  3. Select the Google Account whose passwords and passkeys you want to move, and verify with your screen lock.
  4. When Google Password Manager opens, tap Export.

Google also offers a CSV download in Chrome on Android under More > Settings > Autofill and passwords > Google Password Manager > Settings > Export passwords & passkeys > Download file. Google describes that file as a download of your passwords, and it is not encrypted, so use the app-to-app route whenever you can.

Windows, Microsoft Password Manager, Proton Pass and Samsung Pass

Not every manager has joined the transfer yet. For these, plan on recreating passkeys.

Windows Hello and Microsoft Password Manager. Microsoft documents how to view and delete passkeys saved on a Windows device, but not how to export them. Since the November 2025 Windows 11 security update, Windows supports third-party passkey managers as plugins, starting with 1Password and Bitwarden, so a new manager can save passkeys directly when Windows asks.

To move away from Windows Hello passkeys, install your new manager, then open Settings > Accounts > Passkeys > Advanced options and turn on the new passkey service. Create a fresh passkey on each site and save it to the new manager. Once it works, go back to Settings > Accounts > Passkeys, select the three-dot menu next to the old passkey and choose Delete passkey.

Windows 11 Save your passkey prompt offering to save a new passkey to 1Password as the passkey manager
Image: Microsoft

Proton Pass. Proton’s export lives in the browser extension, the web app and the Windows app, under the settings menu’s Export tab, and not in the mobile apps. You can choose a ZIP with a PGP-encrypted JSON file, an unencrypted ZIP or a CSV. Proton says Pass can export passkeys, but its help pages do not list Credential Exchange support. Unless your new manager’s import guide says it brings passkeys over from a Proton file, recreate them.

Samsung Pass. Samsung does not document a passkey transfer, and Samsung Pass is not among the apps Google and Dashlane name as participants. Recreate passkeys in your new manager.

What to do when there is no import path

If either side of your move does not support Credential Exchange, or a passkey was skipped, you will not lose access. A passkey is just one way to sign in, and most sites let you register more than one. Recreating is slow but safe if you do it in this order:

  1. Set the new manager as your default. Pick it in your phone’s AutoFill or passwords settings so new passkeys are saved there. On Windows 11, enable it under Settings > Accounts > Passkeys > Advanced options.
  2. Sign in to the site with the old passkey. Use the existing credential one last time.
  3. Open the site’s security settings. Look for a page called Passkeys, Security keys or Sign-in methods. Some sites now publish a standard link that password managers can open for you. Apple showed this in iOS 26, with an add passkey button in the Passwords app that jumps straight to the site’s enrolment page.
  4. Add a new passkey. When the save prompt appears, check that it names your new manager, not the old one.
  5. Sign out and test. Sign back in using only the new passkey, ideally on a second device as well.
  6. Delete the old passkey from the site. On the site’s passkey list, remove the entry that belongs to the old manager.
  7. Delete it from the old manager last. Only once the site no longer lists it.

Start with the accounts that matter most: your email, Apple Account, Google Account, Microsoft account, bank and anything you use to recover other accounts. Microsoft’s own advice for its account security page applies everywhere: add the new sign-in method before you remove the old one.

How to check the move worked

  1. Compare the counts. Note the item count on the transfer screen, then check the new manager’s passkey list. Dashlane and other apps show a list of anything that did not transfer.
  2. Spot-check by signing in. Pick five or ten important accounts, sign out and sign back in with the passkey from the new manager. Watch the prompt to make sure it is not quietly using the old manager or a device passkey.
  3. Check one-time codes. If you moved TOTP codes too, confirm a couple of them match what the site expects before you rely on them.
  4. Look for skipped passkeys. Anything with a counter, or anything the old app flagged, needs to be recreated with the steps above.
  5. Switch AutoFill off for the old app. This stops new passkeys being saved to the wrong place.
  6. Wait before you delete. Use the new manager for a week or two. Then delete the old vault and any export files, and cancel the old subscription.

If you are also changing phones, back up your phone before you start, so a failed transfer cannot cost you anything stored only on the device.

Security tradeoffs

Credential Exchange is the safest way to move passkeys today, but it is not risk-free.

  • No file, but full trust. The app-to-app transfer avoids the unencrypted file that CSV exports leave behind. In return, you are handing every secret to the destination app in one go. Google’s help page says to make sure you trust the third-party manager before importing into it.
  • Files are the weak spot. Apple’s CSV, 1Password’s .1pux and CSV, and Bitwarden’s plain .json and .csv are all unencrypted. 1Password says not to email export files or store them online, and to delete them when you are done. If you must use a file, choose an encrypted format such as Bitwarden’s password-protected .json or Proton’s PGP-encrypted ZIP.
  • Two copies for a while. After a transfer, the same passkey exists in both apps. That is useful during testing, but an old vault you forget about is still a target. Delete it once you are happy.
  • Not everything moves. Apple leaves out Wi-Fi items, Dashlane on Android leaves out custom fields and attachments, and counter-based passkeys are skipped. Check before you assume the new vault is complete.
  • Standards still settling. The protocol is still a draft, and each company sets its own version minimums. If a transfer fails, update both apps and the OS first.

There is one more benefit. If you are leaving a browser’s built-in manager, perhaps because the Arc browser is shutting down, moving to a dedicated manager that works across platforms can save you from doing this again later.

FAQ

Can I export passkeys to a file?

Usually not. Apple and Google describe their file exports as password exports, and 1Password’s desktop exports leave out passkeys. Bitwarden is an exception: its .json exports include passkeys, and it recommends the password-protected version. Proton says Pass can export passkeys in its file formats.

Do I need to update anything on the websites I use?

No. Apple says sites and apps do not need to do anything, because the transfer happens between password managers and the passkeys stay the same.

Why did some of my passkeys not transfer?

The FIDO format excludes passkeys that use a signature counter, and the exporting app should tell you which ones it skipped. Missing internet access, an outdated app or an unsupported item type can also cause gaps. Recreate any missing passkeys on the site.

Can I move passkeys from a desktop app?

Mostly no. 1Password says passkey export works only in its iOS and Android apps, and Dashlane’s transfer does not work in its browser extension. Apple supports the transfer on macOS 26. Use a phone or tablet for the move if you can.

Can I move passkeys between an iPhone and an Android phone?

Not directly. The transfer runs between two apps on the same device. Instead, move everything into a manager that runs on both platforms, such as 1Password, Bitwarden or Dashlane, on one device. Your passkeys will then sync to the other.

What happens to my old passkeys after a transfer?

They stay in the old manager until you remove them. Test each transferred passkey on the website before deleting its old copy. Keep the old manager until you have also moved any passwords or other data you still need.

About the author