A password-manager migration involves an especially sensitive temporary file. Plan the destination, transfer only through documented tools, verify the result, and remove unnecessary exported copies.
One topic. 6 useful perspectives.
6 sections
A password manager holds credentials for many services, so moving its contents deserves more care than moving ordinary bookmarks. Begin by deciding why you are changing tools and which features you need to preserve: passwords, passkeys, secure notes, shared items or attachments. Different products support different export formats, and not every type of item necessarily transfers through the same process.
Use a strong, unique master password where the product requires one, and enable its supported account protection. Store recovery information in a secure place that will remain accessible if the primary device fails. Review which devices are signed in and whether synchronization is enabled. A successful import into one local installation is different from a completed, recoverable setup across the devices you intend to use.
Some exports are unencrypted text files, commonly CSV or JSON. Others may be protected in a provider-specific format. The filename alone does not tell you which protection applies. Read the export warning carefully and assume that an unencrypted export can be read by anyone who gains access to that file. Avoid placing it in a shared download folder or a directory that automatically synchronizes somewhere you did not intend.
Use the destination's documented import process and inspect the result before making the switch permanent. Check several item types, not only the first entry in the list. Confirm that account names, usernames, website addresses, notes and any required custom fields arrived as expected. Watch for duplicate entries and for passwords associated with the wrong hostname.
During a transition, two managers may both offer autofill. This can make it unclear which copy was updated after a password change. Choose which tool will handle normal filling and disable the redundant integration when you are ready. Keep any remaining source vault access only for a deliberate verification period, rather than leaving two conflicting systems active indefinitely.
Once the migration is verified, remove unnecessary export files using the operating system's normal deletion process and review synchronized folders or backups where a copy may have been created. Be realistic about deletion: it does not guarantee immediate erasure from every backup, storage medium or previously shared location. If the export was exposed to another person or an untrusted service, deleting your local copy does not undo that exposure.
No matching sections. Try a different phrase or choose All sections.
Take a moment to check your understanding. This is a reflection aid, not a certification or account check.
Progress is saved only in this browser. No account is created.