Skip to content
Netlify Docs
For the complete Netlify documentation index, see llms.txt. Markdown versions of this page are available by appending .md to the URL.

Unlimited seats on Netlify Pro for $20/month → Learn more 👥

Transfer a project

For the complete documentation index, see llms.txt

As a Team Owner, you can transfer a project to another team if team transfers are allowed and you are also an Owner or Developer on the team you are transferring to.

How transfers work

Section titled “How transfers work”

Before transferring a project, consider the following:

  • Project members who are not members of the destination team will lose access to the Netlify dashboard for the project. You may want to invite them to the team before transferring.
  • Some features and settings are restricted to specific plans. If the destination team is on a lower plan than the originating team, you will lose any settings you may have entered for the features you lose. Check the current plan for each team and compare their features and pricing.
  • Sites linked to GitHub Enterprise server or GitLab self-managed repositories rely on a team-level connection to your instance, and require special handling for transfer. If you need to transfer a site that’s linked to a GitHub Enterprise server or GitLab self-managed repo, contact support for assistance.
  • Legacy Global sites use a dedicated CDN, and require special handling for transfer. If you’re considering canceling a Global site plan or transferring a Global site to a team, contact support so we can guide you through the process and avoid any interruptions in service.

To transfer projects between teams with no shared Owners or Developers, please contact support.

Transfer a project

Section titled “Transfer a project”

As a Team Owner, to transfer a project:

  1. Ensure you understand the impact of transferring a project. Check out how projects work.
  2. Go to Project configuration General Project information.
  3. Select Transfer project. You may also choose to create a new team from this menu.

Block transferring a project

Section titled “Block transferring a project”

Team Owners can prevent every project owned by the team from being transferred out, regardless of individual member permissions. This is useful when you want to guarantee that projects stay within the team, for example to meet compliance or ownership requirements.

  1. To change the setting, go to Team settings Access & security Transfer site settings and select Edit settings.
  2. Choose whether you want to block or allow transferring projects:
  • Allowed (default). Team members with the required permissions can transfer projects to other teams.
  • Blocked. No member of the team can transfer a project to another team, even Team Owners. The Transfer project action is hidden from the UI for every project owned by the team, and the backend rejects transfer requests for those projects.

Enterprise teams start with Site transfers set to Blocked for security reasons, but Team Owners can change it to Allowed at any time.

Only Team Owners can change this setting. Other roles see the card in read-only mode. Changes are recorded in the team audit log.

The setting only affects transfers out of the team. Incoming transfers from other teams are not blocked by this setting. If you need to move a project out of a team while transfers are blocked, change the setting back to Allowed before starting the transfer.