@verita84_uwu @mint If it is trivial as adding/renaming the field, you just do the logical reverse, drop/rename it back. Only possible with non-destructive migrations, switching to another hashing algorithm would likely require to explicitly support both algorithms on application level, or notify every user to set working emails and then do mass password reset after returning back to upstream. Assuming there isn't any more backwards-incompatible changes, so make a backup and experiment on local test instance maybe.