· By IMRAN HOSSAIN
Quick answer: You can move from LastPass to 1Password by exporting your LastPass vault as a CSV or using LastPass export, then importing that file into 1Password Desktop or the web importer, reconfiguring two factor authentication and reassigning shared items; test thoroughly before deleting LastPass. For strategy and a broader comparison, see LastPass vs 1Password.
- Key takeaways: export LastPass CSV, import into 1Password, reassign shared vaults, migrate 2FA codes manually, then securely delete LastPass.
- Create a rollback plan and validate every login after import, especially for shared items and team accounts.
- Keep a temporary offline backup and an Emergency Kit for 1Password until you confirm full cutover.
Who should switch from LastPass to 1Password, and which plan fits you?
If you want a password manager that uses a Secret Key plus a master password and strong family or team sharing controls, 1Password is worth switching to. Individuals who value a polished desktop app, families that need shared vaults, and teams that want detailed access controls usually prefer 1Password. If you prefer open source or self hosting, consider alternatives like Bitwarden; see the family and team features comparison for group needs. Decision rule: if you need native shared vaults and a single vendor with cross platform apps, choose 1Password; if you need self hosting or lower cost at scale, choose Bitwarden and read this migrate to Bitwarden guide.
How do you export data from LastPass?
Export your LastPass vault as a CSV or HTML file from the LastPass web vault, then store it offline. Open LastPass in a browser, unlock the vault, go to Account Options, then Export; follow the on‑screen prompt to save a CSV. After export, immediately move the CSV to an encrypted folder or a local machine that is not synced to cloud storage. If you need vendor documentation, consult the official LastPass export help, and if you see HTML export, prefer CSV because 1Password imports CSV fields more predictably. For teams, export each shared folder owner or admin separately and record ownership in a migration plan.
How do you import into 1Password?
Import the LastPass CSV into 1Password using 1Password Desktop or the 1Password web importer. Open 1Password Desktop, choose File, Import, then select LastPass or CSV and follow the mapping prompts. If you prefer detailed docs, check the official 1Password import guide. After import, 1Password will create items, secure notes and tags; verify folder or tag mappings, then enable the 1Password extension in Chrome, Firefox and Safari. For business or Teams, use 1Password Admin tools to move imported items to team vaults and set permissions. Keep your exported CSV until you confirm every critical login works.
How do you preserve folders and shared items when migrating?
Folders and shared metadata do not always map exactly between LastPass shared folders and 1Password shared vaults, you must plan mapping and reassign ownership manually. Export a CSV that includes the LastPass folder column, then during import to 1Password map that column to tags or vaults. For team migrations, create corresponding vaults in 1Password Teams or Business first, then import users’ items into those vaults using the admin import workflow. Communicate changes with your team and use temporary access lists until ownership and permissions are confirmed. If you use group passwords in LastPass, export owner and membership lists to recreate them in 1Password Shared Vaults and note each user’s role for accurate permissioning.
How do you migrate two factor authentication (2FA) and authenticator codes?
Authenticator codes usually cannot be exported automatically, so you must reconfigure two factor authentication manually for each site. For each service, disable 2FA or switch to a new authenticator by scanning a new QR code into 1Password’s built in authenticator, or use Authy or Google Authenticator while you migrate. The recommended sequence is: import passwords, log into each account, go to security settings, replace the old 2FA with a new QR code scanned into 1Password, then confirm recovery codes. For hardware keys like YubiKey and FIDO2, remove the old key and add it under 1Password or service account settings as needed. Keep a spreadsheet of sites and the migration status to avoid lockouts.
What changes for families and teams during migration?
Families and teams need an account structure and an owner who coordinates vault assignments and permissions. Create 1Password Families or 1Password Teams accounts, invite members, then import items into each user’s personal vault and shared vaults for group items. Use the 1Password admin console to move items into Shared Vaults and assign roles. Communicate a migration schedule and expect per‑user authentication resets for 2FA and password sharing. If you need to evaluate alternatives for group use before changing, consult the Bitwarden vs 1Password comparison or the 1Password vs NordPass page for other group features. For universities or enterprise migrations, prepare CSVs of membership and map them to 1Password groups first.
Hidden tradeoffs and a simple decision framework for 2026 migrations
Choose between convenience, control and cost by weighing shared vault fidelity, 2FA migration overhead, and licensing fees. If your primary need is exact preservation of shared folder metadata and group roles, give priority to solutions that support server side imports and admin mapping, otherwise accept manual reassignment. Hidden cost example: time spent reconfiguring 2FA can be 15 to 30 minutes per frequently used account; multiply that by active users. Use this rule: if you have under 5 people, manual reassignments are acceptable; if you have 5 to 50 users, budget an admin day; if over 50 users, plan staged migrations with CSV mapping and a support window. This framework helps you pick between 1Password Families, 1Password Teams or an alternative like Bitwarden when ownership, self hosting or pricing matters; compare costs in the site’s pricing comparison.
How do you troubleshoot common sync problems after import?
Sync problems usually occur because items ended up in the wrong vault, extensions are not signed in, or the CSV mapped fields incorrectly. First confirm you are signed into 1Password Desktop and the browser extension. Check that imported items are in the expected vault and that folders were mapped to tags. For multi device sync, confirm that 1Password sync is active and that devices run supported versions. If a browser extension cannot autofill, clear the browser cache, re-enable the 1Password extension and confirm site matching rules. If problems persist for teams, use 1Password Admin logs to find failed imports and reimport affected CSV rows after correction.
How should you securely decommission your LastPass account?
Do not delete LastPass until you confirm every critical login works in 1Password and 2FA is reconfigured. After verification, export one last CSV for backup, then remove saved passwords from browsers and mobile apps, disable browser extensions, and delete stored vaults from synchronized cloud folders. Finally, follow LastPass account deletion steps in their account settings and revoke any third party sessions or API tokens. Keep records of deletion and the final CSV in an encrypted archive for 90 days and then securely shred it. For a review of LastPass history and security context, consult the LastPass review.
Practical checklist before, during and after migration
Use this checklist to lower risk and avoid lockouts. Back up LastPass and keep the CSV offline, invite 1Password admin(s), create target vaults and groups, import a pilot user’s data and validate, reconfigure 2FA per site, confirm browser and mobile extension behavior, then schedule cutover and decommission LastPass. Keep an Emergency Kit from 1Password, and ask each user to confirm access for at least 48 hours before full deletion. If you reconsider alternatives during planning, see Bitwarden vs LastPass or Dashlane vs 1Password.
- Pre migration: export LastPass CSV, create 1Password account, record admin contacts.
- Pilot: import one account, test 10 critical sites, verify 2FA work.
- Cutover: import everyone, reassign shared vaults, confirm team access.
- Post migration: final backup, remove browser extensions, delete LastPass account.
What are common mistakes and how do you fix them?
Common mistakes are deleting LastPass too early, not preserving folder metadata, and assuming authenticator codes import automatically. Fixes: keep LastPass active until every user verifies credentials, preserve the CSV with folder columns and map them to 1Password tags or vaults, then manually reissue authenticator codes by scanning QR codes into 1Password. Other mistakes include neglecting admin permission mapping for team vaults and skipping extension reinstallation; resolve these by running a staged migration with a clear owner for each shared item. If your team prefers open source workflows, review alternatives like Bitwarden setup guide and this Bitwarden review.
Comparison: Should you pick 1Password, LastPass, Bitwarden or another option?
Use this table to compare at a glance, focusing on price range, best for, strengths and limits.
| Product | Price range | Best for | Key strengths | Main limits |
|---|---|---|---|---|
| 1Password | Subscription plans | Families, teams, polished apps | Secret Key, Shared Vaults, desktop apps | Closed source, subscription |
| LastPass | Subscription plans | Existing users wanting low friction | Browser integration, historically familiar UI | Past security incidents, changing plans |
| Bitwarden | Free plus paid tiers | Self hosting, open source preference | Open source, self hosting, low cost | UI less polished, admin features vary |
| Dashlane / NordPass / RoboForm | Subscription plans | Specific feature needs like VPN or different sharing | Alternate UX and optional features | Migration steps differ, features vary |
Which one fits you? Reader profiles and recommendations
Choose 1Password if you want a managed product with shared vaults and a Secret Key, and choose Bitwarden if you need open source or self hosting. For a solo creator who wants a simple desktop and mobile experience, 1Password Individual is usually best. For a tight budget household, Bitwarden Families or 1Password Families both work; compare the costs on the pricing comparison. For small teams that need role based access, 1Password Teams or Business gives admin controls; for self hosting or the lowest per user cost, consider Bitwarden for businesses and review migration steps in Bitwarden vs 1Password. For up to date subscription and feature cost comparisons in 2026, read our detailed pricing analysis: LastPass vs 1Password pricing explained: Real costs for 2026.
Worked examples with numbers
Example: a solo creator with 350 logins, 20 secure notes and no shared vaults. Export CSV, import to 1Password Desktop, and reconfigure 2FA for about 45 to 90 minutes total. Example: a 6 person household with 1200 combined items and three shared folders. Create a 1Password Families account, import per user, map three shared vaults and plan a 3 to 4 hour migration window. Example: a 25 person team with 6 shared resources should stage migration by team, export membership CSVs, and schedule multiple admin sessions for permissions and 2FA reissue; budget a full business day plus follow up.
FAQ
Below are concise answers to common spoken questions about migrating.
Is it easy to migrate from LastPass to 1Password?
Yes, it is straightforward if you follow a plan: export LastPass CSV, import to 1Password, reconfigure 2FA, and reassign shared vaults. For single users expect under 90 minutes; teams require more planning and verification.
Why are people leaving LastPass?
People often leave LastPass because of historical security incidents, changes to pricing or feature sets, and the desire for different sharing or admin models. Many evaluate alternatives to match their trust, control and cost preferences.
What is the downside of 1Password?
The main downsides are that 1Password is closed source and subscription based, so it is not ideal for users wanting self hosting or open source transparency. Migration of large team permissions requires planning and admin time.
Which is more secure, LastPass or 1Password?
Both LastPass and 1Password use strong encryption, but they take different approaches to key handling and recovery. Check each vendor’s security documentation for current designs, and pick the model that matches your threat model and administrative needs.
How long does migration from LastPass to 1Password take?
For a single user with under 1,000 items, expect 30 to 90 minutes. Families typically need 1 to 3 hours. Teams with shared vaults and custom permissions should budget multiple hours to a few days for staged migration and validation.
Will I lose folders when migrating?
Not necessarily, but folder metadata may not map perfectly. Export the LastPass CSV that includes folder columns, then map folders to 1Password tags or vaults during import, and verify shared items manually to avoid missing links.
Summary: export a safe LastPass CSV, import into 1Password, reconfigure 2FA and shared vaults, validate every critical login and keep a final encrypted backup before deleting LastPass. For broader context on features, pricing and security tradeoffs, review LastPass vs 1Password, and if you want alternatives check Bitwarden vs LastPass or Dashlane vs 1Password.