Agent skill · software engineering · jeremylongshore
clerk-migration-deep-dive
Migrate from other authentication providers to Clerk.
Why this skill is useful
Adds executable scripts for migrating user data from various authentication providers to Clerk, which are not available in public documentation.
What it needs
Requires jq installed locally. Requires clerk account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Clerk Migration Deep Dive Current State !npm list @auth0/nextjs-auth0 next-auth @supabase/auth-helpers-nextjs firebase 2>/dev/null grep -E "auth0 next-auth supabase firebase" echo 'No auth providers detected' Overview Comprehensive guide to migrating from Auth0, Firebase Auth, Supabase Auth, or NextAuth to Clerk. Covers user data export, bulk import, parallel running, and phased migration. Prerequisites Current auth provider access with admin/export permissions Clerk account with API keys Git repository with clean working state Migration timeline planned (recommend 2-4 weeks) Instructions Step 1: Export Users from Current Provider Auth0 Export: NextAuth (Prisma) Export: Step 2: Import Users to Clerk Step 3: Update Database References Step 4: Replace Auth Code (NextAuth to Clerk Example) Step 5: Parallel Running (Optional Safety Net) Step 6: Cleanup After Migration Output User export from current auth provider (Auth0, NextAuth, Firebase) Bulk import script with rate limiting and error handling Database reference mapping (old auth IDs to Clerk IDs) Code migration examples (NextAuth to Clerk) Parallel running bridge for safe transition Cleanup checklist for removing old auth code Error Handling Error Cause Solution ------- ------- ---------- Duplicate email on import User already exists in Clerk Skip (status: 'exists') or merge Invalid email format Dirty data from export Clean/validate before import Rate limited during import Too many API calls Add 100ms delay between creates Password can't be migrated Passwords are hashed Use skipPasswordRequirement, user sets new password OAuth accounts Social login tokens non-transferable Users re-link OAuth accounts on first Clerk sign-in Examples Migration Verification Script Resources Clerk Migration Overview Migrate from Auth0 Migrate from NextAuth Next Steps After migration, review clerk-prod-checklist for production readiness.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clerk-migration-deep-dive