diff --git a/docs/guides/development/migrating/overview.mdx b/docs/guides/development/migrating/overview.mdx
index 0e05de8ec3..44b4819675 100644
--- a/docs/guides/development/migrating/overview.mdx
+++ b/docs/guides/development/migrating/overview.mdx
@@ -22,7 +22,7 @@ Each of these have trade-offs you'll need to consider for your application and i
 
 With basic export/import, you're taking an export from your previous tool and importing data into Clerk. The most common way to handle this is by making use of the [`CreateUser`](/docs/reference/backend-api/tag/users/post/users){{ target: '_blank' }} Backend API endpoint. It's important to note that the `CreateUser` endpoint is rate limited. For more information, see the [guide on rate limits](/docs/guides/how-clerk-works/system-limits#backend-api-requests).
 
-You'll also need to provide your `password_hasher` value (the hashing algorithm used to generate the password digest) and in some instances Clerk will transparently upgrade your users' password hashes to the more secure Bcrypt hashing algorithm. More details on this topic are available in the [Backend API reference docs](/docs/reference/backend-api/tag/Users#operation/CreateUser!path=password_hasher\&t=request){{ target: '_blank' }}.
+You'll also need to provide your `password_hasher` value (the hashing algorithm used to generate the password digest) and in some instances Clerk will transparently upgrade your users' password hashes to the more secure Bcrypt hashing algorithm. More details on this topic are available in the [Backend API reference docs](/docs/reference/backend-api/tag/users/post/users.body.password_hasher#tag/users/post/users){{ target: '_blank' }}.
 
 ### Considerations