Migrate from LastPass to LitePassword (small-team guide)
Export your LastPass vault, paste secrets into matching LitePassword types, invite your team, revoke LastPass. End-to-end in ~15 minutes for a 10-person team.
Step-by-step migration from LastPass
- 01
Export your LastPass vault
Sign into LastPass web vault → Account Settings → Advanced → Export. Pick "LastPass CSV File". Save it locally — do not email it, do not put it in Slack. This file contains every password in plaintext.
- 02
Create your LitePassword account
Go to app.litepassword.com/sign-up. Use your work email. Pick a strong master password (16+ characters, mixed case, numbers). When the recovery key appears, copy it into a fireproof note app (1Password, a physical envelope, a safe).
- 03
Create your vault structure
Decide on shared vault names first — "Production credentials", "Marketing tools", "Client — Acme". Create empty shared vaults. The private vault is auto-created.
- 04
Import secrets by type
Open the LastPass CSV in a spreadsheet. Group rows by what they are — logins (most rows), credit cards (look for cardholder fields), notes (no URL, just text). For each group, create a new secret in the matching LitePassword type and paste the values. Do not paste the whole CSV; the types are different and the import quality is better one-by-one.
- 05
Invite your team
Users page → Invite user. Pick role: Admin for co-founders, Manager for full team members, View only for contractors. They receive an email, sign up, set their own master password, generate their own recovery key.
- 06
Grant per-vault access
For each invited user, open Manage Vault Access. Toggle on only the shared vaults they need. Engineering team gets Production credentials, marketing gets Marketing tools, etc. Cryptographically enforced — they cannot decrypt vaults they were not granted.
- 07
Delete the CSV export
The CSV from step 1 is now redundant and dangerous to keep. Securely delete it (Mac: srm -v, Windows: SDelete, Linux: shred). Empty trash.
- 08
Cancel LastPass
Once everyone is unlocking from LitePassword, log into LastPass admin and cancel the subscription. Delete the LastPass organization. Each member should also delete their personal LastPass account and uninstall the browser extension.
Why a manual import is the cleaner path
Bulk CSV imports tend to look efficient and produce a mess. LastPass categorizes secrets loosely (everything’s “Site” or “Secure Note”); LitePassword has five specific types with different default fields (login, password, card, note, custom). Importing one-by-one means each secret lands in the right type with the right field structure — which is what makes the daily-use experience clean later.
For a 10-person team with ~80 shared secrets, the entire migration is ~15 minutes including invites and per-vault access setup. Slower than a bulk import would look, but you don’t end up cleaning up mis-categorized entries for the next month.
Things to double-check after migration
- Every login has the right Username + Password fields populated. A common error is missing the username for sites that LastPass autodetected but didn’t store cleanly.
- Credit cards have CVV, expiry, and cardholder name. These often end up as plain notes in LastPass.
- Recovery codes for 2FA-enabled accounts are in Secure notes.
- Each team member has signed up and unlocked at least one shared vault — confirms the key wrapping flow worked.
Cancel LastPass cleanly
Don’t just stop using it. Actively cancel:
- Log into LastPass admin.
- Cancel the team subscription (this stops billing).
- Delete the organization (this removes shared folders from your account).
- Have each member delete their personal account and uninstall the browser extension.
Leaving a dormant LastPass account around means an attacker who eventually phishes the master password can still see (now-stale) credentials. Close it cleanly.
Done migrating from LastPass? Cancel their seat.
LitePassword bills only for active users. No long-term commitment, no cancellation fee.
Considering other tools instead of LastPass?
Common questions about leaving LastPass
Does LitePassword import LastPass CSV directly?
Not in v1 — we deliberately recommend manual per-secret entry. CSV imports tend to dump everything into a single bucket; manual entry lets you sort by type (login vs password vs note vs custom) and gives you cleaner default fields. A 10-person team typically migrates in ~15 minutes this way.
My team has been on LastPass for years — will I lose data?
No. Your LastPass account remains active until you cancel. Run both in parallel for a few days, copy secrets over, verify a few sample credentials in LitePassword, then revoke LastPass.
What about LastPass Secure Notes?
They map cleanly to LitePassword Secure Notes type. For long notes (recovery procedures, runbooks), keep formatting in mind — LastPass plain text translates fine.
What about TOTP / 2FA codes stored in LastPass Authenticator?
LitePassword does not generate TOTP codes today. Move those to a dedicated authenticator app (Google Authenticator, Authy, 1Password). Store backup recovery codes as Secure notes in LitePassword.
My LastPass account had emergency access set up. Does LitePassword have this?
No. Emergency access in LastPass was a vendor-mediated grant. LitePassword does not have a vendor-mediated path (zero-knowledge by design). The equivalent is: physically share your recovery key with a trusted person (sealed envelope, safety deposit box).
Can I import only partially and keep LastPass as backup?
Yes — but only briefly. Running both means two recovery models to maintain, which adds attack surface. Migrate fully within a week.
Stop sharing passwords in Slack messages.
Create your account in under a minute. Pick a master password. We'll generate your recovery key for you.