Let's say that you are about to change your log in system and you have a few millions of users that you want to switch to the new system.

Specification Old System

  • Username : email address
  • Password Policy : None
  • Email Verification : None
  • Password Hashing : None

Specification New System

  • Username : email address
  • Password Policy : Yes
  • Email Verification : Yes
  • Password Hashing : Yes

I am of the opinion that the users should have to recreate their password and verify their email address but asking the users that have been client for many years to suddenly recreate an account, verify their email or change their password might be a bad user experience.

So, I'm asking both in term of security and user experience :

How would you migrate those old accounts?

Note : Since it's a system that involves money transaction I really don't think we should keep the old passwords that often look like "123", "abc", "password", etc.

1 Answer 1


What you could do is hash the old passwords and make the users choose a new one when they login. You really need to force them to use new passwords though since if there's not a 100% chance that the old database was leaked their financial info could be exposed. If you think that the old system was compromised you'd be better off sending out emails, or requiring verification when they login.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .