To transfer passkeys between compatible password managers on Android without creating an unencrypted comma-separated values (CSV) file, start in the new password manager. Choose its option to import or migrate from another app, then follow the Android prompts to select and unlock the old provider, approve the transfer and check the imported items. Keep the old vault intact until you have tested the new one.
Android’s credential-transfer system can move passwords and passkeys directly between participating apps on the same device. It uses the FIDO Credential Exchange Format, a standard for transferring credential data, and does not require you to download a CSV file as part of the app-to-app process. Compatibility still varies by app, Android version and transfer direction, so a provider may support importing from another app without supporting every possible export pairing.
Check compatibility and prepare both vaults
Check the requirements in the destination password manager before you begin. For example, 1Password and Bitwarden require Android 14 or later for direct Credential Exchange imports. Dashlane supports Credential Exchange on Android 10 or later when Google Play services are up to date. The source and destination apps must both support the transfer method.
Before starting, complete this safety checklist:
- Update Android, Google Play services and both password manager apps.
- Install both providers on the same Android device and sign in to each one.
- Let the old vault finish synchronizing so recent password and passkey changes are present.
- Set a device screen lock, such as a PIN, pattern, password or fingerprint.
- Make sure you can unlock the old manager and have its account-recovery information available.
- Use a reliable internet connection. Dashlane notes that passkeys require an internet connection for transfer.
- Keep recovery codes and another sign-in method available for important email, financial and work accounts.
The destination app controls how the process begins. Current paths include:
| Destination | Where to start |
|---|---|
| Google Password Manager | Settings, then Import passwords and passkeys |
| 1Password | New Item, then Migrate data into 1Password |
| Bitwarden | Settings, Vault, Import items, then Import from another app |
| Dashlane | Vault, Logins, Add new, Import multiple items, then From another password manager |
Menu names can change with app updates. If the app offers both a file import and an option such as Import from another app, Migrate data or Start import, choose the app-to-app option for a passkey transfer.
Transfer passwords and passkeys step by step
- Open and unlock the destination manager. Start with the manager that will receive the credentials rather than looking for a conventional export in the old app.
- Select its direct import option. Android then shows compatible credential providers installed on the device.
- Verify your identity. You may need to confirm your device screen lock and then sign in to or unlock the old password manager.
- Choose the source provider. Select the old manager and, where the app asks, the account or vault that contains the credentials.
- Review the credentials and approve the transfer. The source provider controls the final authorization. Confirm that the receiving app shown on screen is the manager you intended to use.
- Wait for the completion message. Keep the apps open and note any skipped items or error messages. Do not immediately repeat the import, as this can create duplicates in some managers.
Google Password Manager does not add passwords it recognizes as already saved. Dashlane says its Android import automatically removes most duplicate items, although some duplicates can remain. Bitwarden warns that its ordinary file imports do not check for duplicates, so review the new vault before attempting another transfer.
Do not assume every item in a vault will move. Passwords and passkeys are central to this transfer method, but support for verification codes, cards, identities, secure notes, custom fields, attachments, Secure Shell keys, folders and shared collections differs by provider. For example, Dashlane says that Android Credential Exchange transfers do not include bank-account information, custom text fields or file attachments.
Set the new provider and test it carefully
Importing items does not necessarily make the destination your preferred password and passkey provider. In Android Settings, search for Passwords, passkeys or autofill. On many current devices, the setting is called Passwords, passkeys and autofill. Choose the new manager as the preferred service and enable it if Android lists it separately as an available provider. Names and locations can differ by phone manufacturer.
Chrome has its own related setting. In Chrome, open Settings, then Autofill services, and select Autofill using another service if you want Chrome to use a third-party manager rather than Google Password Manager. Chrome may ask to restart after the change.
Then test the migration rather than relying only on the completion message:
- Search the new vault for several important accounts and check usernames and website addresses.
- Test password autofill in a browser and an installed app.
- Use transferred passkeys to sign in to a few important services.
- Check accounts with multiple logins, similar names or more than one passkey.
- Confirm that recently changed passwords are correct.
- Review verification codes, notes, attachments and shared items separately if you rely on them.
- Allow the new vault to synchronize, then confirm the credentials appear on another trusted device if that is part of your setup.
Avoid testing by deleting an old passkey from the account first. Use the transferred credential while the old vault and an alternative sign-in or recovery method are still available.
Fix transfer problems without risking access
The import option is missing
Confirm that you are looking in the destination app, not the source. Update the app and Google Play services, confirm that the device meets the app’s Android-version requirement and set a screen lock. If the option is still unavailable, the manager, account type or installed version may not yet support Credential Exchange.
The old manager is not listed
The old app must be installed, signed in and compatible with the requested transfer. Support for a specific pairing can lag behind general support. For example, Bitwarden states that importing Dashlane data through Credential Exchange is not currently supported on Android.
If a pairing is unsupported, do not assume a file-import option will move passkeys. You can wait for direct support, use another verified migration method for passwords where appropriate, or create replacement passkeys at individual accounts while the old vault remains available.
You are asked for a recovery key or old device lock
This can be a legitimate part of authorizing portable passkeys. Google Password Manager notes that, when importing or exporting passkeys on a new device, you may need the old device’s screen lock or your Google Password Manager PIN. Enter recovery information only in the expected Android or password-manager flow. If you cannot complete the prompt, cancel the transfer and recover access to the old provider before trying again.
Only some credentials transferred
Check whether the missing items belong to another account, vault or shared collection. Make sure both apps are unlocked and connected, then try again only for the missing items if the app offers item selection. Unsupported item types, restricted credentials and organization policies can require manual handling.
Keep the old password manager installed and its vault unchanged until every important password and passkey has been tested. Remove old credentials, cancel a subscription or uninstall the previous app only after sign-in, autofill, synchronization and account recovery all work from the new provider.
