Your domain was registered through a developer you no longer work with. The website still functions, but you want the registration under an account you control. You find a cheaper provider and consider moving everything immediately. Before you Transfer a domain to another registrar, there is an important distinction to understand: moving the registration is not the same as changing where your website or business email runs.
Transfer a domain to another registrar: the essential steps
Confirm that you control the domain registration and can access the registered contact email. Check transfer restrictions, record existing DNS settings and obtain the required authorisation code. Start the transfer through the receiving registrar, approve legitimate confirmation requests and verify the domain, website and email afterwards. Do not cancel the existing registration prematurely.
Understand what a registrar actually does
A domain registrar manages the registration of your internet address.
For example, if your business uses example.es, the registrar is the company through which you manage that registration.
The website itself may run on a different hosting platform. Your email could be provided by another company again.
Changing registrars does not inherently mean that you must redesign the website, migrate its code or replace the email service.
This distinction matters when someone tells you that changing providers requires rebuilding everything.
Ask exactly which service is being moved.
If your goal is simply to change your website hosting, you may be able to keep the current registrar.
If you want better control over renewals, billing and domain access, then transferring the registration may make sense.
Start by identifying the current provider and checking whether the domain is registered to the correct person or business.
You should also know who has administrative access and which email address receives official notifications.
Check ownership and contact details first
Log in to the existing registrar dashboard.
Confirm the domain name, expiration date, registrant details and available transfer controls.
If you do not know the registrar, ICANN provides a domain registration lookup service that can help identify the provider for supported registrations.
Some registration details may not be publicly visible because of privacy protections.
If the domain is held in a former contractor's account, contact that person or the registrar to establish the proper transfer procedure.
Do not assume that paying for a website automatically gives you administrative access to the domain.
If you need to change the registered holder as well as the registrar, ask which procedure should happen first.
For some generic top-level domains, changing registrant details can trigger a transfer restriction. Making an apparently harmless contact update immediately before requesting a transfer could therefore delay the move.
If you operate through a Spanish company or as an autónomo, keep the registration details consistent with the actual holder of the domain.
Do not transfer ownership to an unrelated individual simply because that person is available to manage the account.
What is an authorisation or EPP code?
Many domain transfers require an authorisation code, sometimes called an Auth-Code, AuthInfo code or EPP code.
The code helps verify that the transfer request is authorised.
For generic top-level domains covered by ICANN's transfer rules, the current registrar provides a process for obtaining it.
You may find it in the dashboard or need to request it from support.
Treat this code as sensitive. Do not publish it in a shared document, support screenshot or public message.
The receiving registrar will normally explain where to enter it.
The precise procedure depends on the domain extension and registry rules.
For example, a .com domain and a Spanish .es domain should not automatically be assumed to follow identical transfer workflows.
Check the instructions applicable to your extension before beginning.
You can consult ICANN's official domain transfer FAQ for generic domains covered by its policies.
Why might a transfer be blocked?
Domain transfer restrictions are not always evidence that a provider is trying to prevent you from leaving.
For certain generic top-level domains, ICANN rules include restrictions relating to recent registrations, previous transfers and changes of registrant.
A 60-day restriction may apply in circumstances covered by those policies. Some situations allow an opt-out, while others do not.
That does not mean every domain extension follows the same rule.
Check the applicable registry and registrar conditions.
A domain may also have a transfer lock enabled for security. Removing that lock is usually a separate step from obtaining the authorisation code.
If your transfer request is rejected, ask the provider for the specific reason.
Do not repeatedly change contact information or DNS records while trying to resolve it.
The restriction could be temporary, or additional authorisation may be required.
For a business that depends on its website, identifying the reason is safer than experimenting with settings.
How to keep your website and email working
The main technical concern during a registrar change is preserving the domain's DNS configuration.
DNS records direct different requests to the appropriate services.
Some records are used for the website. Others manage email delivery or verify ownership for external platforms.
Changing the registrar does not necessarily require changing those records, but it may affect where they are managed.
Before starting, document the current nameservers and important DNS entries.
Ask the receiving registrar whether the existing DNS hosting will remain unchanged during the transfer.
If you are also moving DNS management, prepare the equivalent configuration before switching.
Pay particular attention to email-related records such as MX, SPF, DKIM and DMARC.
A website can continue loading while email delivery fails because an important record was omitted.
Do not assume that successful domain transfer confirmation means every connected service works.
A checklist for the transfer process
These checks help separate administrative progress from the technical result.
| Step | Action | Main risk to avoid |
|---|---|---|
| 1 | Verify registrar and account access | Starting without proper authorisation |
| 2 | Record DNS and email settings | Losing critical configuration |
| 3 | Check domain restrictions | Requesting a transfer that cannot proceed |
| 4 | Obtain the authorisation code | Sharing sensitive information |
| 5 | Initiate the receiving registrar's process | Missing confirmation messages |
| 6 | Test connected services | Assuming the transfer guarantees availability |
Keep the old registrar account accessible until the process is complete.
Do not remove payment details, cancel services or close the account simply because you have submitted the request.
Some providers bundle domain registration with additional products.
Check which subscriptions are independent and which might need separate handling.
A domain transfer should be completed deliberately, not as part of a rushed account cleanup.
Do I need to change my hosting too?
No.
If your website is performing well and your only concern is registrar billing or access, there may be no reason to move its hosting.
Likewise, you do not need to change domain registrars merely because you are switching website developers.
Ask the new developer what access is actually required.
In many situations, appropriate DNS permissions or a limited collaboration role are enough.
There is also a difference between transferring a domain to another registrar and transferring its legal or administrative ownership to another person.
If you are selling a business, changing legal entities or transferring the brand, clarify which transaction you actually need.
Those changes can have contractual and administrative consequences beyond the technical transfer.
How to check the result after transferring
Start with the receiving registrar dashboard.
Confirm that the domain appears in the correct account and that its registration information and renewal settings are accurate.
Then test the website from a normal browser and a mobile connection.
Open both the main domain and any configured www address. Check important internal links and HTTPS.
Send a test email from an unrelated account to your business address. Reply to confirm that outbound email also works.
If you use forms, booking tools or third-party services connected to the domain, test them as well.
Check any verification records needed for Google Search Console or other business platforms.
Keep your documented DNS configuration available for comparison if something fails.
Do not rely solely on a dashboard message saying the transfer is complete.
A successful administrative transfer and a functioning website are related but distinct outcomes.
When you should leave the domain where it is
If the current registrar is reliable, the business controls the account and renewals work properly, transferring may offer little practical benefit.
You also might want to postpone a transfer when the domain is close to an important business launch or you do not have reliable access to the relevant accounts.
There is no requirement to consolidate every online service under a single provider.
A business may reasonably use separate companies for domain registration, hosting and email.
At Skyba Tech, the client receives the website code, and the domain and hosting are registered in the client's name. That helps avoid unnecessary dependency on a particular developer.
Transfer a domain to another registrar only when it solves a real administrative or operational need. Preserve the existing configuration and verify the connected services afterwards.
If you are changing providers and need help understanding which parts of your setup should move, contact Skyba Tech on WhatsApp.