Turn your app
into a business.

Code

1. In your Lovable project open Project settings → Git → GitHub and connect it. Lovable creates a repository and keeps it in sync.
2. Connect that repository to GO. On paid plans you can also download the codebase and upload the ZIP.

Data

1. Using Lovable Cloud? Export your data under Cloud → Advanced → Export data (up to 5 GB, once a day). The download link arrives by email.
2. Upload the export when GO asks for it.

Good to know

• Storage files and secrets are not part of the export. GO lists what is missing and asks you for it in a secure field.

Code

1. Click the GitHub icon in Bolt and create a repository, then connect it to GO.
2. Or use Export → Download and upload the ZIP.

Data

1. Bolt Cloud database: export each table as CSV or JSON from the Database view and upload the files.
2. On Pro and Teams plans you can also claim the database into your own Supabase organization — then follow the Supabase guide.

Good to know

• Values under Database → Secrets aren't exported. You enter them in GO.
• Server functions are set up again on the new home.

Code

1. Connect your v0 project to GitHub (v0 syncs on a v0/* branch), then connect the repository to GO.
2. Or export the version you want as a ZIP and upload it.

Data

1. A database added through the Vercel Marketplace lives with its provider (for example Neon, Supabase or Upstash). Enter that provider's connection string in GO's secure field.

Good to know

• Environment variables live in your Vercel project — see the Vercel guide.

Code

1. Open the Git pane in your Repl, connect GitHub and push. Then connect the repository to GO.
2. Or download the project as a ZIP (up to 200 MB) and upload it.

Data

1. Production database: copy the connection URL from Database → production → Settings and enter it in GO's secure field.

Good to know

• Secrets are not copied with the project — you enter them in GO.
• Replit-only services such as Replit Auth or Replit DB don't move as they are. GO replaces them and tells you what changed.

Code

1. Connect GitHub from your Base44 app, or export the code as a ZIP (Builder plan and above).

Data

1. Export your data as CSV, one file per entity, and upload the files.

Good to know

• Base44 apps call Base44's own SDK for data and sign-in. GO rewires those calls, so this move takes longer than a plain repository.

Code

1. Turn on the GitHub backup under Integrations → GitHub, or download the code — depending on your plan.
2. Connect the repository to GO, or upload the ZIP.

Data

1. Ask Macaly support for a snapshot of your database and upload it when GO asks for it.

Good to know

• Macaly's built-in database and sign-in are replaced during the move.

Code

1. If your service deploys from GitHub, connect that repository to GO.
2. Deployed with the Railway CLI only, without a repository? Contact us.

Data

1. Postgres, Redis or MongoDB: copy the public connection URL (through Railway's TCP proxy) and enter it in GO's secure field.

Good to know

• Files on volumes can only be copied through a running service — contact us if your app stores files there.
• Variables marked as sealed can't be read back. You enter them in GO.

Code

1. Connect the GitHub repository your Render service deploys from.

Data

1. Postgres: enter the external connection URL in GO's secure field, or upload a Render Postgres export (.dir.tar.gz).

Good to know

• Files on persistent disks aren't included — contact us if your app uses one.

Code

1. If the project deploys from Git, connect that repository to GO.
2. Deployed from the CLI without Git? Contact us.

Data

1. Databases added through the Vercel Marketplace live with their provider. Enter that provider's connection string in GO's secure field.

Good to know

• Sensitive environment variables can't be read back from Vercel. Enter them in GO and rotate them afterwards.

Code

1. If the site deploys from Git, connect that repository to GO.
2. Deployed by drag and drop or from the CLI without Git? Contact us.

Data

1. If your site uses a separate database, follow the guide for that service.

Good to know

• Environment variables marked as secret can't be read back. Enter them in GO.

Code

1. Connect the GitHub repository your app deploys from. If you only push to Heroku Git, push the code to GitHub first.

Data

1. Copy DATABASE_URL from Settings → Config Vars and enter it in GO's secure field.

Good to know

• Data kept inside add-ons stays with the add-on provider — contact us if you rely on one.

Code

1. Connect the repository with your app's code. Edge Functions kept in the repository (supabase/functions) come along with it.

Data

1. Copy the database connection string from your Supabase project and enter it in GO's secure field. Tables, data, row-level security policies and scheduled jobs come with it.
2. Sign-in users live in your database, so they move with the data. Storage files are copied separately.

Good to know

• Secret values and sign-in provider settings can't be read from Supabase. You enter them in GO.

Code

1. Firebase Studio: use Move now → GitHub or Zip & Download, then connect the repository or upload the ZIP.
2. Other Firebase apps: connect the repository with your app's code.

Data

1. Firestore, Authentication users and Storage each have their own export. Contact us and we'll walk you through it.

Good to know

• Security rules and triggers are rebuilt on the new home. GO shows you what changed.

Code

1. Connect GitHub, pick the repositories GO may read and install. Access is read-only and limited to those repositories.
2. Built in Cursor, Claude Code or another editor? Push to GitHub first.

Data

1. If your app has a database, GO asks for a connection string or an export file — always in a secure field.

Good to know

• If GO finds keys committed in your repository, it tells you, so you can revoke them and enter new ones in GO.