Vibe Code Forum teamAdmin
Most people start in one place and move as their project grows. Moving is normal, not failure, and it is easy if you plan for it.
Signs it is time to move
- Each change takes several attempts and breaks something else.
- You are spending more on credits fixing things than building new ones.
- You need something the tool doesn't support: a particular payment provider, a background job, a different database.
- You want to understand and own what you built.
Before you start: get your code out
- Connect GitHub in your current tool (most app builders support it) or download the project as a zip.
- Check the repository has everything: open it on GitHub and look for a
package.json(JavaScript projects) orrequirements.txt/pyproject.toml(Python). - Note every service the app uses (database, sign-in, payments, email) and where its keys are set. You will need to set them again. See Environment variables and .env files.
Moving to an editor or agent
- Clone the repository to your computer. See Git and GitHub explained.
- Open it in your AI code editor or start a terminal agent in the folder.
- First prompt: "This project was built in another tool. Explain its structure, how to run it locally, and which environment variables it needs." Then follow its steps until it runs on your computer exactly as before.
- Create a
.envfile with your keys (not committed to Git), run it, and check every feature. - Commit. You now own the project.
Moving hosting
App builders often host for you. When you move, you will set up hosting yourself. See Vercel, Netlify and friends and the going live checklist.
Going back and forth
You can keep using an app builder for quick design changes and an editor for logic, as long as both work on the same GitHub repository and you pull the latest changes before each session. Make one change at a time in one place to avoid conflicts.