Yes, you can transfer a domain name to a new registrar without moving the website itself. In most cases, the domain transfer only changes who manages the registration of the domain. Your website files, databases, email accounts, and DNS settings can stay where they are, as long as you keep the correct DNS records in place and do not change the nameservers unless you intend to move the services too.
This is a common setup for businesses that want to use a different domain registrar while keeping hosting on the same platform, for example in a managed hosting or Plesk environment. The key point is to separate the domain registration from the website hosting. They are related, but they are not the same service.
What happens when you transfer a domain?
A domain transfer moves the registration of the domain from one registrar to another. The registrar is the company that manages your domain in the registry and controls renewal, ownership details, and transfer status.
During a normal transfer:
- the website files remain on the same web server;
- the database remains unchanged;
- email can continue to work if DNS stays pointed correctly;
- the domain registration is updated at the new registrar;
- DNS records may remain exactly as they are, depending on where DNS is hosted.
If the domain is used only as the address for a website and email, moving the registrar does not automatically move the site. The site only moves if you also change hosting, nameservers, or DNS records to point to a new platform.
Domain transfer vs website migration
It helps to understand the difference between these two actions:
Domain transfer
This changes the registrar that manages the domain name. It does not usually affect the actual website or email service.
Website migration
This moves the website content, application, database, and sometimes email to a new hosting provider or server.
These can happen separately or together. For example, you may transfer a domain to a new registrar today and keep the website on your current managed hosting plan for months or years. Or you may move the site to a new hosting platform without changing the domain registrar.
When you can transfer a domain without moving the website
You can usually keep the website where it is if:
- the website is hosted on a separate hosting account or server;
- the DNS records are kept the same after the transfer;
- you do not change the nameservers to the new registrar’s default DNS unless you recreate all records there;
- email MX records, SPF, DKIM, and DMARC remain correctly configured;
- the domain is not locked by a registry restriction or a special transfer rule.
In a hosting platform or control panel such as Plesk, the website usually continues to run as long as the domain still resolves to the correct IP address and the web server configuration remains unchanged.
How the website stays online during the transfer
Your website is reached through DNS. DNS tells browsers which server should answer for the domain. If the A record, AAAA record, or CNAME record still points to the same hosting server, the site should continue to load normally.
That means the transfer itself is not what brings the site down. Problems happen when one of these changes:
- the nameservers are changed without copying the DNS zone;
- the domain’s DNS records are deleted or overwritten;
- the hosting account is suspended or changed at the same time;
- SSL certificates depend on validation or records that are altered;
- the email service uses records that are not recreated correctly.
If you are moving only the registrar, the safest approach is to keep DNS where it is until the transfer is complete and verified.
Best practice: decide where DNS will be managed
Before starting the transfer, choose one of these two models:
Option 1: Keep DNS at the current host or DNS provider
This is often the easiest option if your website and email are already working well. You transfer the domain registrar, but the nameservers stay pointed to the existing DNS provider. The new registrar simply becomes the place where you renew and manage the registration.
This option is useful when:
- your hosting provider manages DNS for you;
- you use Plesk or another control panel that already hosts the DNS zone;
- you have website and email records configured and do not want to rebuild them;
- you want minimal risk during the transfer.
Option 2: Move DNS to the new registrar or platform
In this case, you transfer the domain and also change nameservers to the new platform. This does not have to move the website files, but it does require recreating every DNS record correctly. If you miss an MX record or a verification record, email or related services may stop working.
This option is better when:
- you want all domain management in one place;
- you have a managed hosting plan that includes DNS hosting;
- your current DNS setup is simple and easy to replicate;
- you are prepared to test every record after the switch.
Step-by-step: transfer a domain without moving the website
The exact process depends on your registrar, but the general steps are similar across most EU hosting and domain platforms.
1. Check the current domain status
Make sure the domain is eligible for transfer. Common requirements include:
- the domain is not newly registered or recently transferred within the last 60 days, depending on the TLD rules;
- the domain is unlocked;
- the authorization code or EPP code is available;
- the registrant email address can receive approval messages;
- the domain contact details are up to date.
For some country-code TLDs, transfer rules can vary. Always check the registry policy before starting.
2. Export or document your DNS records
Before making any changes, copy the current DNS zone. Save the following records:
- A and AAAA records for the website;
- CNAME records for www or subdomains;
- MX records for email;
- TXT records for SPF, DKIM, DMARC, verification, and service integrations;
- SRV records if used by any applications;
- NS records if you will be switching DNS hosting.
If DNS is managed in Plesk, you can review the DNS zone in the control panel before the transfer and confirm which records must be preserved.
3. Confirm the website hosting will not change
Check where the website is hosted and make sure that the hosting subscription, virtual host, or server configuration remains active during the transfer. If the site uses Apache, Nginx, or a managed stack, the domain should continue to point to the same server IP address.
If the hosting account is linked to the domain inside the panel, make sure the domain remains assigned to that subscription. The registrar transfer does not remove the website from the hosting account.
4. Unlock the domain and obtain the transfer code
Most gTLD domains require a transfer authorization code. Log in to the current registrar, disable the transfer lock, and request the code. Some registrars send the code by email, while others display it in the control panel.
5. Start the transfer at the new registrar
Enter the domain name and the authorization code at the new registrar. Approve any transfer email if required. In many cases, the current registrar will also send a transfer confirmation message.
During this time, the domain usually continues to resolve normally. The website should remain online if DNS is unchanged.
6. Keep DNS unchanged until the transfer completes
Do not change nameservers unless you have planned the DNS move. If the website is already working, leaving DNS alone reduces risk. The domain can finish transferring while continuing to use the same live DNS zone.
7. Verify the domain after the transfer
Once the transfer completes, check:
- the domain resolves to the correct website IP;
- the website opens with the correct hostname, including www if used;
- SSL/TLS works and the certificate is valid;
- email sending and receiving still work;
- MX, SPF, DKIM, and DMARC records are still present;
- renewal settings and auto-renew are enabled at the new registrar.
What can go wrong if you change nameservers by mistake
Changing nameservers is the most common reason a website or email stops working during a domain transfer. When you switch nameservers, you are effectively telling the internet to use a different DNS provider. If the new DNS zone is empty or incomplete, the domain may stop resolving correctly.
Typical problems include:
- the website points to no server or the wrong server;
- email stops receiving because MX records are missing;
- subdomains stop working;
- verification records for third-party tools disappear;
- SSL renewals fail if validation records are removed.
If your goal is only to transfer the domain registration, do not change nameservers unless necessary.
How to keep email safe during a domain transfer
Email can be more sensitive than the website because it depends on several DNS records. To avoid interruptions, keep these records intact:
- MX records for the mail server;
- SPF TXT records to authorize sending;
- DKIM TXT records for signed mail;
- DMARC TXT records for policy and reporting;
- autodiscover and mail host records if your setup uses them.
If your email is hosted separately from the website, the registrar transfer still should not affect mailbox data. However, if your email relies on the domain’s DNS zone and that zone changes, mail delivery can fail even though the mailbox itself still exists.
How this works in Plesk or a managed hosting environment
In Plesk and similar control panels, the domain can be attached to a subscription, and the panel manages the web server vhost and DNS zone. If the registrar changes but the DNS zone remains the same, the hosting setup does not need to change.
Useful checks in the control panel include:
- confirming the domain still exists in the subscription;
- checking the domain’s IP address;
- verifying the DNS zone after the transfer;
- ensuring the SSL certificate is still assigned;
- testing mail services if they are included in the hosting plan.
If DNS is disabled in Plesk and managed externally, make sure the external DNS provider still contains all required records. If DNS is enabled in Plesk, make sure the nameservers at the registrar continue to point to the panel’s DNS servers.
Common scenarios
Scenario 1: Move the registrar, keep the same host
This is the simplest case. You transfer the domain to a new registrar, keep the same nameservers, and the website stays online. Only the registrar changes.
Scenario 2: Move the registrar, but not the hosting
This is the same as above. The domain registry moves, while the hosting platform remains unchanged. This is very common for businesses with long-running websites and stable hosting.
Scenario 3: Transfer the domain and switch DNS to the new provider
The website can still remain on the same host, but you must recreate DNS records at the new DNS provider. This requires careful planning and testing.
Scenario 4: Transfer the domain and later migrate the website
You can do both, but it is usually safer to separate them. First transfer the domain and verify everything remains stable. Later, move the website if needed.
Checklist before you transfer
- Confirm the domain is eligible for transfer.
- Unlock the domain.
- Get the transfer code.
- Back up the current DNS zone.
- Make a note of website IP addresses.
- Record email-related DNS entries.
- Check SSL certificate status.
- Confirm the hosting account will remain active.
- Decide whether nameservers will stay the same.
- Keep access to the registrant email account.
Checklist after the transfer
- Verify the domain is in the new registrar account.
- Check that the website loads normally.
- Test the www version and the root domain.
- Send and receive test email.
- Review MX, SPF, DKIM, and DMARC.
- Confirm auto-renew is enabled.
- Update billing and contact details if needed.
- Document where DNS is managed going forward.
SEO and website visibility considerations
From an SEO point of view, transferring a domain without moving the website is usually low risk if the URL structure, content, and server response stay the same. Search engines care more about stable access and consistent redirects than about which registrar manages the domain.
To reduce risk:
- avoid unnecessary DNS changes;
- keep the site accessible with the same primary domain;
- make sure HTTP to HTTPS redirects still work;
- check that canonical tags are unchanged;
- avoid downtime during the transfer window.
If the transfer is handled correctly, rankings should not be affected by the registrar change itself.
FAQ
Will my website go offline during a domain transfer?
Usually no. If the website hosting stays the same and DNS records are not changed, the site should remain online throughout the transfer.
Do I need to move the website files to transfer the domain?
No. A registrar transfer does not require moving website files, databases, or application data.
Can I keep the same DNS records after transferring the domain?
Yes, if DNS stays with the same provider. If you switch nameservers, you must recreate the records at the new DNS host.
Will my email stop working if I transfer the domain?
Not necessarily. Email should continue working if MX and related records remain correct. Problems usually happen when DNS is changed without copying all mail records.
Is a domain transfer the same as changing hosting?
No. A domain transfer changes the registrar, while hosting migration moves the website to a different server or platform.
What should I check in Plesk before transferring the domain?
Check the domain’s assigned IP address, DNS zone records, SSL assignment, and whether the subscription will remain active after the registrar move.
How long does a domain transfer take?
It varies by TLD and registrar, but many transfers complete within a few days. During that time, the website can remain live if DNS is not changed.
Conclusion
You can transfer a domain without moving the website, and in many cases that is the safest approach. The registrar change affects ownership and administration of the domain, not the actual hosting location. As long as the DNS records continue pointing to the same server, the website and email can keep working normally.
The most important steps are to back up your DNS records, keep nameservers unchanged unless you intentionally move DNS, and verify website and email after the transfer. In a managed hosting or Plesk setup, this is usually straightforward when the domain registration and the hosting service are handled separately.