# Migrate Supabase Storage bucket: Bulk import staging

Move object storage from Supabase Storage bucket to Ample, one component at a time. Destination verified on Ample: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). Source procedure: Inventory objects through the Supabase Storage API or dashboard. Move separately: enforce authorization in the app and stream private objects through it; signed uploads use `ample bucket upload-url`, and image transformations move into the app. Cutover: Switch the app's S3_* environment to the Ample bucket with a redeploy, verify reads and writes, keep Supabase Storage read-only until confirmed. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

## What it runs on

- [S3-compatible object storage verified](/content/discover/primitive/s3-compatible-object-storage/index.html)
Buckets speak the S3 API with SigV4 credentials Ample Computer issues; `ample bucket upload-url` returns a presigned upload URL. PutObject and GetObject are checked by canary.

## You need

- Authorized access to the Supabase Storage bucket 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, buckets:write

## Exact tested configuration

- `npm run build --if-present`
- `npm install`
- `node`
- `sizes-1vcpu-1gb`
- `npm run start`
- `node-22`

## Steps

1. **Inventory the source.** List what Supabase Storage bucket provides beyond the component you are moving. Plan these separately: enforce authorization in the app and stream private objects through it; signed uploads use `ample bucket upload-url`, and image transformations move into the app.

2. **Source step 1.** Inventory objects through the Supabase Storage API or dashboard.

3. **Source step 2.** Copy objects with `rclone sync` from the Supabase S3-compatible endpoint (or a scripted download) to the Ample bucket endpoint using the issued credentials.

4. **Source step 3.** Verify a sample of objects by size and checksum after the copy.

5. **Create the destination bucket and copy.** Create the bucket, copy with rclone or the S3 CLI in path-style mode using the issued credentials, then pass the credentials to the app as encrypted S3_* variables.

```bash
   $ ample bucket create --name <bucket-name>
   ```

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/bulk-import-staging).

7. **Cut over.** Switch the app's S3_* environment to the Ample bucket with a redeploy, verify reads and writes, keep Supabase Storage read-only 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"

✓ bulk-import-staging check from the destination example· http get/p/bulk-import-staging → "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 (a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok)). The source-side export from Supabase Storage bucket uses the vendor's standard tooling.

## Tested examples

- **Express pattern fixture (destination).** Verified destination basis: bulk import staging.

## 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 Supabase Storage bucket's standard tooling.
- Plan separately: enforce authorization in the app and stream private objects through it; signed uploads use `ample bucket upload-url`, and image transformations move into the app.
- Verified on the node-22 template at s-1vcpu-1gb.
- Buckets speak the standard S3 API; copy objects with rclone or the AWS CLI in path-style mode.
