How to change the Category assigned to a record

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.