How to transfer a Lovable or Bolt project to another account or developer

You can transfer a Lovable project to another account in three ways. You can transfer ownership to a member of your workspace, or, on Business and Enterprise plans, to an outside account by email. You can move the project to another workspace you belong to. Or you can remix it into a copy. Bolt offers a transfer and a duplicate. Each option keeps different things: the database, the Git connection, payments, collaborators and the AI chat history do not always follow the project.

This guide is for founders and product owners handing an existing customer-facing app to a developer, or moving it into the company’s own account. It covers what each option keeps and drops, what blocks a transfer, how to keep the decisions made in the AI chat, and what evidence to ask for before the previous developer loses access. For the wider question of whether another team can run the product, read Can another team own your AI-built product?.

Answer in 60 seconds

  • Lovable: transfer ownership inside the workspace, move the project to another workspace, or remix it. Only Business and Enterprise plans can transfer ownership to an outside account.
  • Bolt: a move between your own workspaces keeps the database, GitHub and Supabase. A transfer to another user removes GitHub; the Supabase account stays with its owner.
  • A new developer does not need to own the project. If the company controls ownership and billing, give the developer the role the work needs.
  • Copies often lose the AI chat: a Lovable remix by default, a Bolt duplicate and a Replit manual copy. Keep a checked record of accepted decisions, without secrets or customer data.
  • Before an irreversible move, clear payment and domain blockers, take backups and agree how the developer will prove they can deploy, restore and protect private data.

In this article

  1. Decide what needs to change before transferring
  2. Transfer a Lovable project to another account or workspace
  3. Transfer or duplicate a Bolt project
  4. Replit, v0 and Base44: transfer conditions to check
  5. Keep the decisions from the AI chat, without the secrets
  6. Move the backend only if needed, and test private data
  7. Accept the handover against evidence

1. Decide what needs to change before transferring

Giving a developer access, changing the owner, moving a project to another workspace, copying it and migrating the database are different operations. Start with one sentence both sides can approve, for example: “The company keeps the current backend; the new developer needs access to maintain it.”

What needs to change Operation to consider Question to settle first
A new developer maintains the existing app Invite the developer or change their role Does the company already control ownership, billing and account recovery?
The wrong person owns the project Transfer ownership Is the recipient eligible, and who keeps access afterwards?
The project belongs in a company workspace Move to another workspace Which payments, connections and collaborators change?
A separate version is needed Duplicate or remix Which data, history and live connections does the copy take?
Development or hosting leaves the platform Export the code, and migrate the backend as a separate project if needed Must data, user accounts and files move too?

Then list every service the app uses (repository, database, sign-in, files, hosting, domain, payments, email, scheduled jobs) with its company-controlled owner, billing contact and planned destination. Record where each secret is stored, never its value.

Do not commission a rebuild only because a developer is taking over. IZZY’s Rescue service starts with an audit before deciding what to refactor or rebuild. In our experience, the larger problem in AI-built code is missing structure and verbose, tangled logic rather than individual wrong lines: a reason to inspect before deciding, not to start again.

2. Transfer a Lovable project to another account or workspace

Lovable’s project settings offer two operations, and a remix adds a third.

Transfer ownership. The owner chooses a workspace member with the owner, admin or editor role; viewers, external collaborators and pending invitees are not eligible. A transfer to a member keeps the project in the same workspace. On Business and Enterprise plans, the owner can also enter the email of an account outside the workspace, and that person accepts a transfer request.

Move to another workspace. You can move a project only to a workspace you belong to. This changes billing and control, and it changes the most:

  • The Git connection is disconnected; the repository and its history stay in place. When you reconnect, Lovable links the same repository again if the destination workspace has a connection to the account that owns it (Git sync overview, GitHub page). On GitHub Enterprise Server or self-managed GitLab, or if the original repository was deleted, it creates a new one instead. Check which repository is linked after reconnecting.
  • If payments are configured, Lovable blocks the move until they are disconnected. Disconnection cannot be undone and checkout stops until payments are set up again. Active subscriptions keep billing at the payment provider, but the app stops receiving payment events.
  • Direct project collaborators and pending invites are removed, unless you tick the option to transfer them, the destination allows their role and you have permission to grant it there.
  • App connectors are disconnected and their stored credentials removed. The email sender domain is disconnected, and the access setting resets to the destination’s default.
  • The database, user accounts, storage, server functions, scheduled jobs and the secrets you saved yourself stay with the project; secrets stored by a connector are not included. Analytics history restarts from the move. The destination workspace pays for usage from the move onwards.

