A domain transfer looks simple on the surface, but a few small mistakes can cause delays, downtime, or even a failed transfer. Before you start the process, it is important to confirm that the domain is eligible, that your contact details are correct, and that your DNS and hosting setup are ready for the change. This is especially important when the domain is connected to a website, email service, or managed hosting environment.
In this guide, you will find a practical checklist for domain transfers, along with the most common issues to verify before you move a domain to a new registrar or hosting provider. The steps below are useful whether you manage everything from a control panel such as Plesk or work with a fully managed hosting platform.
Start with the basics: understand what is being transferred
A domain transfer usually means moving the registration of a domain name from one registrar to another. It does not automatically move your website files, databases, or email accounts. Those services may remain on the current hosting account unless you also migrate them separately.
This distinction matters because many transfer problems happen when customers expect the domain move to include hosting migration. Before you proceed, confirm the following:
- The domain registration will move to the new registrar.
- Your website hosting may stay the same or may be moved separately.
- Your DNS records may need to be updated after the transfer.
- Email services may continue to depend on the current DNS and mail configuration.
If your hosting and domain are currently managed in the same account, plan the transfer carefully so that name servers, A records, MX records, and SSL-related settings remain consistent during the transition.
Check whether the domain is eligible for transfer
Not every domain can be transferred immediately. Most registrars and domain extensions follow standard transfer rules, and checking eligibility early helps avoid wasted time.
Verify the registration age
Many gTLD domains such as .com, .net, and .org cannot be transferred within the first 60 days after registration or after a previous transfer. This restriction is common and usually enforced by the registry.
Review lock status
The domain must typically be unlocked before a transfer can begin. A locked domain is protected against unauthorized changes and transfer requests. In many control panels, this setting may appear as:
- Domain lock
- Registrar lock
- Transfer lock
- Client transfer prohibited
Check the current registrar’s interface or Plesk integration if domain management is available there. If you are using a managed hosting platform, support may also be able to confirm the lock status for you.
Confirm the domain is not expired
Some domains can still be transferred after expiration, but this depends on the extension and registrar policies. It is safer to transfer a domain before it expires. If a domain is already expired, renewal may be required first, and that can add time and cost.
Look for registry-specific restrictions
Country-code domains and special TLDs may have different transfer rules. Some require additional paperwork, local presence details, or DNS changes before transfer approval. Always check the rules for the specific extension.
Make sure you have access to the current registrar account
You should have admin access to the current registrar before starting the transfer. Without access, it becomes difficult to unlock the domain, obtain the authorization code, or approve transfer-related emails.
What you may need from the current registrar
- Account login credentials
- Access to the domain management panel
- Authorization code or EPP code
- Approval access to the registrant email address
- Ability to disable any active transfer protection
If the domain is managed by a former developer, agency, or third-party provider, ask them to confirm that they can provide full transfer access. A missing authorization code is one of the most common reasons a transfer stalls.
Confirm the registrant contact email is correct and accessible
The registrant email address is often the most important contact during a transfer. Transfer approval notices, verification messages, and registry confirmations are commonly sent there.
Before starting the transfer, check that the email address on file:
- Is active and monitored
- Belongs to the current domain owner or authorized administrator
- Can receive messages without filtering them as spam
- Is not tied to an employee who has left the company
If the email address is no longer accessible, update it first if possible. For domains involved in business operations, use a stable address such as [email protected] or a company-controlled mailbox rather than a personal email account.
Review DNS and hosting dependencies before moving the domain
A domain transfer does not necessarily change DNS, but the transfer process can expose weaknesses in your setup. If the domain currently points to your website, email, or other services, check how those services are configured before the move.
Check your name servers
If your name servers are managed by the current registrar or host, make sure you know where they are hosted and what records they contain. If the new registrar uses different defaults, the DNS zone may need to be recreated after the transfer.
Export or document your DNS records
Before making any changes, save a copy of your DNS configuration. Make sure you have a record of:
- A and AAAA records for the website
- CNAME records
- MX records for email
- TXT records for SPF, DKIM, and domain verification
- SRV records if used by applications or VoIP
- Any custom records for subdomains
If you manage DNS in Plesk, you can usually review and export zone data from the domain’s DNS settings. In other hosting control panels, the process may differ, but the goal is the same: have a complete backup of the current zone before transfer-related changes begin.
Check whether the website uses third-party services
Your domain may also be connected to platforms such as:
- Email filtering services
- CDNs
- Shopping cart platforms
- SSL certificate validation services
- Marketing or analytics tools
These services often rely on DNS records. If name servers or DNS hosting change during the transfer, those integrations may stop working unless records are recreated correctly.
Back up the current website and email configuration
Even though a domain transfer does not directly move website data, backups are still essential. A transfer often happens alongside other changes, such as hosting migration or DNS restructuring.
Back up website files and databases
Make a complete backup of the site, including:
- Website files
- Databases
- Configuration files
- SSL certificates, if applicable
- Scheduled tasks or cron jobs
Back up mailboxes and mail settings
If email is hosted with the same provider, export or copy mailbox data where possible. Also document:
- Mailbox names and quotas
- Forwarders
- Autoreplies
- Spam filtering rules
- SMTP, IMAP, and POP settings
This is particularly important in managed hosting environments, where mail services may be tightly tied to the control panel configuration.
Check whether the domain is part of a bundle or managed service
Many businesses register domains together with hosting, SSL, email, or website management services. If the domain is part of a bundled package, the transfer may affect billing or service continuity.
Ask these questions before transferring
- Will transferring the domain cancel any bundled discounts?
- Is the hosting account independent from the domain registration?
- Will DNS hosting stay active after the domain moves?
- Are there services that must be reconfigured at the new registrar?
- Will the current provider still host the website after transfer?
If the domain is used as the primary identifier for your hosting account, update internal references before the move. This includes billing contacts, support records, and any automated renewal notices.
Check transfer timing to avoid downtime
Timing matters when transferring a domain used by an active website or business email. Although a transfer itself does not usually interrupt service, accidental DNS changes or account changes can.
Choose a low-risk period
Whenever possible, avoid transferring a domain during:
- Sales campaigns
- Product launches
- Holiday traffic peaks
- Critical email periods
- Planned website migrations
Lower your TTL before changes, if needed
If you expect DNS records to change during or after the transfer, lower the TTL on important records in advance. This allows changes to propagate faster. Do this only if you know your DNS setup and can apply the change safely before the transfer begins.
Check domain security settings and transfer protection
Security settings can stop a transfer or delay approval if they are not managed correctly. Before starting, review any security layers applied to the domain.
Two-factor authentication
If the registrar account uses two-factor authentication, make sure the relevant administrator can complete approval steps without being locked out. If multiple people manage the domain, confirm who has final approval authority.
Registry and registrar protection tools
Some registrars offer extra protection features such as transfer fraud prevention, registry lock, or account-level restrictions. These can be helpful, but they may need to be turned off or verified before the transfer request can succeed.
Change notifications
Watch for email notices about registrar changes, WHOIS updates, and transfer requests. Missing one of these notices can slow the process if additional approval is required.
Review WHOIS or registration data before transfer
Accurate domain data helps prevent approval issues and ownership disputes. Before you begin, review the registrant, admin, and technical contact details.
What to verify
- Registrant name or organization
- Contact email address
- Phone number, if required
- Billing contact details
- Country and address information
If the domain belongs to a company, the registration data should ideally reflect the company rather than an individual employee or contractor. This makes future transfers and account recovery much easier.
Understand the impact on DNS propagation
One of the most common concerns during a domain transfer is whether the website or email will go offline. The transfer itself usually does not cause downtime, but DNS changes can take time to propagate.
Keep in mind:
- DNS changes may take minutes or up to 48 hours to fully propagate.
- Some resolvers cache old records based on TTL values.
- Different services may update at different speeds.
- Users may temporarily see old or new settings depending on their network.
To reduce risk, avoid changing name servers and transfer settings at the same time unless necessary. If the website remains on the same host, keeping DNS unchanged during the transfer can minimize disruption.
Prepare a transfer checklist for your team
If multiple people manage the website, registrar, and hosting account, create a simple transfer checklist so responsibilities are clear.
Useful checklist items
- Confirm domain eligibility
- Unlock the domain
- Retrieve the authorization code
- Verify the registrant email address
- Back up DNS records
- Document hosting dependencies
- Confirm renewal status and expiration date
- Notify stakeholders of the transfer window
- Monitor email for approval messages
- Check the website and mail after completion
In a managed hosting environment, support teams often use a similar checklist to reduce mistakes during coordination between registrar, DNS, and hosting services.
Common problems to avoid before a transfer
These are the issues that most often delay a domain transfer:
- The domain is still locked at the current registrar.
- The authorization code is missing or outdated.
- The registrant email is inaccessible.
- The domain was registered or transferred too recently.
- The domain has expired and must be renewed first.
- DNS records were not backed up before changes.
- Email services depend on old MX records that are not documented.
- A third-party service still points to the old registrar DNS.
Most of these issues are preventable with a short preparation phase before the transfer request is submitted.
When to contact hosting or registrar support
If something does not look right, it is best to contact support before submitting the transfer. This is especially useful when the domain is part of a larger hosting setup or when access is shared across multiple team members.
Contact support if:
- You cannot unlock the domain
- The transfer code is not available
- The registrant email is outdated
- The domain uses custom DNS and you are unsure how to recreate it
- The domain is managed in Plesk and you need help locating records
- You expect the transfer to affect active mail or website services
Support teams can usually confirm the correct transfer steps, explain registry rules, and help you avoid accidental service interruption.
FAQ
Does a domain transfer move my website too?
No. A domain transfer usually only moves the registration. Website files, databases, and email hosting remain separate unless you migrate them independently.
Will my website go offline during the transfer?
Usually not, as long as DNS records and name servers remain unchanged. Downtime is more likely if DNS settings are edited incorrectly during the process.
Do I need an authorization code for every transfer?
In most cases, yes. The authorization code, also called an EPP code or transfer code, is required by many registrars to approve the transfer request.
Can I transfer an expired domain?
Sometimes, but it depends on the extension and registrar. It is safer to transfer before expiration to avoid extra steps or recovery issues.
What should I back up before transferring a domain?
At minimum, save your DNS records. If the transfer is part of a larger migration, also back up website files, databases, and mail settings.
How do I find DNS records in a control panel?
In hosting control panels such as Plesk, DNS settings are usually available under the domain management area. You can review current records there and export or document them before making changes.
Can support transfer my domain for me?
Support can usually guide you through the process, but the transfer must still be approved through the registrar and authorized by the domain owner or account holder.
Conclusion
Before starting a domain transfer, take time to verify eligibility, unlock the domain, confirm access to the current registrar, and document your DNS and hosting settings. If the domain supports a live website or email service, careful preparation is the best way to avoid interruptions.
A successful transfer is usually not about speed. It is about checking the right details in advance so the domain moves cleanly to the new registrar while your hosting, DNS, and email remain stable. If your domain is managed through a control panel or part of a broader hosting environment, a short preparation checklist can save time and prevent service issues later.