Yes, there are a few more guides that you might find helpful. Firstly, when importing hashed passwords, Ory supports several algorithms including MD5. However, it's important to note that Ory doesn't hash passwords by MD5 but can compare stored MD5 hashes and migrate to the configured hasher (

hashers.algorithm

). You can configure MD5 hashes to use a plain format (for hashes without salt) or a salted format (for hashes with salt) [source](https://www.ory.sh/docs/kratos/manage-identities/import-user-accounts-identities#hashed-passwords). If your MD5 hashed password uses salting, you should follow the guide on importing salted format hashes. This guide explains how to import passwords that use salting to calculate the MD5 hash. Ory doesn't prepend or append the salt to the user's password. To determine the way the system performs salting, use the

salting-format

parameter [source](https://www.ory.sh/docs/kratos/manage-identities/import-user-accounts-identities#salted-format-hashes-with-salt). If you're migrating from another service like Auth0, you might find the guide on migrating from Auth0 useful. This guide provides steps on how to import your Auth0 users to Ory, including how to handle password hashes [source](https://www.ory.sh/docs/migrate-to-ory/migrate-from-auth0#import-users-to-ory). Lastly, if you're importing clear text passwords, Ory supports this as well. The password will be hashed according to the configured password hashing algorithm and stored in the database. The user will then be able to sign in using their email and the imported password as credentials [source](https://www.ory.sh/docs/kratos/manage-identities/import-user-accounts-identities#importing-credentials). Remember to ensure that the hashed password is provided in the correct format in the JSON payload during the import process.