Move your Base44 project into EzCoder
This is the migration that needs the most work, and it is worth being blunt about why before you start. Getting the files out is the easy half.
Getting the code out
What the export contains: A React front end that talks to Base44’s hosted backend through their SDK.
- Export from Base44 as a ZIP download, or sync the project to a GitHub repository. Both routes require a paid Base44 plan — there is no export on the free tier.
- In EzCoder, choose ZIP upload for the archive, or GitHub if you synced a repository.
- Expect to spend time after the import replacing the Base44 backend calls. Ask the EzCoder agent to do it — that is exactly the kind of change it is built for.
Import source to choose in EzCoder: ZIP upload or 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 export is still pointed at Base44
A Base44 export is not a standalone application. It carries @base44/sdk imports, a base44.config file and BASE44_API_KEY-style references, and every one of those still calls Base44’s servers. Move it anywhere — here or a laptop — and the front end renders while the data layer talks to a backend you are trying to leave. EzCoder detects all three signals on import and reports them instead of pretending the app is ready. Removing the config file does not change this: the SDK imports live in your source and only a rewrite removes them. Replacing that data layer is real work, and the agent can do most of it, but plan for it rather than being surprised by it.
The Base44 files EzCoder targets
EzCoder recognizes a Base44 project by these marker files, and these are the Base44-specific paths it targets for removal so you do not inherit config for a platform you have left.
Recognized by.base44/base44.config.js
Targeted for removal.base44base44.config.js
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 React front end, components and styling, unchanged.
- An explicit report of the Base44 SDK usage, config and API-key references found in the code.
- A project that needs its data layer rebuilt before it runs on its own.
Coming from somewhere else
Bring it over
Import is open on every plan, including the free one.