Hey, here’s your docs preview: https://clerk.com/docs/pr/1345

• Use @clerk/backend instead of @clerk/clerk-sdk-node. sdk-node is just a re-export of backend, but we've kept it around for backward compat reasons. The code is all isomorphic for cross-runtime compat, though, so we prefer backend for guides going forward.
• I don't think I understand the "Caution" callout. I would expect guidance on setting this for my existing user pool instead of a link to create a new user pool.

i think the right idea is to move this from "guides" and put it the "deployments and migrations -> migrations" section

• Use @clerk/backend instead of @clerk/clerk-sdk-node. sdk-node is just a re-export of backend, but we've kept it around for backward compat reasons. The code is all isomorphic for cross-runtime compat, though, so we prefer backend for guides going forward.
• I don't think I understand the "Caution" callout. I would expect guidance on setting this for my existing user pool instead of a link to create a new user pool.

@colinclerk

1. Good suggestion, I'll update to use @clerk/backend
2. The caution callout mentions that you can create a new client for your user pool. This is not to be confused with the user pool itself. Do you think this is misleading and should be removed? Or should we keep it and reword to be less confusing?

Edit updated the word to be less confusing

i think the right idea is to move this from "guides" and put it the "deployments and migrations -> migrations" section

@kylemac done. The page is now at /docs/deployments/cognito-password-migrator

How about just generically "migrate from Cognito" and then inside there we share about the migrator feature

How about just generically "migrate from Cognito" and then inside there we share about the migrator feature

@kylemac Sounds good to me. That should be an easy title + slug change. The document is pretty un-opinionated w.r.t it being about Migrating from Cognito vs. the password migrator feature. 👍