A password export needs a more careful destination than an ordinary bookmark file. Before exporting, choose the receiving password manager and read its supported import process. Keep the existing working password store until the new one has been checked.

Prepare the receiving side

Confirm the intended user and account on both devices. Separate company credentials from personal credentials according to the organisation’s rules. A successful import into the wrong account creates a new problem even when every row transfers correctly.

In Chrome, open Passwords and autofill, Google Password Manager, then Settings. Google provides Download file under Export passwords. Choose a private local destination you control, and follow the authentication prompts shown by the device.

Treat the exported file as readable credentials. Do not attach it to an ordinary support email, upload it to a shared project folder or paste its rows into chat. Check whether the chosen folder is automatically synced or backed up before using it as temporary storage.

Check the migration before cleaning up

Import through the receiving manager’s documented function. Google’s own desktop import expects CSV; another manager may have its own field mapping and duplicate handling. Read the import result and investigate failures before attempting another whole-file import.

Check several accounts by site and username, then test an authorised sign-in through the new manager. Include one account with multiple usernames if that is part of your real workflow. Do not assume a password CSV transfers passkeys, second-factor recovery methods or existing signed-in browser sessions.

After confirming the needed passwords are available, remove the temporary export using the operating system’s file-deletion process and check any copies created during transfer. Deleting one local file does not recall a copy already shared elsewhere. If a credential export was exposed, handle that as a credential incident rather than relying on tidying the Downloads folder. Retire the old store only after the overall account-access handover is complete.

Sources: Chrome documentation.