Remix into another account. On other plans, a remix gives the other person their own copy. Lovable’s remix page lists what it copies: the code, database structure, server functions, storage settings and secret names. It leaves behind secret values, database records, user accounts, scheduled jobs, custom domains, collaborators and service connections. A project cannot be remixed while payments are enabled, while it sends email from its own domain or while an online store is connected; an external Supabase project must be disconnected before a cross-account remix. The chat history comes along only if the person making the remix has edit access to the original and turns on “Include project history”. A remix made from the public link never includes it, and in a remix into another account the copy has no chat history or Files-tab files, because the destination account lacks edit access to the original.

The database export serves a move to a database you control. It includes user accounts and password hashes, so store it with restricted access. It does not include stored files, server function code, secrets, sign-in provider settings or API keys, and Lovable documents no self-service way to load it into another Lovable project.

3. Transfer or duplicate a Bolt project

Bolt’s project rules depend on who receives the project.

Between your own workspaces, the Bolt database, the Supabase integration and the GitHub integration stay connected. This move is also allowed on the Free plan.

To another user or team, either the sender or the recipient must have a paid plan. The Bolt database transfers and stays connected. GitHub is removed when the new owner accepts. Supabase settings move with the project, but the Supabase account does not change owner, so Bolt recommends transferring the Supabase project first.

Stop at the domain check. Custom domains do not transfer and must be removed first. A domain bought through Bolt cannot be reconnected until it expires, and Bolt advises against transferring such a project.

A duplicate is not an isolated copy. It starts with an empty chat history; Bolt suggests generating a summary of the chat before duplicating. The Stripe keys are copied, so both projects charge through the same Stripe account. A new Bolt database gets the same tables but no user accounts, user data, uploaded files, secrets or sign-in settings, and server functions are copied as files without being deployed. A project on its own Supabase can instead stay connected to the same live database. Review every connection before creating the copy.

4. Replit, v0 and Base44: transfer conditions to check

Platform Conditions to check before transferring
Replit Personal-to-team and team-to-team transfers are both irreversible. Team-to-team transfer needs one shared billing account, Owner access on the project and the Admin or Member role in the destination; an attached App Storage bucket blocks it. Linked Account Secrets do not transfer, and the transfer fails for a public deployment if the destination allows only private ones. In a manual copy, Agent conversations stay behind; exclude the .cache folder from any ZIP, as it holds cached secret values.
v0 Chats move between personal and team scopes, and the linked Vercel project follows if you are an Owner of its current team. Team Owners can read a moved chat’s full history. On Vercel, environment variables are copied except those in vercel.json; integrations must be added again, and logs, log drains and monitoring data are not transferred.
Base44 Direct transfer outside the workspace needs Business, Enterprise or approved Partner status, an owner or admin, and a workspace setting that allows it; the invitation expires after seven days. Otherwise, move the app to another workspace (you must own the current one, and you and the app owner need the editor role or higher in the destination), then change the owner. A move disconnects GitHub sync, custom connectors, bank account connections and SSO, and closes the app’s Google Ads account. The code export needs the Builder plan or higher, excludes app data, users and secrets, and still relies on Base44.

5. Keep the decisions from the AI chat, without the secrets

The chat can explain why a feature behaves as it does. It also holds abandoned instructions, failed fixes and requests that were never built. Handing over everything does not tell the next developer which decision still applies.

Keep the original project, with its chat, in a company-controlled workspace with restricted access. Give the developer a short record of accepted decisions, plus the extracts they need. For each decision, record the behaviour, the reason, the rejected alternative, who approved it, the code version and a test that confirms it. An AI-written summary is a starting point; a person must compare it with the conversation and with the current code. Microsoft’s guidance on decision records recommends recording context and rationale, and that is the useful principle here.

Hypothetical example, not an IZZY client case: a booking app keeps a cancelled slot blocked until a manager releases it, so equipment can be checked; automatic release was rejected. The record names the manager and links the cancellation code and a test with fictional bookings. If the current code frees the slot at once, the record flags the mismatch: the old chat does not prove current behaviour.

Before sharing any chat, attachment or code archive, remove customer identifiers, payment details, private messages and credentials, and run a secret scanner with masked output. Cursor warns that redaction of shared transcripts can miss secrets, so automatic redaction does not replace a review.

