Feature request: convert a login into a different type

revlisoft

It would be nice to convert one login into a different type like an email account or between related types.

DBrown

As discussed in many threads, each type has a specific "template"—what fields of what types must be included, with one type requiring very different kinds of information than another—and you cannot currently switch items from one type to another.

We never say "never," though, so thanks for letting us know you'd find that useful!

revlisoft

That's understandable. If this is implemented you can have a "windiff" like interface showing where the new fields are being moved or lost or if any field is being truncated you can convert those into name:value pairs and put it into the notes which can then be converted back if a user decided to re-classify the type.

DBrown

Types (categories) are so fundamental to our data structure that it would take a major overhaul (on four different platforms, nearly simultaneously) to revamp the concept from the ground up. I'm not aware of any plans at this time to take such a measure.

revlisoft

I wouldn't propose a revamp of the data structure since that is too extreme. My suggestion would be to

1. allow a user to select an existing entry (of a certain type)
2. let them select the new type
3. read from the old type into the new type.
4. fields which are readily transferable (common fields) should go through. Those which can't are either dropped or saved into the notes as name:value pairs

Not all types can be converted from one to another especially if they are extremely different. However, only allow those which are somewhat similar. I would start with simple types and add support for more types over the next few releases. I think people will also spend less time figuring out what the best type is knowing they can convert some of them without having to manually retype.

DBrown

Thanks again for the suggestion, @revlisoft!

RichardPayne

@revlisoft‌ do you have a need for this during normal usage or is it just for sorting out "logins" imported from other systems?

revlisoft

During the initial import is important as that directly drives how your new users will be willing to convert. It's also a nice feature enhancement for ongoing use.

RichardPayne

I asked because I honestly have never found a need for this during normal. I can absolutely see the need during import though.

[Deleted User]

I think the most common user case of changing category (outside import) is when the user has created an Email account item for a webmail account, not realizing the Login category is the preferred category for such accounts. But then I wonder, isn't the solution to make the user choose the right category from the beginning, rather than making it easy to convert from one to another? Or in other words, how do I explain to the average user that no, your Gmail account should not be an Email account in 1Password, because you use Gmail and the Email account category is only used if you manually configure a local client while your Gmail is automatically configured, even if you use it not in your browser but in your local client?

Presumably, the same reasoning got the IM and iTunes categories removed.

AlexHoffmann

As David described earlier in the thread, our item types are highly specialised and any restructuring or addition of features related to switching item types would have to happen on all four platforms simultaneously.

That being said, we realise that customers like you would benefit from a solution to this issue. There are things we're thinking about doing, but none of them will get into public releases any time soon.

Sorry I don't have better news. I have however brought this particular to the attention of the team again.