Already built it somewhere else? Bring it here.
EzCoder imports an existing project from a GitHub repository or a .zip archive, targets the platform-specific config for removal, works out which services it depends on, and opens it in the editor. Here is exactly what that means, including the parts it will not do for you.
Before you start
What the import does
Automatic
- Takes your code from a GitHub repository or a .zip archive.
- Drops the dead weight on the way in — node_modules, .git, dist, build and .next never reach the project.
- Recognizes which of the four builders your project came from by its marker files, and carries a cleanup list of that platform’s own config files. Anything an import removes from your project is itemised on the result screen when it finishes — if nothing is itemised there, nothing was removed.
- Reads the NAMES of the environment variables your code refers to, so you get a checklist instead of a blank page.
- Detects the services you were using — Supabase, Stripe, auth providers, storage, email — and tells you which ones still need credentials before the app will run.
What it does not do
Yours to finish
- It does not bring your secrets. API keys and passwords are never read out of a .env file, by design — you add them again in EzCoder, encrypted.
- It does not port a non-Node project. EzCoder runs Node.js; a Python, Go, Ruby or Rust project is detected and refused rather than half-imported.
- It does not rewrite your app to work here. What arrives is your code, as it was written, in an editor with an AI that can then change it with you.
- It does not scrub every trace of the old platform. It removes that platform’s own config files; a reference to it inside your source is still there afterwards, and changing that is a job for you and the AI.
- It does not connect your databases or third-party services for you. It finds them and asks you for the credentials.
- It does not take unlimited size. Archives cap at 500 MB and project source at 50 MB — enough for essentially any front-end app, not enough for a repository with media checked into it.
Where are you coming from?
Each platform hands you your code in a different shape, and leaves a different amount of itself behind. Pick yours for the specifics.
Replit
Push to Git or download the archive. Replit’s own config files are targeted on the way in.
Secrets re-entered by handGitHub repoLovable
Connect the GitHub repository Lovable writes to, then import the repo directly.
ZIP or GitHub, paid planBase44
Exportable on a paid plan — but the export is still wired to Base44 and will not run standalone.
Needs rework after exportZIP downloadBolt
Download the project as a ZIP and upload it. A plain Vite, React and Tailwind tree.
Secrets re-entered by handHow the import runs
You choose a source: a GitHub repository, or a .zip archive you upload. EzCoder pulls the files, skips the package directories and build output, and applies the cleanup list it carries for whichever platform it recognizes. The result screen at the end itemises anything that was removed, so that screen — not this page — is the record of what happened to your tree.
It then reads the project rather than guessing at it. It works out the runtime, the environment variables the code refers to, and the third-party services it talks to, and turns that into a short list of what still needs a credential. Anything blocking is flagged before you open the editor, not after.
Then the project opens, with a live preview and an AI that can see the whole codebase. At that point it is a normal EzCoder project.
Import is available on every plan. Publishing an imported project to a live URL requires the Creator plan or higher.
Questions, answered.
Bring your project over
Import from GitHub or a .zip archive. Free plans included.