Android now provides a direct route for moving credentials between participating password managers. The useful question is whether your source, destination and installed software support the exact journey you want to make. A general statement that both managers support passkeys does not answer that question.
What changed
In its 10 September announcement, Google described a transfer experience that avoids a downloaded export file. You begin an import in the destination app; Android identifies available sources, and the source app asks you to review and authorize the transfer. Google named Google Password Manager, 1Password, Bitwarden and Dashlane as participating apps. That launch list is not a guarantee for every transfer direction.
Check the destination's specific requirements
Bitwarden's current import guide specifies Android 14 or later for its Android CXP import flow. It also explicitly excludes importing from Dashlane through CXP on Android at the time of this review. Use that route-specific restriction when assessing Dashlane → Bitwarden, even if a broader announcement lists both brands.
Do not replace an app requirement with a platform headline. Record the operating system, both app versions, transfer direction and documentation date. If two official pages disagree, mark the result uncertain and seek clarification before relying on it.
Prepare a small, reversible check
- Confirm that you can open both managers and access an independent recovery method for the account you will test.
- Choose a low-stakes account with a passkey and another working sign-in route. Avoid using your only administrator or recovery account as the first experiment.
- Follow the destination's current import instructions, then review the credential types and items offered by the source app.
- Return to the actual service and complete a fresh sign-in using the destination manager. An item appearing in a vault is not, by itself, a completed sign-in test.
If the source does not appear
Recheck both vendors' current instructions and software requirements. Do not upload a vault export to a third-party checker to diagnose the problem. If no documented transfer route is available, check whether the service lets you register an additional passkey in the destination manager. Keep the existing working route until the replacement has been confirmed.
Passkey Atlas helps you identify the documented route and its limitations. It does not open your vault, transfer credentials or establish that an untested combination works.