Skip to content
Docs

Transferring Domains to Another Team or Project

If you are moving a website and its domains to another team, transfer the project so its deployments and project configuration move together. Review how project transfers handle apex domains, subdomains, and wildcard domains before starting.

To move domain ownership without transferring a project, use the Move action below. The domain's DNS records are preserved, but moving ownership does not transfer its associated projects. This is also the option for a domain that is not currently assigned to a project.

  1. You can move domains to another team using the Domains section in your team dashboard sidebar.

  2. Once on the Domains tab, select the context menu next to the domain you wish to move, and click Move. You can also use checkbox next to each domain to select more than one domain

    Selecting which domains to move from the Domains tab.
    Selecting which domains to move from the Domains tab.
  3. After selecting the domain(s) and clicking Move, you will be asked to confirm which profile or team you wish to move them to.

    Entering a new profile or team destination for a domain.
    Entering a new profile or team destination for a domain.

    When selecting the input field, you will be provided with a list of teams you belong to. If the profile or team you wish to move the domain(s) to is not present, enter the slug value instead. You can find the slug value in Settings page for both profiles and teams.

    When moving domains to another team or user, all existing project domains associated with them will remain and not be moved to prevent service disruption. However, any custom aliases that are not part of project domains will be removed immediately.

  4. To confirm the change, select Move. The domains will be transferred to the new profile of team immediately.

To move a domain between projects in the same team, add it to the destination project and confirm the move. You do not need to remove it from the original project first. Deleting the domain before reassigning it can interrupt traffic.

  1. Deploy and test the destination project using its generated deployment URL. Make sure the environment you will assign the domain to serves the version you want visitors to receive.
  2. In the destination project, open Settings, then Domains, and add the existing domain. Select the intended environment, Git branch, or redirect settings.
  3. When Move Domain appears, review the source and destination projects and the full list of domains. The move can include other domains that redirect to the selected domain.
  4. Confirm the move, then visit the custom domain and check its configuration in the destination project. Verify any redirects and branch assignments.

For automated workflows, use the Move a project domain API instead of separate remove and add requests. The API accepts the destination project ID and optional Git branch and redirect settings.

To point a custom domain at a specific deployment with the CLI, use vercel alias:

terminal
vercel alias set your-deployment.vercel.app example.com

Replace your-deployment.vercel.app with the destination's unique deployment URL, and omit https:// from the custom domain. This assigns the alias to that deployment. Also move the domain's project configuration using the steps above so future deployments use the intended project and environment.

Transferring a domain's registration and changing its DNS provider are separate operations. Before transferring a domain into or out of Vercel:

  • Check transfer eligibility with the current registrar. ICANN transfer restrictions can include a 60-day lock after registration, a previous transfer, or changes to registrant details. Registry-specific rules can also apply.
  • Confirm that the receiving registrar supports the domain's top-level domain (TLD), and review its transfer requirements and charges.
  • Export or copy the current DNS records, including website, email, and verification records. Confirm whether the current DNS provider will continue serving them after the registration transfers.
  • If you also change nameservers, migrate and verify the DNS records before switching. Keep the previous DNS service active while the change propagates.
  1. Review the registrar transfer prerequisites, then open the domain on your team's Domains page. Confirm that Vercel is the registrar and that the domain has no active transfer restriction. Domain age alone does not establish eligibility.

  2. For domains that are registered with Vercel, you can retrieve an authorization code for transferring out to another registrar from Domains in the Dashboard sidebar.

  3. Once on the Domains tab, click on the triple-dot menu button for the relevant domain. A menu-item button to transfer the domain out will be presented if the domain is registered with Vercel.

    Menu item button for getting domain's transfer authorization code.
    Menu item button for getting domain's transfer authorization code.

    If under a Team scope, only Team Owners will see the menu-item button.

  4. After clicking the menu-item button, a modal will open up with the authorization code required to transfer the domain. Use this authorization code with your new registrar to confirm that you want to transfer the domain. There is no additional confirmation that you need to do on the Vercel side. Transferring a domain can take up to a week.

    If you encounter problems with the transfer code, ensure you've entered it correctly without typos or extra spaces. If the code seems correct but still doesn't work, please contact Vercel support for further assistance.

    Modal for domain's transfer authorization code.
    Modal for domain's transfer authorization code.

Transferring your domain into Vercel moves its registration to Vercel. You can also use a domain registered elsewhere with a Vercel project by adding the domain and configuring DNS, without transferring its registration.

  1. Review the registrar transfer prerequisites and confirm eligibility with your current registrar.

    If Vercel reports that the TLD is not supported for transfer, keep the registration with your current registrar and connect the domain to your Vercel project through DNS instead.

  2. Once you have verified your domain's eligibility to transfer, proceed with unlocking your domain in your registrar's domain settings. Most domains are usually locked by default to prevent unauthorized changes.

    The domain lock feature appears in different forms across registrars. Sign into the host where your domain is registered and look for a Domain Lock or similar option to unlock your domain. If this option is not available, contact your registrar to change this.

    The status clientTransferProhibited indicates a registrar transfer lock. Ask the registrar whether you can unlock the domain or must wait for a transfer restriction to end.

  3. After unlocking the domain, you will need to obtain an authorization code. The code will be sent to the email address associated with your domain by your registrar. In some cases, your authorization code pops up on your dashboard. This may be available in the domain registrars dashboard. If it is not available, contact your registrar to obtain this.

  4. When transferring a domain, you will have two options to choose from. Either using the Vercel Dashboard or Vercel CLI.

    Option 1: Using Vercel Dashboard

    After obtaining the authorization code, click on the Transfer in button in the Vercel Domains Dashboard and enter in your domain and respective authorization code.

    Option 2: Using Vercel CLI

    With Vercel CLI, you can run the following command from your terminal.

    vercel domains transfer-in [your-domain]

    You will be requested to provide an authorization code from your registrar after running this command. Once you get the authorization code from your registrar, paste it into the prompt and the transfer will begin.

    In a case where your domain cannot be transferred, check that it has been over 60 days since the domain has been registered or previously transferred. If it still does not work, contact your registrar.

  5. Keep DNS and website migration separate from the registration transfer. Use the registrar transfer preparation steps to preserve website and email records.

    Pre-generate SSL certificates

    If you are migrating a deployment to Vercel, require zero downtime, and aren't using Vercel's nameservers, you can pre-generate and issue SSL certificates to your domain. If you have enabled Vercel DNS by pointing your domain's nameserver to Vercel and have generated an SSL certificate, you can ignore this step.

    Follow the detailed guide to set up SSL certificates before finalizing the domain transfer.

    Set DNS records in your registrar

    For a website moving to Vercel, configure the A or CNAME records shown in your project's Domains settings at the authoritative DNS provider. Certificate-verification TXT records alone do not route website traffic. If you also switch to Vercel's nameservers, copy and verify the full DNS configuration first.

  6. You can deploy your app with Vercel once the domain has been successfully added to your account.

    By setting a production domain from your projects' Domains dashboard, you will be able to use the following command with Vercel CLI:

    vercel --prod

    This command will deploy your project and make it accessible at the production domain that you have setup.

Last updated August 28, 2026

Was this helpful?

supported.