Learn how to transfer a project between Vercel accounts or teams.
Table of Contents
You can transfer projects between your Vercel accounts with zero downtime and no workflow interruptions.
You must be an owner of the team you're transferring from, and a member of the team you're transferring to. For example, you can transfer a project from your Hobby team to a Pro team account, and vice versa if you're an owner on the Pro team.
During the transfer, all of the project's dependencies will be moved or copied over to the new Vercel team namespace. To learn more about what is transferred, see the What is transferred? and What is not transferred?.
To begin transferring a project, choose a project from the Vercel dashboard.
Then, select the Settings tab from the top menu to go to the project settings.
From the left sidebar, click General and scroll down to the bottom of the page, where you'll see the Transfer Project section. Click Transfer to begin the transferring flow:
The Transfer Project section.
Select the Vercel account or team you wish to transfer the project to. You can also choose to create a new team:
Choosing an account to transfer the project to.
If the target Vercel team does not have a valid payment method, you must add one
before transferring your project to avoid any interruption in service. If a valid
payment method is added to a team on a Pro Trial Plan, the trial will be upgraded
to the Pro Plan immediately.
You'll see a list of any domains, aliases, and environment variables that will be transferred. You can also choose a new name for your project. By default, the existing name is re-used. You must provide a new name if the target Vercel Account already has a project with the same name:
The original project will be hidden when initiating the transfer, but
you will not experience any downtime.
Reviewing the project data that will be transferred to the target Vercel Account, and choosing a new project name.
After reviewing the information, click Transfer to initiate the project transfer.
While the transfer is in progress, Vercel will redirect you to the newly created project on the target Vercel team with in-progress indicators. When a transfer is in progress, you may not create new deployments,
edit project settings or delete that project.
Transferring a project may take between 10 seconds and 10 minutes, depending on the amount of associated data. When the is transfer completes, the transfer's initiator and the target team's owners are notified by email. You can now use your project as normal.
Once you transfer a project from a Hobby team to a Pro or Enterprise team, you may choose to enable additional paid features on the target team to match the features of the origin account. These include:
The Active Branches section under Project will be empty
Environment variables defined in the env and build.env configurations of vercel.json must be migrated to Environment Variables in the Project Settings or configured again on the target team after the transfer is complete
Project domains will automatically be transferred to the target team by delegating access to domains.
For example, if your project uses the domain example.com, the domain will be moved to the target team. The target team will be billed as the primary owner of the domain if it was purchased through Vercel.
If your project uses the domain blog.example.com, the domain blog.example.com will be delegated to the target team, but the root domain example.com will remain on the origin Vercel scope. The origin Vercel scope will remain the primary owner of the domain, and will be billed as usual if the domain was purchased through Vercel.
If your project uses a Wildcard domain like *.example.com, the Wildcard domain will be delegated to the target team, but the root domain example.com will remain on the origin Vercel scope.
This only applies when transferring away from a team.
When transferring between teams, you may be asked whether you want to add additional features to the target team to match the origin team's features. This ensures an uninterrupted workflow and a consistent experience between teams.
Adding these features is optional.
