How to move a Replit, Bolt, Lovable, Base44 or v0 project to GitHub, or download it as a ZIP

    Each of the five big AI app builders can push your project to a GitHub repository, and four document a ZIP download. This guide gives the steps from each builder’s own documentation, the plan each step needs, and what stays behind in the builder: your database rows, your secrets and your users. The last section covers what to do with the code once it is on GitHub, including turning it into native iPhone and Android apps.

    The short answer. In Replit, open the Git tool in the project and connect a GitHub repository. In Bolt, click the GitHub icon at the top right. In Lovable, open Project settings → Git → GitHub. In Base44 (Builder plan or higher), click the GitHub icon in the dashboard. In v0, open the project menu → Settings → GitHub. Each of these keeps the repository in sync with the builder.

    What reaches GitHub is the app’s code. The data in your database, your secrets (API keys) and your app’s users stay in the builder or in your backend service, so plan for them separately.

    Before you start: what moves and what stays

    You need a GitHub account. The repository receives the code; three things stay behind.

    Data. Lovable’s docs say the repository holds migration files "but never the data inside your database." Base44’s docs: "Your app’s data isn’t included." Base44 lets you export each table as CSV from the Data section.

    Secrets. Lovable: "Secrets you store in Lovable stay out of the repository." Base44: "Your secrets and app users aren’t included."

    Running services. Code exported from Base44 still calls Base44 for data, logins and functions, and "Base44 doesn’t support self-hosting." Lovable does not deploy Edge Functions or database migrations when commits sync.

    Write down where your backend lives (Supabase, Firebase, the builder’s own cloud or your own API) before you export. A new host, or a mobile app built from the code, connects to that same backend.

    GitHub and ZIP, builder by builder

    BuilderConnect GitHubSyncPlan for GitHubDownload as ZIP
    ReplitAccount connected services, then Tools → Git in the projectTwo-way with auto-sync onNot stated for github.comFile tree three-dot menu → Download as zip
    Bolt.newGitHub icon, top right → install the GitHub App → Create repositoryTwo-way; Bolt checks GitHub every 30 secondsNot statedProject title, top left → Download (desktop only)
    LovableProject settings → Git → GitHub → ConnectTwo-way, one branchAll plans (github.com)Project settings → Git → Download codebase (paid plans)
    Base44Dashboard → GitHub icon → Connect to GitHub → Create RepositoryTwo-way, automaticBuilder plan or higherMore actions → Export project as ZIP (Builder plan or higher)
    v0Project menu → Settings → GitHub → Create RepositoryWorking branch and pull requests, both directionsNot statedFrom the project menu; steps not documented

    From each builder’s documentation, read 5 November 2026. "Not stated" means the pages read do not say.

    Replit to GitHub

    Replit’s docs: "Link your GitHub account from your account’s connected services, then open the Git tool in your project and connect the repository."

    1. In Replit, link GitHub under your account’s connected services.
    2. In the project, open Tools → Git. If the project has no repository yet, click Initialize Git Repository.
    3. Connect the GitHub repository, then click Push updates to send your code.
    4. Turn on auto-sync in the Git pane for two-way syncing.

    Replit’s pages do not state a plan requirement for github.com. GitHub Enterprise Server, GitLab Self-Managed and Bitbucket Data Center need Replit’s Enterprise plan. Pushing from the Shell with git commands needs a GitHub personal access token.

    Download a Replit project as a ZIP. In the file tree, open the three-dot menu at the top and choose Download as zip. If the download fails, Replit suggests running zip -r project.zip . in the Shell. Secrets and the database are not project files: for a project copied to another account, Replit’s docs say to "set up secrets, the database, and deployment configuration in the new project".

    Bolt.new to GitHub

    1. Click the GitHub icon at the top right of the project.
    2. Log in to GitHub, click Authorize, and install the GitHub App for all repositories or only selected ones, then click Install & Authorize.
    3. Enter a repository name and click Create repository.

    Bolt’s docs: "The repository starts as private, on a main branch." Bolt "checks GitHub every 30 seconds for any updates made outside Bolt and pulls those in", so edits made in GitHub come back into Bolt. Only the project owner can connect the integration. A disconnect is permanent, and only Bolt support can reconnect it. For a GitHub organization, an org admin installs the GitHub App first. Bolt’s docs do not state the plan needed.

    Download a Bolt project. Click the project title at the top left, then Download. Bolt’s docs: "You can’t currently download a project from a mobile device." To run the download on your computer, unzip it and run npm install && npm run dev.

    Lovable to GitHub

    Open Project settings → Git → GitHub (or the + button next to the chat → Project → GitHub), add your GitHub account, install the Lovable GitHub app, and click Connect. Lovable "creates a new GitHub repository and starts two-way sync automatically." Sync with github.com is "available on all plans".

    Two limits from the same page: "Git sync always creates a new repository", so you cannot attach an existing one, and reconnecting creates another new repository. On paid plans, Download codebase in Project settings → Git gives you the files directly. The full Lovable walkthrough, with what the export contains, is in how to download a project from Lovable.

    Base44 to GitHub

    Base44’s docs: "Connecting to GitHub requires a Builder plan or higher."

    1. In the dashboard, click the GitHub icon at the top right, then Connect to GitHub → Connect GitHub → Authorize Base44 Builder.
    2. Pick the account and repositories, click Install, enter a repository name and click Create Repository.

    The sync is two-way and automatic. Base44’s docs: "There’s no option to manually push updates from your Base44 app to GitHub." The default branch must be main. You still click Publish in Base44 to put changes live, and versions from before the connection cannot be restored.

    Download a Base44 project as a ZIP. Click the More actions icon at the top right of the editor → Export project as ZIP → Download ZIP. "ZIP export is available on the Builder plan and higher." The ZIP has no data, secrets, users or version history, and the code keeps calling Base44 for data and logins. Publishing a Base44 app to the stores is covered in how to publish a Base44 app to the App Store.

    v0 to GitHub

    Open the project menu (…) → Settings → GitHub, click Connect, choose your account or organization, enter a repository name and click Create Repository. v0 "creates a private repository and pushes the project’s current code to it."

    v0 pushes its changes to a working branch and "never pushes directly to main". Publish opens or reuses a pull request and merges it, and Pull Changes brings commits from the base branch back into v0. Branch protection rules on the repository can block Publish, and deleting the repository can make the code unrecoverable.

    v0’s docs do not state the plan needed or the ZIP steps. A changelog entry from 19 June 2026 says view-only members "can download a chat’s code as a ZIP from the project menu."

    No GitHub button? Upload a ZIP to GitHub

    If you have a ZIP but no GitHub connection, upload the files yourself.

    1. On GitHub, open the + menu at the top right → New repository. Choose the owner, enter a name, pick Public or Private, do not add a README, and click Create repository.
    2. Unzip the project on your computer.
    3. In the new repository, click Add file → Upload files, drag the files and folders in, write a short message and commit.

    GitHub’s limits: "Files that you add to a repository via a browser are limited to 25 MiB per file," and you can upload up to 100 files at a time, so a larger project goes up in several batches. GitHub’s push protection blocks files that contain secrets, such as an .env file with API keys; leave those out.

    From GitHub to a native iPhone and Android app

    A repository is the input most next steps take. People usually do one of three things with it: host the web app somewhere else, wrap it for the app stores with Capacitor, or rebuild it as a native mobile app on the same backend.

    For the native route, paste the repository URL into Modaal on Website to app. Modaal reads the code as the reference and writes a migration plan you review. Your own AI agent then builds SwiftUI screens for iPhone and Jetpack Compose screens for Android, flow by flow, connected to the backend your web app already uses. Modaal runs on a Mac.

    Frequently asked questions

    Keep reading

    Your code is on GitHub. Turn it into native iPhone and Android apps.

    Paste the repo URL. Modaal writes a migration plan, and your own AI agent builds SwiftUI for iPhone and Jetpack Compose for Android on the backend you already have.