Bringing things in

Bring your code

A zip in: what goes to the website, what goes to the Vault, what is left out.

Updated 12 Oct 2026

Code you already have (a Lovable export, an old site, any website) comes in as a zip: Import a zip on the new-project page, or later Apps › Website › Settings › Bring in a website (the owner's). It goes into the website's folder in one commit, as it is.

Before anything is uploaded

The page reads the zip in your browser and shows what goes where:

  1. The website: the folder with the site in it, and what it is built with. It goes into the website's box and is put online. No website found means the code goes into the repo and nothing goes online from it.
  2. Keys to the Vault: a .env is never committed; its keys go to the Vault under the names they had. A key file (a keystore, a service account) is kept in the Vault whole.
  3. Left out: installed packages, git history and build output.

Then Bring it in: the site rebuilds from it, and Flexi has the first word on what he made of it.

Where next

Still stuck? Ask Flexi in your project, or ask a flexpert.