Base44 migration guides: export, sync and move your app
Export your Base44 code, sync it with GitHub, run it locally, move the data out, and migrate the backend to Supabase or your own hosting.
Start here
Leaving or extending Base44: the export and migration guide
What you can take out of Base44 and what stays: exporting code, GitHub sync, data export, and migrating the backend to Supabase or your own hosting, step by step.
Read the guide7 more guides
-
Using Claude Code, Cursor or Codex with a Base44 app
Three ways to bring Claude Code, Cursor or Codex to Base44: GitHub sync, the app's cloud sandbox via the CLI, or the Base44 MCP server. Plans, setup and trade-offs.
-
How to export your Base44 code (ZIP, GitHub or CLI)
Three ways to export Base44 code: download a ZIP, sync to GitHub, or eject with the CLI. What each includes, which plan you need, and what the export can't take with it.
-
Exporting your Base44 data, users and files
Export Base44 data table by table to CSV, get your entity schemas and users out, download uploaded files, and use backups and recently deleted records.
-
Base44 GitHub integration: how two-way sync works
How to connect a Base44 app to GitHub, how two-way sync behaves, the rules that catch people out, and how Base44's GitHub import works for existing repositories.
-
Running a Base44 app locally with the Base44 CLI
Run a Base44 app on your own machine: clone from GitHub or eject with the CLI, link it, and use base44 dev. What runs locally, what's forwarded, and the remote-mode trap.
-
Self-hosting a Base44 app on Vercel, Netlify or Cloudflare
Build an exported Base44 app and deploy it to Vercel, Netlify or Cloudflare. What keeps working on Base44's backend, what breaks, and the SEO step people forget.
-
How to migrate a Base44 app to Supabase
Move a Base44 app to Supabase: turn entities into tables, import the data, move users, replace Base44 SDK calls, and port backend functions and integrations.