Skip to main content
Move your repository and Dockerfile, export your data and configuration, and replace the floo features your app uses. Verify the app on its new host before deleting it from floo. The steps below use my-app and prod; repeat them with --env dev for anything you keep from dev. Export everything before you delete the app: deletion destroys its databases, Storage buckets, and env vars.

Get the code

An app deployed from your GitHub repository already has its code there. A floo-hosted project (made with floo deploy --hosted) keeps its code in a repository floo hosts, which floo apps delete destroys. Clone it first:

Export the database

With floo db dump

Requires floo CLI v2026.11.10 or later (floo update). floo db dump runs your local pg_dump against the environment’s DATABASE_URL and writes the dump to a file. It needs pg_dump from PostgreSQL 17 or newer on your PATH and a WRITE-scoped floo API key.
--env is dev (default) or prod. --format is plain (default, SQL for psql) or custom (for pg_restore). The dump leaves out owners and grants, so it restores into any Postgres:
The file appears only when the dump succeeds; a failed run leaves no partial file. floo db dump reads DATABASE_URL only; dump a named Postgres service with pg_dump directly. Errors:

With pg_dump directly

floo env get prints DATABASE_URL as a standard Postgres connection URL, which pg_dump accepts as-is. This works with any floo CLI version:
--reveal-secrets prints the URL, password included. Run it only where the output stays on your machine. A named Postgres service has its own variable, such as DATABASE_URL_ANALYTICS for [managed.analytics]; dump each one.

Export Storage files

floo Storage is S3-compatible: a deployed app receives STORAGE_BUCKET, STORAGE_S3_ENDPOINT, STORAGE_S3_ACCESS_KEY_ID, STORAGE_S3_SECRET_ACCESS_KEY, and STORAGE_S3_REGION (suffixed for a named service, such as STORAGE_BUCKET_FILES). The interface supports object list and get. See Storage for the client setup. STORAGE_S3_SECRET_ACCESS_KEY is write-only: floo env get does not return it. Copy objects from code that runs inside the app, where the keys are injected, with the same S3 client the app already uses: list the bucket, get each object, and write it to the destination. For a few objects, list them with floo storage ls and download each through a signed GET URL. A WRITE-scoped floo API key requests the URL:
The response’s url downloads the object for 60 to 3600 seconds (default 900). --name is the Storage service name from floo.app.toml (default if omitted). floo storage ls returns at most 75 objects per call; use a narrower prefix when the list is truncated. A Storage service created before v2026.09.27.1 (September 27, 2026) has no S3 keys; copy its objects from inside the app with the storage SDK the app already uses (Storage).

Export env vars and config

List every key, with values masked:
floo env get returns a config value. Secrets are write-only and never returned; use the copies in your secret store on the new host. The following writes app-level config values to a local .env file. Use it for single-line values only, and keep the file private and out of git:
Add multiline values and the secrets from your secret store to the new host separately. For a service’s own variables, pass --service SERVICE_NAME to both floo env commands and drop and .service_id == null from the filter. Replace SERVICE_NAME with the service name. DATABASE_URL, PG*, REDIS_URL, STORAGE_*, and FLOO_AUTH_* come from floo’s managed services; take their new values from the services you move to. floo.app.toml is in your repository and holds the rest of the app’s configuration.

Run the same image elsewhere

floo builds each service from its Dockerfile. Build and run it the same way:
The container contract holds on any host: bind $PORT on 0.0.0.0. Variables with a build-time prefix (NEXT_PUBLIC_, VITE_, REACT_APP_) reach the build as build args, so pass them with --build-arg the way floo does. A multi-service app has one Dockerfile per service path in floo.app.toml; build and run each.

Replace what is floo-specific

An app that uses User accounts needs a replacement sign-in service before it moves.

Delete the app on floo

--preflight shows what would be deleted. The delete prompts you to type the app name. It destroys every service, env var, managed service (databases and Storage buckets included), domain, the deploy history, and a repository floo hosts. A connected GitHub repository of your own is kept. Non-interactive runs (CI, --json, pipes) require --yes-i-know-this-destroys-data. Deletion is irreversible. See floo apps delete.