You can create a random password for each user and send an email notification with all your new password. But this will lead to confusion if the user does not see the letter.
I recommend that you add another db field for the bcrypt value, and then create a record when the user logs in for the first time after the change. You can use either a separate field or delete the old hash for tracking.
When your active users migrate, feel free to use the random password method for the rest of your user base to complete the migration.
source share