Transferring a domain to a new registrar is a common task when you are consolidating services, changing providers, or moving a website together with hosting. The process is usually straightforward, but it requires careful timing and a few technical checks to avoid downtime, email interruptions, or transfer delays.
This guide explains how domain transfers work, what you need before starting, how to complete the transfer, and what to verify after the move. It is written for site owners, administrators, and support teams managing domains alongside hosting services, including environments where the domain may also be connected to DNS, email, or a control panel such as Plesk.
What a domain transfer is
A domain transfer moves the registration of a domain name from one registrar to another. The registrar is the company that manages the domain’s registration records and renewal settings. A transfer does not usually move the website files or mailboxes themselves, but it can affect DNS and email if those services are also tied to the current registrar.
In practice, a domain transfer changes who manages the registration of the domain, while the hosting account may remain unchanged. In many migrations, both the hosting and the domain move at the same time, which makes planning important.
What changes during a transfer
- The new registrar becomes responsible for domain renewal and management.
- The domain’s registrar-level settings change.
- Authorization and control move to the gaining registrar.
- DNS may remain the same if nameservers are unchanged, but this should be verified.
What does not automatically change
- Your website files and application data.
- Your hosting account, unless you move it separately.
- Email accounts and mailboxes, unless they depend on the old provider.
- DNS records, if they are hosted externally and nameservers stay the same.
Before you start the transfer
Preparation is the most important part of a successful domain transfer. Most failed or delayed transfers happen because one of the required pre-checks was missed.
Check domain eligibility
Most domains can be transferred if they are not in a restricted status. Common restrictions include:
- The domain is newly registered or recently transferred.
- The domain is locked at the registrar.
- The registrant email address is outdated or inaccessible.
- The domain uses privacy or proxy settings that hide contact details, making approval harder in some cases.
For many generic top-level domains, there is a waiting period after registration or a prior transfer before another transfer can begin. If you are unsure, check the current registrar’s transfer policy first.
Unlock the domain
Before a transfer can begin, the domain must usually be unlocked at the current registrar. This is often called registrar lock or transfer lock. When the domain is locked, unauthorized transfers are prevented. You will need access to the control panel of the current registrar to change this setting.
Obtain the authorization code
Most domains require an authorization code, also known as an EPP code, transfer code, or AuthInfo code. This code is issued by the current registrar and must be entered at the new registrar to confirm the transfer request.
Keep the code secure. It is a sensitive credential that proves control over the domain transfer process.
Verify contact information
Transfer approval messages are often sent to the registrant or administrative email address associated with the domain. Make sure the email address is active and can receive mail. If the contact information is incorrect, you may miss an approval message and the transfer can fail or time out.
Check DNS and hosting dependencies
If the domain is connected to a website, mail service, or a control panel-managed subscription, review how it is currently configured.
- Identify the current nameservers.
- Export DNS records if they are managed at the old registrar.
- Note MX records, SPF, DKIM, and DMARC settings for email continuity.
- Confirm whether the website uses a temporary URL, dedicated IP, or SSL certificate tied to the domain.
If you are moving hosting at the same time, plan the hosting migration first or at least prepare the destination environment before changing nameservers or completing the domain transfer.
Step-by-step: how to transfer a domain to a new registrar
The exact interface differs by provider, but the overall process is similar across most registrars and hosting platforms.
1. Review the current domain status
Log in to the current registrar and confirm that the domain is eligible for transfer. Look for indicators such as lock status, expiration date, and any pending updates or disputes. If the domain is close to expiration, renew it first if needed, unless your registrar’s policy advises otherwise.
2. Disable the transfer lock
Turn off registrar lock in the domain management area. This action allows the transfer request to proceed. If the domain remains locked, the gaining registrar will not be able to finalize the move.
3. Request the authorization code
Generate or retrieve the transfer code from the current registrar. Some registrars send it by email, while others display it in the control panel. If the code is not visible, open a support request with the current provider.
4. Start the transfer at the new registrar
At the new registrar, choose the option to transfer an existing domain. Enter the domain name and provide the authorization code when prompted. Some providers may also ask you to confirm contact details or choose a renewal period.
5. Approve transfer requests
After initiating the transfer, you may receive approval emails from the current registrar or the registry process. Follow any confirmation instructions promptly. In some cases, the transfer begins automatically once the request is submitted and the code is validated.
6. Wait for completion
Domain transfers usually take a few hours to several days, depending on the domain extension and registrar policies. During this period, the domain generally continues to work as normal if DNS is configured correctly.
7. Confirm the new registrar settings
Once the transfer is complete, log in to the new registrar and verify that the domain appears in your account. Check renewal status, lock settings, nameservers, and contact information. Make sure the domain is secured after the transfer is finalized.
How to avoid downtime during a domain transfer
A domain transfer itself does not necessarily cause downtime. Problems usually occur when DNS, hosting, or email records are changed at the wrong time.
Keep DNS stable
If your website and email are already working through reliable nameservers, consider keeping them unchanged during the transfer. That way, visitors continue to reach the same DNS zone while the registration changes in the background.
Lower DNS TTL before making changes
If you plan to update DNS records or move hosting, reduce the TTL on important records in advance. A shorter TTL helps changes propagate faster, which is useful when migrating websites or email services.
Move hosting first if needed
When the domain transfer is part of a larger hosting migration, prepare the new hosting account first. Upload the website, test the application, configure SSL, and verify email routing before switching DNS. This is especially useful in managed hosting environments where the control panel or Plesk subscription needs to be ready before the public cutover.
Keep email records intact
Email disruption is one of the most common issues during transfers. If your mailboxes rely on DNS records such as MX, SPF, DKIM, and DMARC, make sure they are copied exactly to the new DNS zone before changing nameservers.
Domain transfer and Plesk or control panel environments
If your hosting is managed through a control panel such as Plesk, the domain transfer should be coordinated with the hosting configuration. The domain registration can move to a new registrar while the hosting subscription remains on the same server or moves to a new provider.
What to check in Plesk
- Confirm the domain is added to the correct subscription.
- Check that the document root points to the correct site files.
- Verify SSL/TLS certificate status after DNS changes.
- Review mail service settings if the server handles email.
- Ensure DNS service is active only where intended.
If Plesk is managing DNS locally, make sure the zone contains the correct A, AAAA, MX, TXT, and CNAME records. If DNS is hosted elsewhere, the control panel settings should match the authoritative DNS provider.
When the registrar and hosting provider are different
It is common to register a domain with one company and host the site with another. In that case, the registrar only manages ownership and renewal, while the hosting company handles the server. This separation can be useful, but it requires that DNS points to the correct hosting environment and that renewal notices are monitored at the registrar level.
Common problems during domain transfers
Even when the process is simple, transfers can fail or stall for predictable reasons. Knowing them in advance helps you resolve issues quickly.
Incorrect authorization code
If the transfer code is wrong, expired, or copied incorrectly, the request will fail. Request a fresh code from the current registrar if needed.
Domain is still locked
A locked domain cannot be transferred. Recheck the registrar lock setting and confirm the change has fully saved before retrying.
Administrative email is unavailable
Transfer approval may depend on messages sent to the contact email address. If the mailbox is inactive, inaccessible, or filtered, the transfer can be delayed. Update contact details before starting, if the registrar allows it.
Pending changes or disputes
Recent ownership updates, registrar changes, or legal disputes can temporarily block the transfer. In such cases, wait until the restriction expires or contact support for clarification.
The domain expired too early
Some domains can still be transferred after expiration, but this depends on the extension and registrar policy. Do not rely on this if the domain is critical. Start the transfer early and renew if necessary to avoid service interruption.
DNS was changed without planning
If nameservers were changed before records were copied, services may stop resolving. Always export or recreate the full DNS zone before switching providers.
Best practices for transferring a domain
A few simple habits reduce risk and make future management easier.
- Start the transfer well before the expiration date.
- Keep the registrant email address current.
- Record all DNS settings before making changes.
- Do not change nameservers and transfer the domain at the same time unless necessary.
- Verify website and email functionality after the move.
- Enable domain lock again after the transfer completes.
- Store login credentials and authorization codes securely.
If you manage multiple domains, keep an internal checklist for ownership, renewal dates, DNS hosting, SSL expiry, and mail service dependencies. This is especially useful in managed hosting and agency workflows.
How domain transfers affect email and SSL
Domain registration changes do not automatically break email or SSL, but the services around the domain may be affected if DNS or hosting details change.
For email to continue working, MX records must point to the correct mail server. In addition, SPF, DKIM, and DMARC TXT records should be preserved. If your hosting provider handles mail through Plesk or another panel, confirm that mail routing is set correctly after the migration.
SSL certificates
SSL certificates depend on domain validation and hosting setup, not just registrar ownership. After a transfer, the certificate usually remains valid if the site and DNS do not change. However, if you move hosting or switch IP addresses, you may need to reissue or reconfigure the certificate.
FAQ
How long does a domain transfer take?
Most transfers complete within a few hours to several days. The exact time depends on the domain extension, the current registrar, and whether any approval steps are required.
Will my website go offline during the transfer?
Usually no. A transfer changes the registrar, not the website files. Downtime only occurs if DNS is changed incorrectly or the hosting environment is not ready.
Do I need to move hosting at the same time?
No. A domain transfer and a hosting migration are separate processes. You can transfer the domain first and move the hosting later, or do both together if the plan is carefully prepared.
What is the authorization code used for?
The authorization code verifies that you have permission to transfer the domain. It acts as a transfer credential between the current and new registrar.
Can I transfer an expired domain?
Sometimes, but policies vary by extension and registrar. It is safer to start the transfer before expiration or renew the domain first if allowed.
Should I keep my old nameservers during the transfer?
If your DNS is already working and hosted separately, keeping the same nameservers is often the simplest option. If you are moving DNS too, copy all records first and switch only after testing.
What happens to my DNS records after the transfer?
If the nameservers stay the same, DNS records usually remain unchanged. If the new registrar also hosts DNS and the nameservers change, you must recreate the records there.
Is domain privacy removed during transfer?
Some registrars may temporarily disable privacy or show contact details during the transfer process. After completion, you can usually re-enable privacy if it is supported by the new registrar.
Conclusion
Transferring a domain to a new registrar is a routine administrative task, but it should be handled carefully when the domain is tied to a website, email service, or managed hosting setup. The key steps are simple: unlock the domain, obtain the authorization code, start the transfer at the new registrar, and verify DNS and service settings after completion.
When the transfer is coordinated with hosting changes, especially in a control panel or Plesk-based environment, planning matters even more. Keep DNS records accurate, preserve email settings, and confirm that the new hosting destination is ready before making public changes. With the right preparation, the transfer can be completed with minimal disruption and no unnecessary downtime.