Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
Former Member
3 years agoHow to change the Category assigned to a record
I like the way 1Password has expanded the Categories available. I also like that when setting up new records, one can choose and existing Category "template". To make using easier, I'd like to change the Category for an existing record from one Category to another without changing the data structure that exists. Is that possible please?
1Password Version: 8.8.0
Extension Version: 2.3.7
OS Version: Windows 10
Browser:_ Chrome
- garethshawNew Contributor
I wanted to follow up on a feature request from over ten years ago. As a developer with a specialization in big data, meaning highly normalized database design, and often over engineering to ensure future compatibility. I understand that your system was built with a clear purpose and vision. However, I’ve run into a significant usability challenge which means, I just don't do anything about it and struggle every day, I renamed all of the email accounts so they appear at the top of the search list when they were super annoying to find. I can't even restrict the list to items that have gmail.com in the website address field, you search every field always. Why?
I currently have 1,372 items of which 645 entries containing “@gmail.com”, and I’m trying to identify email account logins that were created long before your cloud offering existed, not just logins with @gmail.com accounts, and these entries contain valuable historical password data and changes, which I’d rather not lose. Of course, I could manually recreate them—but that’s a tedious and unnecessary step when a structured migration tool could make the process far more efficient, plus, I'd lose the history.
A Simple, Effective Solution
Instead of requiring a complex migration tool upfront, why not offer a basic field-mapping system that allows users to manually align old fields with new ones?
This could be a simple interface that:
• Displays the existing fields in one column and the new category options in another.
• Allows users to manually match them.
• Preserves historical data where possible (or, at the very least, warns users about potential data loss).There’s already a direct correlation between username, password, OTP, passkey, website, and notes—so users can handle the transition themselves without needing an intelligent converter in the first version. This would let people migrate their data efficiently without resorting to copy-pasting hundreds of individual entries.
Design for How Users Work, Not Just How You Expect Them To
We provide feedback because we care about the product and want to see it improve. Misclassifications happen, even to the most organized users.
If your own team has ever categorized an entry incorrectly, ask them:
• How easy was it to fix?
• Did the friction discourage them from ever correcting it?
• Or did they simply leave it as-is, reducing their use of your own product’s effectiveness?If the process is frustrating for your users won’t engage with the system as intended. Instead of designing based purely on an ideal workflow, consider how real users actually interact with the platform.
Accessibility and User-Centered Design
Right now, I’m designing a system for a disability-focused charity, where multiple ways to access the same information are crucial. I interact with data differently than a blind user, who may rely on screen readers, or a physically disabled user, who may use assistive technology. That flexibility ensures the system is inclusive and practical.
The same principle applies here. A migration tool that accounts for different user workflows will improve engagement and satisfaction—without requiring workarounds that cause frustration.
Start Simple, Enhance Later
All we’re asking for is a basic migration tool—even a manual mapping interface would be a huge step forward. You can always add automation and refinements later, but giving users a way to efficiently migrate their data now would make a significant impact.
Thanks for your time, and I hope you’ll consider pushing this request to the top of the list.
- joshfreeNew Contributor
I want to bump this feature request. I'm a long-time user and have thousands of passwords in my vault. I don't want to have to copy and paste hundreds of them by hand just to get the Categories fixed. Surely this process can be automated by the developers.
- Steve_MNew Contributor
I came here with the same question. Among other problems, I have many Login items I want to change to Wireless Router items so I get the QR codes.
I'm not asking for fully automated conversions, only the ability to see one old and one new item side-by-side so I can drag the old fields across to the new item, and hopefully be able to do it once manually and 1Password do the same for the selected, identical source Items. It's partly possible now to do single conversions with some manual effort, but the new item window is stationary in the center of the screen. On a 13" MacBook Pro it can be a challenge.
Being able to apply that mapping to multiple old items would be huge for users and a reasonable coding effort. Here's a use case for why this is important. I have forty-one "Passwords" item types I want to change to "Login" types. I don't know why they were created that way; I don't think it was my choice, and they all lack user names. Anyway, It's a simple conversion: Old password → New password, Old website → New website, and I have to remember and enter the username.
What I need is the ability to:
1. Select all 41 items
2. Choose a "Convert to..." menu item
3. Select a New Item type (maybe with a submenu)
4. See the old item's template on the left and the new template on the right, possibly with one item's field data shown on the left for a more intuitive UX
5. Drag fields from left to right for the mapping I want. See lines from old to new fields. and be able to move or remove them. If it's simple to pre-match the identically-named fields, that would be nice. The titles can transfer over untouched.
6. Click a button, and my mapping is used to create a bunch of new items from the old ones.
7. The final step could be nothing, which is probably best for budget. Other ideas are to have an option to Archive the old items with one click. Undo would be nice, but this can be manually achieved pretty easily.Thanks for continuing to listen.
- Steve_MNew Contributor
I came here with the same question. Among other problems, I have many Login items I want to change to Wireless Router items so I get the QR codes.
I'm not asking for fully automated conversions, only the ability to see one old and one new item side-by-side so I can drag the old fields across to the new item, and hopefully be able to do it once manually and 1Password do the same for the selected, identical source Items. It's partly possible now to do single conversions with some manual effort, but the new item window is stationary in the center of the screen. On a 13" MacBook Pro it can be a challenge.
Being able to apply that mapping to multiple old items would be huge for users and a reasonable coding effort. Here's a use case for why this is important. I have forty-one "Passwords" item types I want to change to "Login" types. I don't know why they were created that way; I don't think it was my choice, and they all lack user names. Anyway, It's a simple conversion: Old password → New password, Old website → New website, and I have to remember and enter the username.
What I need is the ability to:
1. Select all 41 items
2. Choose a "Convert to..." menu item
3. Select a New Item type (maybe with a submenu)
4. See the old item's template on the left and the new template on the right, possibly with one item's field data shown on the left for a more intuitive UX
5. Drag fields from left to right for the mapping I want. See lines from old to new fields. and be able to move or remove them. If it's simple to pre-match the identically-named fields, that would be nice. The titles can transfer over untouched.
6. Click a button, and my mapping is used to create a bunch of new items from the old ones.
7. The final step could be nothing, which is probably best for budget. Other ideas are to have an option to Archive the old items with one click. Undo would be nice, but this can be manually achieved pretty easily.Thanks for continuing to listen.
- kjahnOccasional Contributor
I second this longstanding request. It's all good and well that certain fields should be filled and checked for database consistency when an item's category is changed. but that should be easy to flag - copy the existing stuff into a general (e.g. notes) field and show the fields that should be set up properly.
Btw., have you tried using the "create a new item" e.g. in the passport category? The fields requested there are relevant, but tedious. I tried to set my birthdate. It shows a calendar of the current month (July 2024) and the only way to get to my birthday is 77 years x 12 months = 924 clicks on the back arrow! You can't be serious! I entered the birthdate as a text field. So much for keeping the database consistent, Mr. Developer. - DimatrixNew Contributor
This topic is now over two years old and the feature still doesn't exist?
I need the feature too. Just migrated from my KeePassXC and it looks terrible. - JimmyBillyNew Contributor
I second the comments above. As I have said before a good, experienced Software Engineer could help with this. If you don't have one on staff then you should consider hiring one for a while or bring one in as a consultant.
- technonath1New Contributor
1P_Dave Any chance you have got this to the top of the development list yet ???
We desperately need this now please. - technonath1New Contributor
+1 from me too for this, along with a way to bulk select all the ones you want to change in one go!
- 1P_Dave
Moderator
The team doesn't have any news to share about this feature request. We tend to play things pretty close to the chest since we don't want to promise new features only to frustrate folks when those features are delayed or cancelled.
Hopefully I'm able to share more in the future. For the time being, I'll continue to push for this feature internally. 🙂
-Dave