How to export a single vault

I too am looking to export a single vault. Please pass my feedback along as well.

@LarryMcJ needed to do just the same now (export only one vault for one organisation) and not able to do this.

Add this feature please, 1Password team. Transferring 100+ entries manually would be a pain.

@Dave_1P Dave, it is rather that the guys there want to use an open-source vault on their own hosted Nextcloud instance. Since it is only 1 person at a time using that database - it is not problem on my side to set things this way for them.

It is possible of course to do full 1PUX export, then import everything into KDBX database, then erase everything other than required vault but in such case - there is a big chance of recoverable traces remain.

Thus, it is would be much better if there is an option to export only concrete vault from 1Password - elegant solution and peace of mind pretty much guaranteed.

@Dave_1P sweet! Thank you for the heads up on this!👍

Looks like a solid workaround for sure - since this is not something that is needed often.

Please add another person to the request for the ability to export a single vault. I've been using 1Password since I think version 4 and it feels like every version since then has removed critical functionality and usability. I'd still be on 4 if I haven't been forced to upgrade every step along the way.

Same issue. Why did 1P decide to deprecate this useful feature? I have 1100 credentials and I only need a single vault of ~50. Preeeeeeetty frustrating.

I appreciate the link and your response, but that's a pretty clunky workaround for what seems like basic functionality that was intentionally removed by your product team. Not your fault, just frustrating. I'd rather use the v7 workaround I think. Thank you!

@Dave_1P

I've been using 1Password since v1 and I'd like to add a +1 to being able to export a single vault. I will look at the workaround elsewhere in this thread in the meantime.

I'm sure there was a good reason to remove this fundamental function, but it does remove some of the shine from being able to distribute pw items over different vaults.

"Different vaults! Totally separate!"

"Great! I want to export this vault."

"Totally the same - the good news is you can easily export everything!"

:-|

Doesn't appear that added voices will restore this function, so since I can't code my own app, my recourse is to whine about it. Mission concludes.

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]

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 release notes 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.

Thanks, appreciate the info!

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!