When to switch password managers — and when staying is the better call

Every major security incident involving a password manager is followed by a wave of 'switch immediately' recommendations. Every major pricing change produces a similar wave. Not all of these recommendations are wrong — but they are applied uniformly to situations that require different analysis. Whether switching is the right decision depends on what specifically changed, what you would be switching to, and what the migration cost entails.

The 2022 LastPass breach is the clearest recent case. For some users, switching was clearly the right call: those with weak master passwords, those for whom URL metadata privacy was important, those evaluating password managers fresh and finding the breach history disqualifying. For others — those with strong master passwords, already embedded in enterprise LastPass workflows, who had read the breach disclosures and assessed their risk — staying was defensible. The monolithic recommendation didn't serve either group.

Switching has costs that are often understated: export/import complexity, potential data loss, reconfiguring 2FA, learning a new interface, and the risk of misconfigured settings in the new environment. These costs should be weighed against the specific benefit being sought.

The assumption 'switching is free because import is supported' underestimates migration complexity. The CSV or JSON export from your current manager may not capture all fields — custom fields, TOTP seeds, file attachments, and tags frequently don't transfer cleanly. TOTP seeds require separate reconfiguration in the new manager. Shared vault credentials require coordinated migration with other users. A migration that takes five minutes for a simple individual vault can take hours for a complex multi-user setup.

A second assumption is that newer is better — that switching to a recently launched product with a clean breach history is always an upgrade. Breach history is one dimension; product maturity is another. A newer product has had less time to discover and fix edge cases in autofill, recovery flows, platform compatibility, and enterprise integrations. Proton Pass, launched in 2023, has a clean breach record and a strong architecture; it also has fewer edge cases documented, fewer community workarounds published, and less real-world deployment experience than Bitwarden's decade-old codebase.

A third assumption is that switching resolves the exposure from a previous breach. Migrating to Bitwarden does not erase the URL metadata that LastPass's 2022 breach exposed. Switching forward changes your future security posture. It does not undo past exposure. The migration decision should be based on the forward-looking assessment — which provider architecture is right for your next decade — not on the belief that switching retroactively addresses historical incidents.

Good reasons to switch: your current provider has been breached and the breach revealed architectural weaknesses you cannot accept; pricing changes have made the value proposition non-competitive; you need features the current provider doesn't offer; the current provider has made business decisions (acquisition, policy changes) that change your trust assessment; or you are evaluating managers for the first time and your current choice was made without adequate research.

Poor reasons to switch: panic following a breach announcement without reading the actual disclosure; a single negative review from a source that reviewed a different version; feature envy for one specific feature while your current manager serves all other needs well; or following a generic recommendation without personalising the analysis to your actual usage pattern and threat model.

The migration itself should be approached methodically: export from the old manager first (before cancellation); import to the new manager; run both simultaneously for 1-2 weeks to confirm completeness; then deactivate the old account. Delete the export file after confirming the import. The plaintext export is the most sensitive file created in the process.

This guide discusses individual user migration decisions. Team and enterprise migrations involve additional considerations: coordinating shared vault access, updating SSO configurations, planning offboarding from the old system, and communicating changes to users. Enterprise migrations warrant dedicated planning that goes beyond the scope of a personal migration guide.