TL;DR: Migration risk in auth-as-a-service sits in data, APIs, SDKs, and pricing gates, Clerk says, so leaving a provider depends on more than exporting users. Standard protocols, exportable hashes, and documented exit paths bound the work and make cutover less disruptive.
Editorial analysis by NHI Mgmt Group, based on content published by Clerk: “What Is Auth-as-a-Service? The Complete Guide - Part 3”.
Key questions
Q: Why do standard identity protocols reduce migration risk?
A: They keep the application's identity layer decoupled from one provider's implementation.
Q: What breaks when password hashes cannot be exported?
A: The receiving provider cannot preserve user credentials, so teams lose the ability to move users without resets or trickle migration.
Q: How should teams evaluate auth-as-a-service providers for lock-in risk?
A: Evaluate portability in four areas: data export, API standards, SDK coupling, and pricing or contract friction.
Practitioner guidance
- Define portability requirements up front Require full user export, password-hash export, metadata export, and documented migration-out steps in vendor evaluation and contract review.
- Standardise on open identity protocols Build authentication around OIDC discovery, standard claims, and JWKS validation so application code is not tied to one vendor's token surface.
- Contain SDK coupling behind a facade Route provider-specific logic through a thin auth abstraction so sign-in UI, session checks, and route guards can change without broad rewrites.
Bottom line: Auth-as-a-service lock-in is best understood as an exit-risk problem across data, APIs, code, and commercial terms.
Glossary terms: Auth-as-a-Service Lock-in, Data Portability Request, SDK Lock-in, Portability debt
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Auth lock-in is a governance problem, not just a commercial one. The article correctly separates the pain of migration into data, API, SDK, and pricing dimensions, which is how practitioners should think about it. Identity teams do not only buy an auth stack, they inherit a dependency with operational exit costs. The implication is that portability must be designed, tested, and negotiated before production reliance hardens.
A few things that frame the scale:
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: Should authentication teams prefer providers with documented migration-out paths?
A: Yes. A documented exit path is evidence that the provider expects customers to move data, not just to join the platform. When the migration-out path is missing, teams should assume higher operational risk, greater contract leverage by the vendor, and a harder future change programme.
👉 Read our full editorial: Auth-as-a-service lock-in is about portability, not just pricing