Keep Replit-built internal tools on Replit with a named owner, and move apps that serve customers or need company systems into your repositories, review, and hosting. Replit's own guide to moving a live app names its database and web address as the slowest parts, so copy and verify the data before you switch traffic.
When you need this
- A Replit-built tool now serves customers or holds data the company depends on.
- Engineers are asked to support an app they did not build and cannot find the code for.
- Hosting charges for apps that are rarely used keep recurring.
- An app needs integrations, scale, or review that the builder cannot provide.
Handoff plan
Decide whether it moves
Does the app serve customers, hold sensitive data, or need your review and release process?
HowMove an app once it serves customers, holds data you would have to disclose, or needs company systems. Rokt keeps all its Replit apps internal behind single sign-on, and its adoption lead says Rokt would consider rebuilding a tool inside its core infrastructure once the whole company depended on it. Will Cheung, who ships on Replit, notes limited logging and the need to review large changes. One builder who paid US$300 in a month of Agent fixes now edits in VS Code over SSH with Claude and keeps only hosting on Replit, inside the US$25 plan.
Get the code into Git
Is the full history in a repository your team controls?
HowEvery checkpoint is a Git commit that can sync to GitHub. On Enterprise, Require Git remote enforces it before publishing. Agent can also work on an imported GitHub repository and open a pull request, so changes after the handoff go through your review.
Move the data deliberately
Where is the production data, and how will it be copied and verified?
HowCopy the production database, verify the copy, and only then switch traffic. The production database is separate from the development database and is billed by compute hours and storage. Replit's own guide for copying a live app between workspaces names the database and the web address as the slowest parts and plans for 15 to 60 minutes offline. Plan a similar window for a move to your own hosting.
Replace what Replit provided
Which Replit services does the app depend on?
HowList the Replit Auth, App Storage, Secrets, Replit-managed AI integrations, and scheduled deployments the app uses, and choose replacements before the move. Agent-built apps need a backend deployment, so plan for server hosting. A static host will not run them.
Assign ownership after the move
Who reviews and releases changes from now on?
HowGive the app a repository owner, CI, and pull request review like any other service. Write down how the app was built while its builder is still around. Builders who hand off this way, such as sgt101 on Hacker News, used Replit to reach about 90% and finished the rest in Cursor. Rokt's adoption lead names the risk of skipping it: "If that person leaves the company after developing a valuable tool, how does somebody else pick that up easily and know the context?"
Decision rules
- Does this app serve customers or hold data we would have to disclose if it leaked?
- Is its code in a repository we control, with history?
- Which Replit services must be replaced, and by what?
- What does the app cost to run on Replit today, from the usage page?
- Who owns the app after the move, and who approves its changes?
Red flags
- Customer-facing apps with code only inside a personal Replit project.
- Development data copied into production during a move.
- A move planned without listing the Replit services the app depends on.
- Local git commits mixed with Agent's own git operations on the same project, which left one practitioner in a loop they were unable to reset.
Products in this piece
Sources
- Official documentation
- 8
- Public source
- 6
- Replit docs: Checkpoints and rollbacks
- Replit docs: Source control settings
- Replit docs: Contribute to a GitHub project
- Replit docs: Import from a provider
- Replit docs: Development and production databases
- Replit docs: Publishing and database billing
- Replit docs: Deployment types
- Replit docs: Manually copy a project to another workspace
- Will Cheung, DEV Community: I Built and Deployed a Micro-SaaS in 3 Hours (published Aug 31, 2025)
- vcast on Hacker News: US$300 in a month of fixes, then Claude in VS Code over SSH (published Oct 20, 2025)
- sgt101 on Hacker News: Replit reached about 90% and Cursor finished it (published Jul 25, 2025)
- mannanj on Hacker News: local git commits conflicting with Agent's own git operations (published Jan 9, 2026)
- John Charette: Switching from Replit to Claude Code (YouTube, published Mar 10, 2026)
- Jan-Erik Asplund, Sacra: Replit customer at Rokt on internal tool development and cross-team adoption (published Sep 12, 2025)