People switch password managers for many reasons: a price change, consolidating company tools, or frustration with admin features. But when it's time to move, they get stuck on questions like "Which export format carries everything over?" and "How should I handle the exported file?" That's because the exported file lists every password in readable form.
This article is for the people in charge of moving from 1Password, Bitwarden, or similar tools to another password manager. The first half covers migration steps that apply to any product, and the second half covers importing into a Samurai App vault. We go through what each export format leaves out, what data doesn't carry over, and how to clean up the plaintext file.
The steps for 1Password, Bitwarden, and Google are what each company's official help pages said as of November 9, 2026.
Summary: it comes down to the format you choose and cleaning up the plaintext file
- Export in the format that keeps the most fields. For 1Password, that's
.1pux; for Bitwarden, the unencrypted.json. CSV is convenient, but some fields are left out - The exported file isn't encrypted. Both 1Password and Bitwarden say so officially. Don't send it by email, don't put it in the cloud, and delete it as soon as you're done
- Passkeys, attachments, and items in the trash often don't carry over. Check the counts against the import results at the destination, and don't cancel the old service until that's done
- Try with a small number of items before moving everything
- After moving, change passwords, starting with your most important accounts. You can't fully rule out that a copy of the exported file remains somewhere
Why migration takes longer than you'd expect
If you're just moving a list of passwords, it seems like exporting a file and importing it would be the end of it. What actually takes time is these 4 things.
- Each format leaves out different data. 1Password's CSV covers only login and password items, and doesn't include custom fields or two-factor backup codes
- The sharing structure doesn't carry over. How vaults or collections are divided, and who can see what, isn't in the file. You rebuild it at the destination
- Passkeys and attachments are handled separately. If the destination doesn't support them, they stay in the old service
- Everyone at the company has to set things up. Everyone needs to create an account at the destination, switch browser extensions, and remove the old service's extension
General steps for migrating a password manager
1. Take inventory of what you're moving
List the old service's vaults (or collections), the number of items in each, and the members they're shared with. Counting the items that use passkeys or attachments, and the items holding two-factor setup keys, at this point makes checking after the move easier.
2. Choose the export format
| Old service | Format to choose | Notes |
|---|---|---|
| 1Password (8) | .1pux |
Export from the desktop app. CSV covers only login and password items, and custom fields are left out |
| Bitwarden | .json (unencrypted) |
Items in the trash and Sends aren't exported. Organization items aren't included in a personal export |
| Chrome (Google Password Manager) | CSV | Use "Export passwords" in settings |
1Password exports are done in the desktop app on Mac, Windows, or Linux. 1Password 8 lets you choose .1pux or CSV. The phone apps hand data over using a standard called Credential Exchange, which covers iOS and iPadOS 26 and later, and Android 14 and later.
Bitwarden exports are done in the web vault. In the English interface, open "Tools" > "Export", choose your own vault or an organization vault under "Export from", choose the format, and enter your master password or an email verification code. There are two kinds of encrypted .json: one readable only by the account that exported it, and one protected by a password. If the destination isn't Bitwarden, choose the unencrypted .json.
For Chrome, open Google Password Manager, go to "Settings" on the left, and choose "Download file" under "Export passwords".
3. Try with a small number of items
Don't import everything at first. Put just a few items in a test vault and check that IDs, passwords, URLs, notes, and two-factor codes land in the right fields. Also check that titles and notes in Japanese aren't garbled.
4. Import everything and compare counts
Compare the count from step 1 with the number imported. If they don't match, check whether the difference is explained by the kinds of items that didn't carry over (passkeys, attachments, items in the trash, and so on).
5. Delete the plaintext file
Delete the exported file as soon as the migration is done. Both 1Password and Bitwarden advise not sending it by email, not putting it in the cloud, and deleting it once you're finished. When you delete it, also check that no copies remain in these places.
- Your downloads folder and the OS trash
- Cloud folders that sync automatically (if you sync your desktop or documents)
- Email or chat used to pass the file between staff
- External storage such as USB drives
6. Wind down the old service
After confirming that everyone can use the destination, remove the old service's browser extension and cancel it. Before canceling, decide what to do with the passkeys and attachments that had to stay in the old service.
How to move into a Samurai App vault
On Samurai App's "Passwords" screen, you can import files exported from 1Password and Bitwarden, and browser CSV files. The file is read inside the browser and encrypted before it's sent, so it never goes to the server in plaintext.
Formats it can read
| Old service | Files it can read | How tags and folders are handled |
|---|---|---|
| 1Password | .1pux, CSV |
1Password tags become tags as they are. A nested tag like Work/Accounting becomes a single tag spelled exactly that way |
| Bitwarden | Unencrypted .json, CSV |
A folder becomes one tag named after the folder |
| Browser (Chrome and others) | CSV | The folder column becomes one tag, and a tags column (or one headed "Tags" in Japanese) becomes multiple comma-separated tags |
| Samurai App | Exported .json |
Keeps every field |
| Other | CSV with headers | Read by headers such as title, URL, ID, password, and notes |
The format is identified by the contents, not the file extension. Item types (logins, notes, cards), cards, custom fields, and two-factor setup keys are kept.
Steps
- Open "Passwords". If it's your first time, set a passphrase of 12 or more characters in "Get ready to use passwords" and save the emergency kit
- Create the destination vault with "Create vault". Choose "Shared" if your team will use it
- With the vault selected, press "Import" and choose the exported file
- Check the count it read. It shows how many logins, notes, and cards it read, and how many attachments, passkeys, and trash items it skipped
- Import. If you hit a limit, it stops without sending the rest and tells you so
- Add the people to share with from "Members", and choose "Admin", "Editor", or "Viewer"
- Delete the exported file and change passwords, starting with your most important accounts
All items in one file go into the single vault you selected. 1Password vault names don't become tags. If you want to tell items apart by department, tag them in the old service before exporting. After importing, you can narrow down by department with "Filter by tag".
What doesn't carry over
- Passkeys and attachments: they don't go into the vault, so they stay in the old service. The import screen tells you this too
- Items in the trash: they aren't read, even if they're mixed into a 1Password export
- Encrypted Bitwarden exports: you'll see "Encrypted exports can't be read". Export again without encryption
- Google Authenticator export QR codes (
otpauth-migration://): these can't be read. Enter each site's setup key or anotpauth://URL in "Authentication code key"
Limits and where it doesn't fit
- There are limits: up to 2,000 items per vault (including items in the trash) and up to 256MB for the whole workspace. Companies with many items import into separate vaults
- AI can't use the vault. For sites where you want AI to handle sign-in, open the item and register it separately with "Copy to browser authentication"
- Filling in sign-in pages is done by the Chrome extension. It doesn't suit companies that use autofill in other browsers
- Company admins can't recover an employee's passphrase. A personal vault can no longer be opened if you lose both the passphrase and the recovery code. A shared vault can be opened again if that vault's admin re-shares the key
- Only vault admins can export. If you move elsewhere in the future, you can choose "JSON" or "CSV". CSV includes only the title, first URL, ID, password, notes, and authentication code key, and doesn't include cards, custom fields, or tags
If you want to compare products before deciding, see Password manager comparison. If you're moving from a spreadsheet list, see The risks of managing passwords in Excel. Product details are on the Password manager page.
FAQ
Which format is best for migrating from 1Password to Bitwarden?
Bitwarden's help covers importing from 1Password's .1pux (1Password 8.5 and later), .1pif, and CSV, as well as importing without a file from the desktop app or browser extension. CSV leaves out custom fields, so if you use a file, choose .1pux. Also note that Bitwarden's import doesn't check for duplicates, so importing the same file twice gives you two of every item.
Can I open the exported CSV in Excel and fix it?
You can open it, but saving it again in Excel can change the character encoding or date formats. If you fix it, don't make copies, and delete it along with the original file when you're done. Samurai App's import can also read CSV files saved in Shift_JIS.
Do I need to change every password after migrating?
Not if you can say for certain that no copy of the exported file remains anywhere. If you can't, change the ones involving money, the ones with admin permissions, and the ones that publish in the company's name first.
Can passkeys be migrated?
1Password says passkeys can be handed over too when you export from the phone app using the Credential Exchange standard. Bitwarden also supports direct handover using the same standard. They won't carry over if the receiving side doesn't support it, so check what the destination supports. Samurai App vaults don't import passkeys.
Sources
- Export your data from 1Password (1Password Support)
- Export Vault Data (Bitwarden Help)
- Import Data from 1Password (Bitwarden Help)
- Manage passwords (Google Chrome Help)
- Passwords (how to use) (Samurai App)
The steps for 1Password, Bitwarden, and Google were checked against what each company's official help pages said as of November 9, 2026.