Every builder has
a different exit.

Exporting code is not the same as moving the backend. Base44 documents GitHub sync on Builder plans and above, and an SDK through which app code calls managed authentication, entities and backend services.

WHAT USUALLY MOVES

Source code via GitHub sync or ZIP export (plan-dependent), plus table data exported as CSV.

WHAT WE CHECK

Every Base44 SDK call, data completeness, user account continuity, file storage, backend functions, and whether the app runs with Base44 credentials removed.

Lovable explicitly documents exporting code, moving data and migrating its Cloud backend toward customer-managed infrastructure, including Supabase-compatible options. The complete move is still more than a Git push.

WHAT USUALLY MOVES

Source code, database contents and a documented path for the backend.

WHAT WE CHECK

Auth sessions, stored files, database policies, server and edge functions, OAuth redirect URIs, webhooks, connectors, AI gateways and production cutover.

Bolt.new projects are typically standard web code that can be downloaded or synced to a repository. The backend varies from project to project, so we confirm where your data, logins and server logic actually live.

WHAT USUALLY MOVES

The web project source, plus data from whichever database service the app is connected to.

WHAT WE CHECK

Connected database and auth provider, environment variables, serverless functions, file storage and build settings for your chosen host.

Replit provides code-oriented development tools and a PostgreSQL database. Export and deployment details depend on each project’s runtime and services. Replit has also documented stronger safeguards after an AI-agent database incident in 2025.

WHAT USUALLY MOVES

Project source code and PostgreSQL data, using conventional tooling.

WHAT WE CHECK

Independent database backup, dev/prod separation, rollback, Git repository access, runtime requirements and a reproducible deployment.

Emergent documents saving code to GitHub on Standard plans and above, copying code on other plans, and exporting MongoDB data through database tools. Code export excludes secrets and database contents, which are handled separately.

WHAT USUALLY MOVES

Source code via GitHub or copy, and MongoDB data via a separate export.

WHAT WE CHECK

A fresh MongoDB dump and restore, object and file storage, configuration and secrets handoff, and a deployment that starts outside Emergent.

Bubble apps run on Bubble’s own visual engine rather than as a standard codebase you can export. Leaving usually means a partial or full rebuild, with your data carried across.

WHAT USUALLY MOVES

Your data and your app’s logic and design, used as the blueprint for a rebuild.

WHAT WE CHECK

Data export options, workflows and plugins in use, user accounts, and whether a rebuild is the right call for your business.

Glide is a no-code platform, so there is no conventional codebase to export. Your data often lives in Glide’s own tables or in a connected source such as a spreadsheet, which makes the data side of a move more approachable.

WHAT USUALLY MOVES

Your data, plus the screens and actions as the specification for a rebuild.

WHAT WE CHECK

Where each table lives, user access rules, integrations and automations, and the simplest stack that replaces it.

Built somewhere else, or not sure what your app is running on? Tell us about it. We’ll let you know whether we can help now, or when we can.

WHAT WE NEED

The platform name (if you know it), a link to the app or project, and what the app does.

WHAT YOU GET

A straight answer on whether we can move it, and when.