Powered by Vercel Workflow

Run migrations that outlive a serverless request

Authors and books migrate through a durable workflow, so a run can take hours, retry transient errors, and keep going after you close this page. Reopen it—or open a second window—to follow the same live progress.

[ Vercel Workflow ][ Effect RPC ][ PostgreSQL ][ Bring Your Own Client ]

Workflow migration

Catalog migrations

Migrate Serverconnecting
Try the full TUI in your terminalMIGRATE_SERVER_TOKEN="supersecret" pnpm dlx @migrate-sdk/tui --server "/api/migrate"
Live progressOpen another window and watch each completed batch appear here.

Connecting to Migrate Server…

Live session

Activity

0 events
  1. Waiting for activity…
Durable state

Migration messages

0 messages
  1. Loading messages…
Live state from the same Migrate Server as the TUI
01 / clients

Bring your own client

This page is one small example of what you can build with the Migrate Server protocol. Your application only needs the server URL and credentials; migration code and data access stay where they run.

02 / workflow

Long-running by design

Every run is a Vercel Workflow, not a serverless request. It can run for hours, retry transient errors, start on a cron schedule, and be stopped explicitly. Close this page or open another window—the run continues and every window shows the same progress.

03 / terminal

Full control from your terminal

The Migrate TUI helps you discover, start, stop, retry, and monitor migrations running locally or on a remote Migrate Server. The CLI supports scripts, agents, and cron jobs.