Move from Replit: step-by-step migration guides

Your app's code. The frontend and the server code.
Your GitHub repository. You push it from the Git pane, and it is yours.
Your data. The Replit database is PostgreSQL, so a backup restores into any PostgreSQL database.
Your custom domain. You'll just need to point it to the new host.

Replit Auth logins. They work only on Replit. After a move, people sign up again.
Files in App Storage. You copy them to new storage.
API keys and secrets. You copy them from Replit Secrets.
Your replit.app address. That stays with Replit.
Replit Agent chat history. It doesn't come with your code.

Our guides walk you through four stages

Answer a few questions to get steps tailored to your app.

Set up the accounts and tools needed for migration.

Follow the instructions and check the result of each step.

Test everything before switching. Your Replit app stays online until you're ready.

Back up the database first
Copy the production database with pg_dump before you change anything. The published app uses its own production database, not the one in your workspace.
Push the code to GitHub
Use the Git pane in Replit. You want a version you can go back to.
Write down every secret
Open Secrets in Replit and note every name. Your computer and the new host need all of them.
Check who controls the domain
If the domain is connected to Replit, find the registrar login. You will change DNS at the end.