Some links on this page are affiliate links. If you buy through them, we may earn a commission at no extra cost to you.
· By IMRAN HOSSAIN
Quick answer: Export your Keeper vault to CSV or JSON, clean and map the CSV columns to Bitwarden’s import format, import into Bitwarden using the web or desktop app, then reconfigure TOTP and attachments that did not transfer automatically. Test autofill and sharing, and use the Bitwarden CLI for bulk automation or attachments. After migrating, if autofill or browser extension issues occur, consult Fix Autofill & Browser Extension Issues for Keeper and Bitwarden.
- Key takeaways: export from Keeper in CSV, clean and map fields to Bitwarden, preserve TOTP via a totp column or manual steps, use the Bitwarden ‘bw’ CLI for bulk moves, and run post-import checks for autofill and sharing.
- Use a staged migration: sample batch first, then full import, to avoid locking yourself out of accounts.
- Expect to manually move some attachments and any custom record types, and plan for team re-provisioning if you use shared Keeper folders.
What is the quickest way to migrate from Keeper to Bitwarden?
The quickest practical route is export, clean, import, verify in that order. Export a CSV from Keeper, convert it to Bitwarden CSV layout, import into Bitwarden via the web or desktop app, then test a small set before full sync.
Start by exporting from Keeper on a desktop browser or the Keeper desktop app because mobile exports are restricted. Use CSV when you want to edit fields, or JSON when you have complex item types and a script to translate them. After importing into Bitwarden, allow time for the desktop, browser extension, and mobile apps to sync. If you manage teams or shared folders in Keeper, read the section below about mapping shared Keeper folders to Bitwarden Organizations, because there is no one to one automatic conversion. For an overview that compares both products before you move, read the Bitwarden vs Keeper guide, which helps you decide whether migration is the right move for your situation.
How do I export my vault from Keeper?
Export from Keeper using the Vault export tool to CSV or JSON from the web or desktop app, choosing CSV when you plan to edit records. CSV is easiest for mapping to Bitwarden.
Open Keeper Web Vault or Keeper Desktop, go to Settings, then Export or Vault Options, and choose Export to CSV or JSON. CSV is human readable and editable in Excel, Numbers, or Google Sheets, but it strips binary attachments, which Keeper exports separately as files in an attachments folder when using JSON or the desktop export. If your Keeper data includes attachments or custom record types like Secure Notes with file blobs, export JSON or use Keeper Commander to extract attachments. Keep the exported file on a local encrypted drive and delete any cloud copies after the migration. Back up your Keeper export but do not attach it to email or cloud storage without additional encryption because CSVs are plain text secrets.
How do I prepare and clean the Keeper CSV for Bitwarden import?
Convert Keeper columns to Bitwarden’s import schema, ensure a totp column if you want to migrate TOTP codes, and remove CSV artifacts before importing.
Open the Keeper CSV in a spreadsheet and map the key columns to Bitwarden names: folder, name or title, login_uri or url, login_username or username, login_password or password, notes, totp for one time codes, and favorite. Bitwarden expects certain column names when importing CSV; use ‘login_uri’ and ‘login_username’ exactly if possible. Remove extra commas, merged cells, HTML markup in notes, and line breaks that break CSV rows. If you have many records, use a small Python script with pandas to normalize fields, strip whitespace, and detect duplicates. For example, create a ‘totp’ column with the raw base32 secret if Keeper exported TOTP as a secret. Do not paste raw TOTP URIs into the password field; put them into the dedicated totp column. Save a sanitized copy and keep your original encrypted export until the migration is complete.
How do I import to Bitwarden and preserve TOTP codes?
Import the cleaned CSV in Bitwarden desktop or web, and preserve TOTP only when the CSV includes a totp column formatted for Bitwarden. Otherwise, reconfigure TOTP manually for each login.
Open Bitwarden web vault or desktop app, go to Tools or File, select Import Data, choose the appropriate import source or CSV type, then upload your cleaned CSV. Bitwarden recognizes a ‘totp’ column when present; paste the base32 TOTP secret or an otpauth URI. If your Keeper export did not include TOTP secrets, you must re-add TOTP per account using each site’s two factor settings, or use Keeper Commander to extract TOTP secrets if Keeper stored them as secrets in JSON. After import, verify TOTP codes by generating a code in Bitwarden and using it to sign in at the target site. If an imported TOTP fails, reconfigure that account. Note that Bitwarden supports in‑vault TOTP generation, and for enterprise setups you can enable policy controls after migration; see Bitwarden setup guidance for admin steps.
Can I move attachments and files from Keeper to Bitwarden?
Attachments do not reliably transfer in a CSV import; export attachments from Keeper separately, then upload them to Bitwarden using the API or desktop app for each item.
Keeper JSON or desktop export can produce a bundle of files or a folder containing attachments. Bitwarden’s CSV importer will not attach binary files, so plan a second phase where you attach files to Bitwarden records. For a manual approach, download the file bundle from Keeper, open the corresponding Bitwarden item, and add the file under Attachments. For bulk operations, use the Bitwarden API or the Bitwarden ‘bw’ CLI to upload attachments programmatically and associate them with item IDs. Keep in mind Bitwarden instance attachment size limits and storage quotas; if you self host, check your server limits in the self hosting guide. When attachments are sensitive, re-encrypt them locally before transfer and delete the temporary copies from intermediate storage.
Which hidden trade-offs matter when switching from Keeper to Bitwarden?
Expect hidden costs around team re-provisioning, audit log differences, admin training, and potential API scripting time. Quantify these before migrating because they often exceed the time to move individual passwords.
Decision framework: first, list required capabilities such as SSO, SCIM provisioning, audit logging, attachments sizes, and offline access. Second, compare policies and admin workflows between Keeper and Bitwarden. Third, estimate hours for scripting and manual fixes. For example, Bitwarden Teams costs $3 per user per month, according to the Bitwarden pricing page (2026), so a 10 person team costs roughly $360 per year for Teams, which is useful for budgeting the organization after migration. Hidden trade-offs include different audit log retention, role models, and the need to recreate shared folder rules as Bitwarden Organizations and Collections. Account for help desk time to reset TOTP or fix broken autofill after the switch, because those human costs are commonly underestimated.
What scripts and tools can automate a bulk migration?
Use the Bitwarden ‘bw’ CLI and Keeper Commander or Keeper’s export JSON, plus small Python scripts, to convert and push items and attachments at scale. Test scripts on a sample subset first.
Workflow example: export Keeper JSON, parse it with a Python script to produce Bitwarden CSV rows or direct API payloads, then authenticate with the Bitwarden CLI ‘bw login’ and ‘bw encode’ to add items via ‘bw create item’ or using the /items API. For attachments, upload via the Bitwarden attachments endpoint and link by item id. Community tools such as Keeper Commander can help extract Keeper artifacts, and the Bitwarden CLI is standard for programmatic imports. Avoid exposing secrets in plaintext scripts by using environment variables and cleaning temporary files. Always run an import in a test organization or a separate Bitwarden account first, then proceed after validation. If you prefer not to script, import via the desktop or web UI for small vaults.
How do I map Keeper shared folders and team features to Bitwarden Organizations?
Keeper shared folders map conceptually to Bitwarden Organizations and Collections, but you must recreate membership and permissions manually or by using SCIM provisioning if both sides support it.
If you use Keeper for teams, decide whether each shared folder becomes a Bitwarden Organization, or whether you group multiple Keeper folders into Collections inside one Organization. Bitwarden supports Collections inside Organizations, and SCIM provisioning is available on certain Bitwarden business plans. Export Keeper group membership and recreate users in Bitwarden using the admin console or SCIM connector. For enterprise setups, map Keeper roles to Bitwarden collections and policies. Keep an audit trail of which user was assigned to which shared folder, because permissions do not import automatically. If you rely on single sign on, configure Bitwarden SSO and test provisioning before disabling Keeper team access to reduce downtime for users.
What post-import checks and troubleshooting steps should I run?
After import, verify autofill, logins, TOTP generation, attachments, shared access, and browser extension behavior, and run a duplicate detection pass. Resolve any broken records before decommissioning Keeper.
Checklist: 1) Open 10 high value accounts and log in using Bitwarden autofill. 2) Verify TOTP codes are accepted. 3) Confirm attachments open correctly. 4) Check sharing by asking a colleague to open a shared item. 5) Test mobile autofill on Android and iOS. 6) Run Bitwarden’s duplicate detection to merge or delete duplicates. Common fixes: fix malformed URLs so autofill matches, add missing ‘login_username’ fields, and re-add TOTP on sites that block imported secrets. If browser extension autofill fails, clear extension cache or reinstall. For account recovery or suspicious activity after migration, follow recovery steps similar to other manager incidents and consult account security guides.
Which one fits you? (Which profile should migrate and why?)
Choose based on your usage pattern, team size, budget, and desire for open source hosting. Each profile below has a clear recommendation and reason.
- Beginner, single user: Bitwarden Free or Bitwarden Premium if you want in‑vault TOTP and emergency access; low cost and easy setup. See the beginner setup in the Bitwarden setup guide.
- Tight budget, family: Bitwarden Families is cost efficient for up to six users, and migration is straightforward using CSV. Compare family pricing on the pricing comparison page.
- Small team or agency: Bitwarden Teams is a good fit when you need collections and simple provisioning; migrate shared Keeper folders into Collections manually. Read the Teams scaling advice on business comparison.
- Advanced, self hosting or custom policies: Self host Bitwarden and use SCIM and SSO; follow the self-host Bitwarden guide for detailed steps.
Who should NOT migrate: organizations that depend on Keeper exclusive features like certain privileged session monitoring or specific compliance integrations unless you have a plan to replace those capabilities. If you rely on a Keeper-only feature, evaluate replacement tools listed on the Keeper vs Bitwarden comparison.
What are the most common mistakes and how do I avoid them?
Common mistakes include importing unclean CSVs, missing TOTP secrets, losing attachments, and failing to recreate shared permissions. Avoid these by testing, backing up, and staging the migration.
Specific fixes: 1) Always test with 20 items, verify logins and TOTP. 2) Preserve original Keeper export encrypted until the migration is confirmed. 3) Use exact Bitwarden CSV column names to prevent dropped fields. 4) Script attachment uploads rather than manual copy paste for many files. 5) Communicate change to users to expect password prompts while they enable new autofill. If you run into account lockouts, follow password reset workflows and consult account recovery best practices similar to the guidance in our account compromise recovery article.
Practical migration checklist
Follow these ordered steps to migrate with minimal downtime and risk; execute the list on a workstation with secure backups and encrypted storage.
- Back up Keeper: export encrypted JSON and CSV, store locally encrypted.
- Sanitize CSV: normalize columns, add a totp column if available, remove broken rows.
- Test import: import 10 to 20 items into a fresh Bitwarden account or test Organization.
- Verify: test autofill, TOTP, and attachments for test items.
- Plan team steps: map shared folders to Bitwarden Organizations and Collections, configure SSO or SCIM if needed.
- Full import: import the sanitized CSV into production Bitwarden account or Organization.
- Post checks: duplicate detection, extension tests, mobile sync, and user communications.
- Decommission Keeper: disable new logins, retain encrypted export for 30 days, then delete securely.
| Product | Price range | Best for | Key strengths | Main limits |
|---|---|---|---|---|
| Bitwarden | Free to paid teams and enterprise | Open source and flexible hosting | Open source code, self hosting, CLI tools, strong community | Some advanced features require paid plans and admin work for provisioning |
| Keeper | Consumer to business pricing | Polished consumer apps and enterprise features | Feature rich apps, secure file attachments, polished UI | Proprietary, and migration of certain record types can be manual |
How much time will migration take, and what are the costs?
Time varies: a single user with under 200 items can finish in 1 to 3 hours, while a 50 person team with shared folders and attachments may need several days for planning and automation. Budget for admin time and potential paid plans.
Estimate effort as: 1 hour for export and CSV cleanup for solo users, plus 1 to 3 hours for verification and fixing broken autofill; for teams, add provisioning time and scripting hours. If you buy a Bitwarden Teams plan at $3 per user per month, a 10 person team costs about $360 per year, which helps you plan licensing spend. Hidden costs include help desk support during the first week as users adjust, and potential hour costs to reconfigure TOTP on sites that block imports.
FAQ
Below are common voice-assistant style questions and short answers about migrating from Keeper to Bitwarden.
- Is Keeper better than Bitwarden? Both have strengths; Keeper has polished consumer features, Bitwarden offers open source code and flexible hosting. Your choice depends on features like SSO, audit logging, and budget.
- What is the Bitwarden controversy? The main concerns historically involve pricing changes and governance around open source work. Check the vendor transparency pages and community channels for current details before you migrate.
- How do I export passwords out of Keeper? Export via Keeper Web Vault or desktop app to CSV or JSON from Settings or Vault Options, then secure the export locally. Use JSON for attachments and CSV for easy editing.
- Does NASA use Bitwarden? There is no definitive public statement confirming broad NASA use of Bitwarden; large organizations evaluate tools against procurement rules, so verify via public procurement records if needed.
- How do I migrate from Keeper to Bitwarden on Android? Perform the export on desktop, import into Bitwarden web or desktop, then sync your Bitwarden mobile app; direct mobile to mobile export is not recommended.
- How do I preserve TOTP when migrating? Preserve TOTP by including a totp column with the base32 secret in your CSV, or reconfigure TOTP manually per site if secrets are not exportable.
Summary: migrating from Keeper to Bitwarden is a multi stage process of export, CSV cleanup, import, and verification. Use the Bitwarden CLI for bulk or attachment work, recreate shared permissions as Organizations and Collections, and plan time for manual TOTP and attachment fixes. If you need setup or hosting options, follow the Bitwarden setup and self hosting guides for post‑import hardening.
Internal resources to help your next steps: see a step guide for migrating to Bitwarden at migrate to Bitwarden, the beginner setup at Bitwarden setup guide, and advanced self hosting details at self host Bitwarden. For security best practices, read security best practices. If you want comparisons for alternatives, check Bitwarden vs Dashlane, Bitwarden vs 1Password, and Bitwarden vs LastPass. For pricing context, consult the pricing comparison. If you migrate other password tools, see the LastPass to 1Password migration example at LastPass to 1Password migration. For team focused business features, read the business scale comparison at business comparison. To evaluate Keeper vs Bitwarden further, read Keeper vs Bitwarden. For a full Bitwarden review, see Bitwarden review. For migration pattern examples unrelated to passwords, see our other migration guides like Anytype migration and OneNote to Notion.
External references used for vendor features and pricing: Bitwarden pricing page, Bitwarden documentation for importing, and Keeper support documentation for exporting were consulted for format and policy details.