# Migrate Self-managed PostgreSQL: Transactional workflows

Move PostgreSQL data from Self-managed PostgreSQL to Ample, one component at a time. Destination verified on Ample: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Source procedure: Take a logical backup with `pg_dump -Fc` as a role that can read all application objects. Move separately: extensions beyond pgvector, tablespaces, replication topology and superuser-only settings stay with the self-managed server; on Ample back up with `pg_dump`. Cutover: Freeze writes with the user's go-ahead, take the final dump, restore, validate, redeploy with the managed DATABASE_URL, keep the source server until confirmed. 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

- [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 Self-managed PostgreSQL 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

```bash
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 Self-managed PostgreSQL provides beyond the component you are moving. Plan these separately: extensions beyond pgvector, tablespaces, replication topology and superuser-only settings stay with the self-managed server; on Ample back up with `pg_dump`.

2. **Source step 1.** Take a logical backup with `pg_dump -Fc` as a role that can read all application objects.

3. **Source step 2.** Check the major version, installed extensions, tablespaces and custom roles against the managed engine (PostgreSQL 16, no custom extensions verified).

4. **Source step 3.** Restore into a scratch managed database first and compare row counts.

5. **Provision and restore.** Deploy the app once so a managed PostgreSQL 16 database exists (or create one with `ample database create --engine postgres`), then restore the dump with pg_restore using its connection string; keep migrations idempotent.

```bash
$ ample database create --name <db-name> --engine postgres
```

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/transactional-workflows).

7. **Cut over.** Freeze writes with the user's go-ahead, take the final dump, restore, validate, redeploy with the managed DATABASE_URL, keep the source server until confirmed.

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 express patterns”  
✓ transactional-workflows check from the destination example· http get/p/transactional-workflows → “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 (an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected)). The source-side export from Self-managed PostgreSQL uses the vendor's standard tooling.

## Tested examples

- **Express pattern fixture (destination).** Verified destination basis: transactional workflows.

## 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 Self-managed PostgreSQL's standard tooling.
- Plan separately: extensions beyond pgvector, tablespaces, replication topology and superuser-only settings stay with the self-managed server; on Ample back up with `pg_dump`.
- 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.
