1Password v8 migration preparation

Hi @wagnerone !

The biggest issues are, that the classic browser extension is not supported from 1Password 8 and that 1Password 8 is not supporting local vaults. So if you want to switch to 1Password 8 you have to switch the browser extension, too. And if anyone of you is using a local vault, he / she is not able to use it after switching.

Next thing is the change of the UI. If you start using 1Password 8 you have to get used to the new UI and there are some features that are not implemented yet.

But you could try 1Password 8 by yourself. On Windows, 1Password 7 is automatically removed when installing v8. On Mac, you have to manually remove v7. If you are not comfortable with the new version, you could remove v8 and go back to v7 till it isn't supported anymore.

Nice @DenalB

@wagnerone

1Password in the browser has its own shortcuts for some activities. That may have caused some confusion. For example getting the dialogue to show in Chrome is Command + Shift + X Let us know if you have any questions.

Thanks! Is there a comparison somewhere between "1Password in the browser" and the "classic plug-in"?

Something like advantages of the new version vs the classic one? I've drug my feet because I felt it was inferior in a several ways and would like to be disproven. I can then use that info to educate my business/team.

Hi @wagnerone.

We don't have a specific support page for comparing the "1Password in the browser" and the "classic plug-in". I'm sorry about the inconvenience. I will list the major differences between them here:

1. Desktop app dependency:
2. The "classic plug-in" requires the desktop app to be functional.

3. "1Password in the browser" can work independently. When its integration feature is turned on and working with the desktop app, it can share the same locked state as the desktop app and use the desktop app shortcuts, for example, the "cmd + \".

4. Product development:

5. The "classic plug-in" didn't receive any updates since 2019.

6. "1Password in the browser" will receive continuous development and improve its functionality.

7. Vault access:

8. The "classic plug-in" can access local/standalone vaults, and its primary purpose is for our license users to achieve that.

9. "1Password in the browser" cannot access local/standalone vaults, and it is designed for our membership users. Plus, 1Password 8 will not access local/standalone vaults.

10. Functionalities in the browser:

11. The "classic plug-in" will prompt you to save the login (autosave) after submission.

12. "1Password in the browser" currently doesn't support autosave. But we have an existing feature request, and our development team is dedicated to providing the solution. Meanwhile, it introduced the inline menu suggestion and more features compared to the classic version.

In addition, we can find more support articles for the 1Password classic extension: 1Password classic extension support

Here is a helpful guide, and it includes all the functions and features for 1Password in the browser:
- Get started with 1Password in your browser

I hope the above explanations find you well.

@kevin_li - That is a awesome breakdown and highly appreciated! Thank you. I can share this with our company during our changeover.

Not having autosave seems like a significant issue. Do you have to create all entries manually? Is there an ETA on when this will be available?

Edit: guide revealed you can save manually when filling a new form, so not a big deal and possibly more desirable workflow than autosaving, IMO.

I will read through the links you provided. Thanks again.

Mike

Hi @wagnerone Mike,

You're very welcome.

Regarding what you mentioned:

Not having autosave seems like a significant issue. Do you have to create all entries manually? Is there an ETA on when this will be available?

I'm sorry that there is no exact date for the feature yet. I also want to clear the confusion there. It doesn't mean that we need to create all entries manually. That would be a terrible experience. What changed is the saving process. Allow me to explain:

The saving process changed for 1Password in the browser because of introducing the inline menu detection feature. It basically reverses the traditional password-saving process, asking you to save the login info after clicking the submit button. Instead, when you click the 1Password logo inside the inline field, the 1Password extension will offer you to save the login as shown below:

Here's a demonstration saving process for the current 1Password extension:

Suppose you entered the wrong password and saved it. No worries, we can update the login item anytime before submitting with the "Save in 1Password" button. Here's a demo GIF:

Quick Note: When you click the "Save in 1Password" in the inline menu, you can see the "Update" button when you change an existing login item. You can also save it as a new item, and the button will switch to "Save" accordingly.

Thank you for that follow-up. I should have known it wouldn't be fully manual! :) This looks great.

On behalf of Kevin, you're welcome. Let us know if you have any additional questions. We're here to help.