A Vercel handover is a project transfer between teams, not a copy of a deployment. Your client's team becomes the place where builds, domains, environment variables, and project settings live.
The project may move without downtime, but you still need to inspect what Vercel excludes. Integrations, monitoring data, logs, and some vercel.json-defined environment values need a deliberate follow-up pass.
Before you start
- Take a fresh backup of files, databases, and environment settings before changing ownership.
- Confirm whether email, DNS, domains, add-ons, staging, and backups move with the site or stay behind.
- Give your client a clear window for freeze time, maintenance mode, or DNS changes.
On Vercel, specifically
- Vercel transfers projects between Vercel teams with zero downtime and no workflow interruptions. Source, checked September 3, 2026.
- To transfer a Vercel project, you must be an owner of the team transferring from and a member of the team transferring to. Source, checked September 3, 2026.
- Vercel requires a valid payment method on the target team before transfer when the missing payment method could interrupt service. Source, checked September 3, 2026.
- Vercel transfers deployments, project environment variables, configuration details, domains and aliases, administrators, builds, the Git repository link, and several project settings. Source, checked September 3, 2026.
- Vercel does not transfer integrations, monitoring data, log data, custom log drains, or environment variables defined directly in vercel.json. Source, checked September 3, 2026.
The three stages
Prepare
Inventory the production site, staging copies, database names, cron jobs, environment variables, and billing add-ons. Pause risky content edits while the host prepares the transfer.
Transfer
Start the provider's account-transfer flow or create the receiving account path they document. Share only transfer codes or dashboard invitations, never your own login.
Confirm
Load the site from the new owner context, check SSL, forms, uploads, admin login, scheduled tasks, and any DNS records that point traffic at the host.
What to tell your client
- What moves automatically and what they need to recreate.
- Who pays for the hosting plan once the transfer is accepted.
- Whether your collaborator access stays in place after ownership changes.
After it is done
Record the asset in Everkey, change its ownership status from needs_transfer to client_owned, and leave a short note with the account that now controls the project. The free tier is enough for a small handover map.