# Migrate Netlify web app: Next.js

Move Next.js compute from Netlify web 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: Copy environment variables from Site configuration (or `netlify env:list`) into an env file kept out of the repository. Move separately: Netlify Functions and Edge Functions become routes in the app or a separate Ample service; `_redirects`/`_headers` rules, Forms and Identity move into the app or its framework. Cutover: Add the custom domain with `ample domain add`, set the documented DNS records, keep the Netlify site until verified, then remove the domain from Netlify. 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 Netlify web 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 Netlify web app provides beyond the component you are moving. Plan these separately: Netlify Functions and Edge Functions become routes in the app or a separate Ample service; `_redirects`/`_headers` rules, Forms and Identity move into the app or its framework.

2.  **Source step 1.** Copy environment variables from Site configuration (or `netlify env:list`) into an env file kept out of the repository.

3.  **Source step 2.** Translate `netlify.toml` build settings (command, publish directory) into the repository's own build script; Ample runs the detected build.

4.  **Source step 3.** List Netlify-only features in use: functions, edge functions, forms, identity, redirects and headers rules.

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`, set the documented DNS records, keep the Netlify site until verified, then remove the domain from Netlify.

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 Netlify web 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 Netlify web app's standard tooling.
- Plan separately: Netlify Functions and Edge Functions become routes in the app or a separate Ample service; `_redirects`/`_headers` rules, Forms and Identity move into the app or its framework.
- 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`.
