# Migrate Fly.io app: Next.js

Move Next.js compute from Fly.io app to Ample, one component at a time. Destination verified on Ample: the app built, started and answered on its public HTTPS URL with encrypted configuration delivered. Source procedure: Export secrets and env from `fly.toml` \[env\] and `fly secrets list` (values must come from your own records; Fly does not reveal secret values). Move separately: Fly volumes become Ample volumes and 6PN private services connect with `--link`; Ample runs each app in the USA or Europe and handles placement, so Fly Machines API calls drop out. Cutover: Add the custom domain with `ample domain add`, update DNS from the Fly target, keep the Fly app until verified, then scale it to zero. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

**Verified November 5, 2026**

## What it runs on

- [Computeverified](/content/discover/primitive/compute/index.html)
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)
  Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

## You need

- Authorized access to the Fly.io app source and its export tooling
- An inventory of every component in scope and out of scope
- A validated backup or copy before any cutover
- An Ample account token with servers:write, databases:read

## Exact tested configuration

- **build**: `npm run build --if-present`
- **install**: `npm install`
- **runtime**: node
- **sizes**: 1vcpu-1gb
- **start**: `npm run start`
- **template**: node-22

## Steps

1. **Inventory the source.** List what Fly.io app provides beyond the component you are moving. Plan these separately: Fly volumes become Ample volumes and 6PN private services connect with `--link`; Ample runs each app in the USA or Europe and handles placement, so Fly Machines API calls drop out.

2. **Source step 1.** Export secrets and env from `fly.toml` \[env\] and `fly secrets list` (values must come from your own records; Fly does not reveal secret values)

3. **Source step 2.** Translate `fly.toml` services and the Dockerfile or buildpack into a Node or Python source deploy; Ample builds from source on its templates

4. **Source step 3.** Note Fly-only features in use: multi-region placement, machines API, volumes, private networking

5. **Deploy on Ample in parallel.** next build then next start -H 0.0.0.0 -p $PORT on the node-22 template. Pass the exported variables with --env; keep the source running.
   
   ```sh
   $ ample deploy . --name <app-name> --public --env-file .env.production
   ```

6. **Validate before cutover.** Run the app's own checks and, for data, compare counts and checksums; the example checks are the pattern self-tests (/p/configuration-secrets, /p/relational-records).

7. **Cut over.** Add the custom domain with `ample domain add`, update DNS from the Fly target, keep the Fly app until verified, then scale it to zero.

8. **Rollback.** Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.

## How it was checked

- ✓ destination app responds on its public URL · http get/ → “ample canary next js patterns”
- ✓ configuration-secrets check from the destination example · http get/p/configuration-secrets → “see the pattern fixture checks”
- ✓ relational-records check from the destination example · http get/p/relational-records → “see the pattern fixture checks”
- ✓ data or object counts and checksums match the source · manual → “operator comparison before cutover”

## Evidence

1. November 5, 2026 · canary run

Destination side verified: the Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template) and its checks passed (the app built, started and answered on its public HTTPS URL with encrypted configuration delivered). The source-side export from Fly.io app uses the vendor's standard tooling.

## Tested examples

- **Next.js pattern fixture (destination).** Verified destination basis: Next.js compute.

## What it doesn’t cover

- A step-by-step guide: each stage is an ordinary `ample deploy`, `ample database` or `ample bucket` command you run.
- The destination side was verified on Ample with the pattern fixture; the source-side steps use Fly.io app's standard tooling.
- Plan separately: Fly volumes become Ample volumes and 6PN private services connect with `--link`; Ample runs each app in the USA or Europe and handles placement, so Fly Machines API calls drop out.
- Verified on the node-22 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector. Back up and restore with pg_dump and pg_restore.