If a credential appeared in a chat, replace it in order: create the new one in the approved secret store, update the services that use it, test them, then revoke the old one and confirm the revocation.

6. Move the backend only if needed, and test private data

If the existing backend can stay under company control, leave it. If it must move, plan a separate migration: pause or reconcile new changes, take the final export, verify the destination and keep a tested way to restore service if the cutover fails.

A Supabase project transfer needs the owner of the source organisation and at least a member of the destination. Before the transfer, disconnect any active GitHub integration and remove log drains and, on Team and Enterprise plans, project-scoped roles. The region does not change; moving region needs a migration.

Then test who can see what. Public catalogue entries can be readable without signing in; private customer records must not be. On Supabase, row-level security must be enabled on every table in an exposed schema, and enabling it does not prove the policies are right. The publishable key (legacy: anon) can be read by anyone and reaches only what row-level security allows; the secret key (legacy: service_role) bypasses it and must stay on the server.

In a test environment with fictional data, record allowed and denied results:

  • A visitor can read the deliberately public records and cannot retrieve private ones.
  • Customer A can act on A’s records and cannot read or change customer B’s, including by changing a record identifier.
  • A staff role can do its documented task, and an ordinary customer cannot.

Include file downloads and server endpoints, not only what the interface shows. These checks cover only the tested scope, not the security of the whole app. For wider checks, see customer data isolation and how to scope a pentest and retest.

7. Accept the handover against evidence

Agree the evidence before the previous developer loses access. The receiving developer demonstrates each item with their own authorised account. In our takeover work, the defects that matter in AI-built code tend to appear in real customer journeys rather than in unit tests or code review, which is why the list ends with them.

Area Evidence to collect
Ownership and billing Company-controlled administrators, recovery contacts, invoices and a complete service list
Code and deployment A named version builds and deploys to a test environment from the authoritative repository
Database and files A backup restores in an isolated environment, with live email, payments and scheduled jobs off or sandboxed
Credentials and integrations New credentials work and old ones are revoked; sign-in, sandbox payments and test email succeed
Domain Registrar access is shown, or a harmless test record is added and removed
Private data Dated results of the agreed allowed and denied operations
Customer journeys Sign-up, sign-in, the main purchase or booking and cancellation run end to end on the new deployment

A restored database is only part of recovery: test the customer journey after restoring it. Remove the previous developer’s access, including recovery methods, only after acceptance. A backup cannot undo an irreversible ownership transfer.

Conclusion: transfer only what needs to change

Choose the operation first, clear its blockers and agree the evidence. Move only what must move, keep the reasons behind working behaviour, and check that the new developer can run the app without the previous one before paying for a rebuild.

Bring us the service list and one decision record

Bring the service and ownership list, plus one redacted decision record, to IZZY’s Rescue service. We use them to scope a fixed-quote codebase audit and the choice between keeping, refactoring and rebuilding. Raw AI chats, credentials and customer exports are not needed for the first conversation.

Frequently asked questions

Yes, within limits. Any plan can transfer ownership to a workspace member with the owner, admin or editor role; only Business and Enterprise can send a transfer request to an outside account. After a move to another workspace, that workspace pays for usage. A remix into the other person’s account is the remaining option, but it is blocked while payments, own-domain email or a connected store are active.

Invite them to the workspace with the editor role, or invite them directly to the project as a collaborator. Ownership and billing stay with the company. Only admins and owners can set up payments, and the person who originally set up the integration can also disconnect or switch it, so grant admin only if the work needs it.

Neither help centre, checked on 19 November 2026, describes a chat download. A Lovable remix copies the history only when the person remixing has edit access to the original and turns on “Include project history”. A remix into another account has no chat history, because that account lacks edit access to the original. A Bolt duplicate starts with an empty chat, and Bolt suggests generating a summary first. Keep a checked decision record separately.

No. The code describes the database structure but holds no records or user accounts. Those come from the database export, an archive for a database you control. A Base44 code export likewise excludes data and users, and still relies on Base44 to run.

Sources and limits

No transfer was tested hands-on; this guide relies on the vendor documentation linked in the text, checked on 19 November 2026. Recheck the chosen option on the day you act. IZZY’s observations come from our own takeover work, recorded on 13 October 2026, and are not a statistic. The guide reports no client case.

izzy.agency teamEngineering & product insights from the izzy.agency team.We use AI in our research and preparation. The analysis, the sourcing and the writing are ours. How we work