MRC Converter suite: Enpass to 1Password - unexpectedly matched multiple outkey values for 'url'

Hey Thanks for that additional context. Having emails in their own custom fields at least allows 1password to autocomplete the emails and passwords on the multitude of imported credentials, so it's way more than enough to get me started.

I'll go over them and move the emails to the username field as I move forward, but you've given me so much help and I am absolutely grateful.

Thanks again!

Great!

And LOL - I've always wanted to be a GOAT.

I was editing my reply above to add the following, but saw your reply come in, so figured I'd post it here instead:

map e-mail to the internal Email field

FYI: that's just a 1Password data "type" - it's not an internal Email field. You can add as many additional fields as you like to records, and select the type when you create the field. Currently the type cannot be changed in 1Password 8.

Alright this is beyond perfect!
You are the ABSOLUTE Greatest Of All Time!

Thank you very very much!

@charliesigma

I've updated the dev archive. It adds this custom field mapping:

and another internal addition, to produce:

Ohhh I see. Then I think it's better to import the e-mail field as a custom one and keep username as is. This way, for entries that I have both, they'll at least make sense to me when looking at them.

@charliesigma

Three key fields are used by 1Password for Login autofill. These are keyed in the converter with certain reserved internal field labels: username, password, and url. Other fields (and their labels) are essentially information; there are there for you, but do not take part in autofill. Given that Enpass has both a Username and an E-Mail field for Login records, we have to select which of these fields to map to the field that 1Password will use for autofill.

This might be my lack of knowledge of 1pasword for now, but can it use the 'default' email field?

Like, Keep username as username and map e-mail to the internal Email field:

So, after importing it would look like this:

@charliesigma

Great, thanks for the feedback.

Yes, the E-mail field can become the primary username field. How do you want Username mapped? As a custom field?

Hey it worked perfectly! Thanks so much!

Now, a quick last question: is it possible to map the e-mail field from enpass to the e-mail field from 1password? Most of my logins are e-mail based and the're all being pushed to the notes.

@charliesigma

I've updated the development version for you.