[Bulk migration](https://docs.strivacity.com/docs/bulk-import-migration) transfers all customer accounts to a new system at once, before customers begin signing in through it. When password hashes aren't available from the legacy system, accounts still migrate in bulk, but customers have to reset their password since their existing credentials can't be securely carried over.
Frequently asked questions
Why would a bulk migration require a password reset?
Only when password hashes can't be accessed from the legacy system. If hashes are available, bulk import can carry them over directly using a compatible hash algorithm, and no reset is needed.
Is a reset-based bulk migration ever the right choice?
It can be, despite the added customer friction. It gives every account a clean slate, ensures no outdated or compromised credentials carry over, and sets up stronger authentication methods like passkeys or MFA going forward.
.avif)