For me the question is where I can easily migrate to
Sky's the limit on this. I migrated to both Enpass and Codebook. From the migrants thread:
Well... I've made my decision. And it's an interesting one.
I've decided to migrate to Enpass... and I've decided to migrate to Codebook. Why both?
Both offer what I need, so I'm not worried about requirements/features. As mentioned before, both use SQLCipher, which Zetetic created, and with it being FOSS, I'm comfortable in the encryption methods being used. And as the government uses this as well (meaning that they conform to NIST and ISO 27001 standards), they can provide DoD level encryption, which I've had to use in encrypting PCI data. Not that any of that is relevant here, but that simply because it has the ability to encrypt at that strength leaves me very comfortable in what both can do.
But why both? Simple. the problem.. is me.
Because I'm the IT guy, I'm effectively the de facto IT guy for 4 families: Mine, my mother's side of my family, my father's side of my family, and part of the in-laws. I store all of my family's vital records into that password manager: SSNs, bank account numbers, passports, birth certificates, etc. But with having hold of my extended family's data, this means that they also tend to come to me for some of the passwords to things that they forget. And while I could lump them all together into the same vault, or even create separate vaults for each part of my family, that still leaves one single point of entry: the master password.
Remember how I keep rambling on about Single Point of Failure? That master password is that single point of failure. What that means is that if that master password is lost by any means, all of that data is inaccessible. Further, should I give someone that master password for keeping should something happen to me, that means that that person would have access to everyone's data.
I prefer having that separate, so that one side of my family does not access to my other families' data. So two separate apps with two separate master passwords, and multiple vaults inside each application solves that perfectly. One master password can be given to my immediate family in case of emergency, and one master password to my mother in case of emergency there. I'm an only child, so the data for my father's side of my family will always be with me anyway.
So this way, I keep my family's data separate, plus protect one side from the other, and can keep my data in multiple vaults in applications in multiple places in case of disaster. In short, redundancy.
So both will be working for me, as both will suit my needs.
My requirements were rather simple: local vaults, no subscription, simple to import, multiple fields for data that can be inserted (see above). Both Enpass and Codebook met those requirements, with Enpass having ease of use, and Codebook having the years of experience behind the product. Both do the same for me, but as I said above, I needed a line of separation so both sides of my family can be safe in the fact that one side doesn't have access to the other side's data.
You can't go wrong with either of these, as well as the others that are available, but it all boils down to what requirements you have.
BL.