This automated migration is for apps that use Replit Auth. If your app uses a different authentication system, do not use this flow.
Start the migration
Agent migrations should always run in a new task. You can start the migration in either of these ways:Start from Main Agent
- In the main Agent conversation, ask Agent to migrate your app from Replit Auth to Clerk.
- Agent proposes a separate migration task for you to review and start.
Start from Auth Pane
- In the Project Editor, open Tools and select Users & Auth.
- In the Introducing a new Replit Auth banner, select Update now.
- Select Ask Agent to migrate.
What Agent does
Agent completes the migration in this order:- It moves your Replit Auth user data to Clerk, including account identity details and supported sign-in credentials.
- It waits for the data migration to finish before changing your app.
- It updates your app’s sign-in and session logic, restarts the app, and runs available automated checks.
Your app data stays in place
Agent changes only your app’s authentication code. It does not update your app’s existing database data or schema. Your tables and relationships remain intact. Your existing users remain connected to the records they already own, such as profiles, saved work, and permissions.How long it takes
Expect Agent to work for 10 minutes to an hour. The data migration itself can take several minutes for smaller apps and up to a couple of hours for apps with many users. Agent does not begin changing your app’s code until that migration completes.After the migration
Before publishing, test the updated app in Development:- Sign in with an existing account and confirm its saved data is available.
- Sign out and sign back in.
- Create a new test account and confirm it can use the app as expected.
Additional resources
- Clerk Auth overview — How Clerk Auth works on Replit