How to export a single vault

We as an agency have a vault for each of our clients. Many/most of whom do not use 1Password themselves.

We need a way to export their data from their vault to pass on to them without exporting all 300+ vaults simultaneously to csv where their stuff is mixed in amongst thousands of other items with no way to effectively differentiate them from each other.

@AlexLA

Thank you for sharing. I generally don't recommend that folks manually edit their exported items since it can result in malformed files that 1Password, and other password managers, aren't able to read. This can lead to data loss.

I've let the team know that a selective export feature is highly requested in the community. For now, if you do need to export just certain vaults, I suggest trying the Travel Mode workaround that I mentioned earlier in the thread: https://1password.community/discussion/comment/686235/#Comment_686235

-Dave

I have tested a method for exporting one or several vaults and can recommend it.

Firstly, the .1pux file is an archive. Although this topic is related to the MAC branch, I am confident that you can open this file by clicking, just as I did on Linux.

You need the export.data file from it, which is in JSON format. Extract it and edit it with your favorite editor (I used VSCode).

You may delete or keep any number of dictionary-type items inside the "vaults" list.

Put the edited file back into the archive and use it for import.

Ta-da!

It's my pleasure, thank you again for the feedback. 🙂

-Dave

Thanks, appreciate the info!

@stevenbrown

Thanks for the reply. The only way to fully export a complete copy of your items is by exporting items to a 1PUX file: How to export your data from the 1Password desktop app

The CSV file only contains a limited set of fields that includes the following:

• Title
• Website
• Username
• Password
• One-time password
• Favorite status
• Archived status
• Tags
• Notes

The CSV file will also only include Login and Password items. It won't include other items like Secure Notes, Identities, Documents, etc... If you need an export of every type of item and all of the fields in those items then you need to export to 1PUX.

Re feature req: CSV per item or selection of items, or at least entire vault would be reasonable data access.

Thank you for the feedback, I've passed it along to the team. 🙂

-Dave

Re: Archive - I use it often. Doesn't fill my need for getting my data, but it is appreciated.

Re: New CSV Export fields - Q: Have you recently introduced a feature that exports more fields than just the login/password under the "Export..." function for the entire user account? I browsed the https://releases.1password.com/mac/8.10/ but didn't find any mention of this.

Tried exporting to CSV, intending to export everything and then pick out the records I needed:

1. I chose "Export..." > "user", and saw a warning that it would only export login/password data.

   CSV (Logins and Passwords only): A comma-separated values file (.csv) will export only your usernames and passwords in an unencrypted text file.

2. Not my first choice, but upon testing, looks like the export actually includes fields such as: Title, Url, Username, Password, OTPAuth, Favorite, Archived, Tags, and Notes.

Q: I'm still unsure if this is the entirety of the text. Is it safe to export and then delete the original items? I'll probably delay this until I can cross-check the exported data with the source.

As OP inquired:

The only export options I see are either using the .1PUX format for all my vaults or the .CSV format, which appears to only export the logins and no other categories. There's no feature for exporting individual vaults.

Might be a little much user work to get text from a secure text storage app.

Re feature req: CSV per item or selection of items, or at least entire vault would be reasonable data access. There has to be a subset to the whole dbase. My 1pw CSV export of my user as a single file (with temp vaults imported from browsers, and all the archives, indiv pw's, and every variation of all the pw records therein, since 2006) is over 5100 rows. There are dupes, but the dbase has been fairly well maintained.

@stevenbrown

I removed your license information just in case since this is a public forum. 🙂

Thank you for explaining your use case. I also have a lot of old items that I want to keep around since they contain information that might be useful in the future. Have you thought about archiving those items instead? The Archive is where I keep those items that need to be kept but that I don't want to see suggested in the browser or in my normal item list: Talking trash: Why we're introducing the Archive

That being said, I've passed along your request to the product team.

-Dave

ref: PB-36242686

Hi Dave, thanks. I have a subset (~30) of old logins for a prior hosting provider that have no value to me as authentication info, but have many other fields with info I want to retain.

First try: Select all, Export... [deprecated]

Second try: Select all, new vault, drag to new vault (my item selection was retained as I created a new vault, nice touch), Export vault as.... [nope].

It's my data. I just want it 'cuz I want it 'cuz it's mine. Maybe there's a new way to do it, I saw a workaround using "set 1pw to some more singular vault travel mode"; meh. Overhead cost too high.

Bordering on data lock-in due to inconvenience, which is why I bailed from Evernote to vanilla .md a decade ago.

Appreciate you guys, though, and glad you're around. I'm still here since '06; now on subscrip.

[License information removed. -Moderator]

@stevenbrown

Thank you for the feedback, I'm happy to share it with the team. Can you tell me a little more about why you're trying to export a single vault so that I better understand your individual use case?

-Dave