@jace88 @bradl in the short term you probably right.
But the issues with staying on 1Password 7 (as is the case for many applications that the developer ceases to support) will become:
1/ Any problems with the application will (in all probability) not be patched. The frequent application software patches cease. Vendor support becomes a discussion demanding that you upgrade to the supported app.
Oh, this part is definitely true. However, because they demand that you upgrade to the supported app to get support doesn't mean that you have to upgrade to it. I mean, I'm still on 1Password 6 because it still works for me and suits the purposes that I have. And even the last release they had out for it still contained security patches. Right now, it falls under the 'security by obscurity' phase, because as they've dropped it and have most other people either on 1P7 or 1P8, no-one is really looking for exploits for it.
2/ Operation System updates (iOS, macOS, windows 10) will, probably sooner rather than later, mean that the 1P version 7 app is not compatible with the new OS. ( As an aside, some developers use Apple and Microsoft OS upgrades as an excuse to walk away from existing apps and their problems, demand users give up existing features (no longer supported ... its not our fault) etc (Sonos is a prime example)
The good part here is that unless libraries change (which is the key part) or libraries that the binary needs are not available (if not compiled statically), the application will continue to work due to the architecture of the CPU. 1Password 6 and 1Password 7 will continue to work on my mid-2011 MBA, because it was compiled as 64bit on the x86_84 architecture. If the CPU architecture changes (for example, Silicon), a x86_64 (Intel/AMD CPU architecture) won't work, as the architecture is incompatible for the binary application. The data will still work, but the program will not.
And if the library changes, it also may not work. That is why my iPad mini 4 is still on IOS 10.3.3; I have apps that I like to use (old games) that still use 32bit libraries, and anything iOS 11 or newer removes those, as it was the first iOS to be fully 64bit.
But to have iPassword 6 still work for me for 5-6 years after starting with 1Password 3, all on the same hardware, and across 6 revisions of MacOS says a lot. the iOS app is the latest on my iPhone and still works as well, and that's going from iOS 4 up to 14.
You could keep using v7 and not upgrade the device OS. But thats not too good an idea given the security patches of the OS you deny yourself.
You can use v7 and upgrade the OS. See above. I went from Lion up to Sierra with 1Password 3 through 6, and I'm still going strong. In fact, I put 1Password 6 on when Mavericks was out. I'm on Sierra now, and the only reason I'm on Sierra, is because High Sierra was very unstable on my MBA, and then they dropped support for my Mac after High Sierra.
Best bet is to take your time, export all your data, transfer to another password manager run it in parallel to test it so your happy everything is working before committing to using it as your new production password manager.
Agreed here. That's what I'm planning to do. However, I'm going to do that when I get a new Mac, hence why I am waiting until the next models come out. but I have to say that after rebuilding windows and Linux boxes for personal use every other year, having my Mac run strong for 10 years without a single need of repair is amazing.
bradl's comment ".....but a cancelled subscription is a cancelled subscription, so you would lose access to what you previously subscribed to" is really notable. I had not considered that.
Exactly. This is why the ability to have local vaults and standalone licenses are important. We should be in charge of our data, not anyone else, especially if it comes to that 3rd party being compromised, or any legal issues.
BL.