Select only the Vercel services the application uses. Download or print the resulting list, assign an owner and evidence to every item, and add application-specific dependencies discovered during inventory.
Inventory before implementation
Record domains, DNS, redirects, headers, runtimes, regions, environment variable names, integrations, storage, schedules, databases, analytics, email, authentication, and external allowlists. Separate build-time public configuration from runtime secrets.
Validate before cutover
Exercise critical routes and transactions against the production artifact. Test TLS, caching, streaming, images, Server Actions, uploads, scheduled work, logs, alerts, backups, restores, deployment health checks, and graceful shutdown.
Preserve rollback
Keep the last known-good Vercel deployment and its required dependencies available. Define the person, trigger, DNS action, data compatibility rule, and verification steps for rollback before changing traffic.