Expected Behavior

The migrate browser settings dialogue should explain that it will take your existing KeePassHTTP settings and convert them to KeePassXC-Browser settings, and then destroy the old settings, with no way to undo the change.

Current Behavior

The migrate browser settings dialogue does not explain what is actually happening.

Possible Solution

It is fine to migrate the existing KeePassHTTP settings to KeePassXC-Browser, but the default should be to just migrate, and not destroy the data. Both types of settings can live in the DB. If you are eager to remove the old settings, the user should be informed specifically what that means and then be given an additional choice of removing them.

Steps to Reproduce

Hit 'yes' in the migration box.

Context

This really forked my KeePass DB. Now I have 500 entries that don't work with regular KeePass+KeePassHTTP anymore, which I really need them to. (And please don't tell me that I can run KeePassXC on different OS', or that KeePassXC is better. I know that, it's not what I want to do, and it's not a fix in this case.) It boils down to good programming behavior; don't destroy data.