What actually transfers from a 1Password 1PUX export

1Password's .1pux export is the richest format it produces. It is a ZIP archive containing your items as JSON plus the actual files you attached, which makes it a much better migration source than the CSV export. Buddy reads it directly.

What follows is the field-by-field account of what carries over, taken from the importer itself rather than from a feature list. The parts that do not transfer are listed too, because those are the ones that ruin a migration when you find them a month later.

Making the export

In the 1Password desktop app, choose File, then Export, then your account, and pick the 1PUX format. You will be asked for your account password.

The resulting file is unencrypted. Treat it the way you would treat a text file containing every password you own, because that is what it is. Put it somewhere local, import it, then delete it. Do not leave it in Downloads, and do not let it sync anywhere.

What Buddy reads from the file

Buddy detects the format from the archive contents rather than the file extension alone, then walks every account and every vault inside it.

Core login fields

1Password	Becomes in Buddy
Item title	Title
Primary website	URL
Username	Username
Password	Password
Notes	Note
Tags	Tags
One-time password	TOTP field, with issuer, digits, period and algorithm
Created and modified dates	Preserved

TOTP is worth calling out because it is the field people assume they will have to redo by hand. The secret comes across, so your codes keep generating without visiting any site's security settings again.

Custom sections and fields

1Password items can carry arbitrary extra fields, and those are mapped by type:

1Password field type	Becomes in Buddy
Text, URL, phone, menu	Custom text field
Multi-line text	Custom note field
Concealed value	Custom secret field, masked until revealed
Email	Custom text field, address only
Date	Custom text field, formatted as a date
Month and year	Custom text field, for example March 2026
Address	One custom text field with street, city, state, postal code and country joined together
Single sign-on	Custom text field holding the provider name
File	Encrypted attachment on the entry

Payment cards

Card items get real card fields rather than a pile of custom text: cardholder name, card number, CVV, and expiry converted to MM/YY. The card brand is dropped, since Buddy derives that from the number.

SSH keys

SSH key items bring across the public key, the private key, and the fingerprint and key type as fields in an SSH section.

Attachments

Files attached to items are pulled out of the archive and re-encrypted into your Buddy vault, with their original filenames. They are matched to their items by the document ID recorded in the export, so an item with three attached files arrives with three attachments.

What does not transfer

Read this section before you cancel anything.

• Archived and deleted items. Only items 1Password marks as active are imported. Anything in the archive or the trash is skipped. If something you care about is in there, restore it in 1Password before exporting.
• Your vault structure. 1Password's separate vaults are flattened into the single Buddy vault you import into. Buddy supports multiple vaults, so if you want that separation back, import once per vault into a vault you created for it, or use tags.
• Password history. 1Password records previous passwords per item. Those are not imported. Buddy keeps its own field history from the moment an entry lives in Buddy, but it does not backfill.
• Favorites. The favorite flag is not carried over.
• Additional website URLs. An item with several saved URLs contributes its primary one. Add the others by hand if autofill needs to match more than one domain.
• Passkeys. Buddy does not support passkeys yet, so any stored passkey stays behind. If you rely on passkeys, that is a reason to keep 1Password.
• Sharing, Watchtower state, and account settings. These are service features rather than vault contents, and there is nothing to map them onto.
• Unrecognized field types. If 1Password adds a field type Buddy has not seen, that field is skipped rather than guessed at, and the import log records it.

Doing the import

1. Create the vault you want the items to land in, if you are keeping them separate.
2. Drop the .1pux file onto Buddy's import screen. The format is detected for you.
3. Review the preview. Nothing is written to your vault until you confirm, so this is where you check that counts and fields look right rather than after the fact.
4. Commit the import. Attachments are read out of the archive at this point.
5. Spot-check entries: one login, one card, one item with an attachment, one with a TOTP code.

Before you cancel the subscription

Keep 1Password active for a couple of weeks. It costs one more billing cycle and removes all the pressure from the checks above. In that time you will hit the entries you actually use, which is a better test than any spot-check.

Then delete the .1pux file. It is still a plaintext copy of everything.

If the migration goes the other way later, Buddy exports the whole vault including attachments, and the vault format is documented publicly so the export does not depend on us. That is the same standard this guide is asking you to hold 1Password to.

1Password is a trademark of AgileBits, Inc. Buddy is not affiliated with or endorsed by 1Password, and 1Password's export format can change without notice.