# Migrate Heroku app: Express

Move Express compute from Heroku 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 config vars with `heroku config -s -a <app>` into an env file kept out of the repository. Move separately: Heroku Scheduler jobs become `ample job` schedules and release-phase tasks use `--release-command`; add-ons other than Postgres map to Ample managed databases and buckets or stay with their provider. Cutover: Add the custom domain with `ample domain add`, update DNS from the Heroku DNS target, keep the Heroku app until verified, then scale it down. 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 Heroku 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 Heroku app provides beyond the component you are moving. Plan these separately: Heroku Scheduler jobs become `ample job` schedules and release-phase tasks use `--release-command`; add-ons other than Postgres map to Ample managed databases and buckets or stay with their provider.

2. **Source step 1.** Export config vars with `heroku config -s -a <app>` into an env file kept out of the repository.

3. **Source step 2.** Translate the `Procfile` web process into the start command (`--start` or the package manifest's start script); worker processes need a separate `--kind worker` service.

4. **Source step 3.** Note buildpacks and add-ons in use; managed databases replace Heroku Postgres, other add-ons need their own plan.

5. **Deploy on Ample in parallel.** `npm install`, `npm run build --if-present`, `npm run start` on the node-22 template. Pass the exported variables with --env; keep the source running.

```
   $ 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 Heroku DNS target, keep the Heroku app until verified, then scale it down.

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 · GET / → “ample canary express patterns”  
✓ configuration-secrets check from the destination example · GET /p/configuration-secrets → “see the pattern fixture checks”  
✓ relational-records check from the destination example · 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 Express pattern fixture deployed on Ample (npm install, npm run build --if-present, npm run start 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 Heroku app uses the vendor's standard tooling.

## Tested examples

- **Express pattern fixture (destination).** Verified destination basis: Express 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 Heroku app's standard tooling.  
- Plan separately: Heroku Scheduler jobs become `ample job` schedules and release-phase tasks use `--release-command`; add-ons other than Postgres map to Ample managed databases and buckets or stay with their provider.  
- 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`.
