Moving From Another Password Manager: An Import Guide

Coming from 1Password, Bitwarden, LastPass, or a spreadsheet? Here's a low-stress migration plan.

Don't move everything

Personal accounts should stay in your personal manager. Only move what your household actually shares — usually 15-30 entries out of a much larger vault.

Export from your old tool

Every major password manager supports a CSV or JSON export. Do it on a trusted machine; delete the file when the import finishes.

Map your fields

WarpDesk expects: service, username, password, optional TOTP, optional URL. Most exports match cleanly. Anything odd goes in notes.

Import in batches

Do 5-10 entries at a time. That way you catch mismatches early instead of after 200 rows.

Attach TOTPs during import

If your old tool exported the otpauth URI, paste it into the TOTP field. This is the moment to fix any 2FA gaps.

Verify each entry

Sign into each service once from WarpDesk after importing. This catches password rotations you'd missed.

Delete from the old vault

Once every shared entry lives in WarpDesk, delete it from your personal vault. Two sources of truth are worse than one.

Handle notes and attachments

Notes migrate as plain text. WarpDesk doesn't currently support file attachments — if you had them, save them elsewhere.

A worked example

A user with 240 entries in 1Password imports 22 shared entries to WarpDesk. Total time: 45 minutes, mostly spent verifying each login. The other 218 stay in 1Password.

Handling breach-flagged passwords

If your old tool flagged some entries as breached, rotate them during import. New WarpDesk entry = new random password, generated at add time.

Wrap it up

The migration is deliberately incremental. Move the shared stuff, verify it works, delete the source. Don't try to do it in one heroic afternoon.