Move your Replit project into EzCoder
Replit gives you two ways out and both work here. The Replit-specific configuration is not something you have to hunt down by hand; the importer targets it during the import.
Getting the code out
What the export contains: Whatever you built — but EzCoder runs Node.js projects, so a package.json is the thing to check for first.
- Either push the Repl to a GitHub repository, or download the project as a .zip archive.
- Check that the project root has a package.json. EzCoder runs Node.js — a Python or Go Repl is detected and refused rather than imported into something that cannot run it.
- In EzCoder, choose GitHub for the repository or ZIP upload for the archive.
Import source to choose in EzCoder: GitHub or ZIP upload. 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.
Replit Secrets stay in Replit
Secrets you set in Replit’s panel are injected at runtime and are not part of the files. They do not travel with a Git push or a ZIP. EzCoder reads the variable names your code refers to and asks you for the values, which are then stored encrypted and injected the same way at runtime — the AI never sees them.
The Replit files EzCoder targets
EzCoder recognizes a Replit project by these marker files, and these are the Replit-specific paths it targets for removal so you do not inherit config for a platform you have left.
Recognized by.replitreplit.nix
Targeted for removal.replitreplit.nix.config/replit.cache
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
- Your source. The Replit config paths listed above are on the importer’s cleanup list; the result screen itemises which of them actually went.
- A dependency install driven by your package.json.
- A list of the environment variables to re-enter.
Coming from somewhere else
Bring it over
Import is open on every plan, including the free one.