Auth0 to Clerk Migration

Point this agent at your Auth0-integrated codebase and ask it to plan your migration to Clerk. It inventories your Auth0 tenant and SDK usage, plans user export/import including password-hash handling, scaffolds the Clerk provider/middleware code and JWT claim templates, and validates an import batch against a Clerk development instance.

What it does

1. Map your Auth0 integration: connections, Rules/Hooks/Actions, Universal Login customization, RBAC roles and permissions, M2M clients, and every SDK call site per framework.
2. Plan the migration: bulk vs trickle user migration, the bcrypt hash-export request to Auth0 support, session cutover, JWT claim/template mapping for downstream APIs, and org/RBAC mapping to Clerk Organizations and roles.
3. Scaffold the Clerk side: provider/middleware code per framework, Backend API user-import calls with password hashes, webhook translation, and JWT template configuration.
4. Sandbox — import a sample user batch into the development instance, verify sign-in with an imported hash, compare JWT claims against the mapping, and report PASS/PARTIAL/FAIL evidence.

Prerequisites

• CLERK_SECRET_KEY — secret key for a Clerk development instance
• CLERK_PUBLISHABLE_KEY — publishable key for the same instance
• AUTH0_DOMAIN — optional; your tenant domain for config lookups
• AUTH0_MGMT_API_TOKEN — optional; read-only Management API token for live tenant inventory and user-export jobs

Current scope

This solution migrates users, connections, SDK integration code, JWT claims, and org/role structure. It does not port Auth0 Actions code (Clerk's extension points are narrower — each Action gets a manual-review mapping), does not re-enroll MFA factors, and does not configure per-IdP enterprise SAML connections (it produces a per-IdP worksheet instead). Historical Auth0 logs and analytics do not migrate.