Skip to main content
August 24, 2022
Solved

How can I move an entry from one category to another in the same vault?

  • August 24, 2022
  • 2 replies
  • 277 views

Running the latest version of 1Password on Windows 10. I have an entry in one category I want to move to a different category without having to completely type it in.


1Password Version: 8.8.0
Extension Version: Not Provided
OS Version: Windows 10
Browser:_ Chrome and Edge
Referrer: forum-search:https://1password.community/search?Search=How%20can%20I%20move%20an%20entry%20from%20one%20category%20to%20another%20in%20the%20same%20vault%3F

Best answer by ag_mike_d

Hi @jwscofield,

Thank you for contacting us with your question about changing the category of 1Password items.

Categories are a templates for a set of data based on the item type you are trying to create. In the case where an item was created using the wrong template (say, Credit Card vs Bank account), I can see where the ability to change the category of an item would be useful. At this time, there is no way to change the category of an item once it has been created and saved. You can create a new item in 1Password by selecting New item (Ctrl + N), selecting the new item type you'd like to use and then copy any information into that newly created item.

I've included your thoughts in a feature request we're tracking for the product team. We appreciate your feedback!

ref: IDEA-I-844

2 replies

ag_mike_d
ag_mike_dAnswer
1Password Employee
August 24, 2022

Hi @jwscofield,

Thank you for contacting us with your question about changing the category of 1Password items.

Categories are a templates for a set of data based on the item type you are trying to create. In the case where an item was created using the wrong template (say, Credit Card vs Bank account), I can see where the ability to change the category of an item would be useful. At this time, there is no way to change the category of an item once it has been created and saved. You can create a new item in 1Password by selecting New item (Ctrl + N), selecting the new item type you'd like to use and then copy any information into that newly created item.

I've included your thoughts in a feature request we're tracking for the product team. We appreciate your feedback!

ref: IDEA-I-844

February 20, 2025

any news on this feature request please ? ref: IDEA-I-844

1P_Dave
1Password Employee
February 20, 2025

@technonath1 Thanks for following up! The feature request remains open with the team but I don't have any updates to share at the moment. 🙂

-Dave

February 20, 2025

Thank you for taking the time to reply, I do understand development pressures , but if you look at some of the other FR's that I have bumped - they are things that were already in  V7 - like changing the individual field type and you haven't even put that functionality back 4 years after releasing v8 - that doesn't really build customer confidence in the product - that makes you another MS/google who just take away functionality at random because you think your customers do not need it.
or for example in the windows app you create a vault and then have to log in to the web browser version to admin the security of it! - Surely that is a basic requirement of administering a password safe and should be in the windows app by now .

 Or here's a constructive idea, you could do a MS and use edge webview to just display the existing web interface for controlling permissions inside the windows app? - it's not pretty but would get the job done with minimal dev time needed.

I hope you see my points as constructive.

If you want to improve customer faith in your product then please be more transparent and publish a roadmap - I would rather that you attempted to publish one with dates that are aspirational, than not publish anything for fear of public outcry when you don't meet a certain delivery date.  MS push things back a lot on their roadmap - but at least they are trying to be a little bit more transparent, than log an FR in a forum blackhole never to hear anything again for years on end. I would be much more understanding if you even came back once in a while and said we have looked at this - "it would cost too much to develop" / "would require an extensive redesign"/ "feature X is taking all our dev time, but we aim to get it out in X sprints time....."

thanks for listening.