Move your Lovable project into EzCoder
Lovable projects live in a GitHub repository once you connect one. That makes this the cleanest of the four migrations: EzCoder reads the repository, so there is no archive to download and nothing to upload.
Getting the code out
What the export contains: React with TypeScript, built by Vite.
- Connect your Lovable project to GitHub, if it is not connected already. Lovable pushes the project into a repository you own.
- Confirm the repository has your latest work in it — the code EzCoder imports is the code in the repo, not the code in the Lovable preview.
- In EzCoder, choose GitHub as the import source and authorize access to that repository.
Import source to choose in EzCoder: GitHub. Platform interfaces change; if a control has been renamed since this page was written, look for the action that gives you the outcome each step describes.
The Lovable files EzCoder targets
EzCoder recognizes a Lovable project by these marker files, and these are the Lovable-specific paths it targets for removal so you do not inherit config for a platform you have left.
Recognized by.lovable/lovable.json
Targeted for removal.lovablelovable.json
This page is the same for everyone, so it can only tell you the list the importer carries. Anything actually removed from your project is itemised on the import result screen when the import finishes. If that screen itemises nothing, nothing was removed — the files above are still in your tree, and deleting them is a one-line ask to the AI once the project opens.
node_modules, .git, dist, build and .next are dropped as well, for every import regardless of platform.
What you get on the other side
- A React and TypeScript tree on Vite, which EzCoder runs as-is.
- Any Supabase project you were using is detected but not connected. You supply the credentials.
- Tailwind config, components and routes arrive unchanged.
Coming from somewhere else
Bring it over
Import is open on every plan, including the free one.