Forum Discussion

gholcomb's avatar
gholcomb
Occasional Contributor
2 years ago

Conversion Issue from Keeper to 1Password - Shared Folders Don't get converted to tags

MrC I was checking the data as you suggested and found that shared folders do not get converted to tags like normal folders do. I've put a screenshot of what the JSON file looks like for a shar...
windows
MrC's avatar
MrC
Super Contributor
12 months ago

gholcomb

I get it.

There are several reasons why the perfect world isn't here yet.

  • Creating a single vault was a design decision I made when I created the 1PUX generator. It is (correctly) painful to remove vaults (yet obviously this is something I frequently). Imagine a generator creating a dozen vaults, and then having to manually delete each one:

    • right click the correct vault
    • select Delete Vault...
    • type in the vault name to the confirmation dialog
    • press OK
    • select the next vault
    • rinse, lather, repeat

  • The 1Password 1PUX importer has no user-facing diagnostics, and it is very finicky. It was a lot of reverse engineering to be able to reliably generate importable 1PUX files. When things go wrong, the importer just aborts. So I quit while I was ahead.

  • I didn't want to pollute a user's list of vaults (I realize most converter users would have none).

  • It is much harder to review, edit, purge imported content in multiple vaults (and that's rather important, as you've discovered; and it's critical for me as I review conversions). Its easy to rifle through a list of items (at least for me).

  • I thought it prudent not to muscle-memory train users to delete vaults.

  • I don't have access to the more feature-rich business or memberships of other password managers, and without my ability to construct comprehensive export data, I'd be programming blind. The keeper converter is just one examle (you're the first person to provide me with the format of the shared_folders list and inform me about the "shared_folder" attribute in a record).

All that said, the converter framework can create multiple 1PUX (or 1PIF) files; the onepux and onepif converters do this with the ```--percategory option. I suppose for the keeper converter, there could be an similar per-shared-folder option to do likewise, one 1PUX per shared folder, and I suppose one more for any items not in a shared folder. That could end up being a lot of 1PUX!