Transferring a domain between registrars sounds scarier than it is. The horror stories you've read online almost always trace back to one thing: someone let the site or email go down during the switch because they moved DNS and registrar at the same time, or they let the domain expire mid-transfer. Do it in the right order and a domain transfer to SkyServer is a non-event — visitors never notice, mail keeps flowing, and you end up with your domain and hosting under one roof.
Why Transfers Go Wrong (and How to Avoid It)
A domain transfer moves the registration of your domain from one registrar to another. It does not, by itself, touch your website or email — those are controlled by DNS, which lives separately. The downtime people experience almost always comes from one of these:
- Changing nameservers and initiating the registrar transfer on the same day, so DNS is mid-propagation while the transfer is also processing
- Letting the domain sit inside its 60-day post-registration or post-transfer lock window, then panicking when the transfer gets rejected
- Forgetting to renew before initiating, so the domain expires while it's "in transit" between registrars
- Not lowering the DNS TTL beforehand, so any change takes hours instead of minutes to take effect
The fix for all four is sequencing: get DNS stable and pointed at SkyServer first, confirm the site and mail work from the new setup, and only then move the registration itself. The registration change is invisible to visitors — it's a change of who administers the domain, not where it points.
Step 1: Set Up Hosting at SkyServer Before You Touch the Registrar
Get your site and mailboxes fully working on SkyServer under the domain's existing DNS, using either of these approaches:
- Test via hosts file or a temp subdomain first. Point your local hosts file at the new server IP, or use a throwaway subdomain like
preview.yourdomain.compointed at SkyServer, and confirm the site renders correctly. - Lower your DNS TTL 24-48 hours ahead of the cutover. Log in to wherever your DNS currently lives and drop the TTL on your A, MX, and CNAME records to 300 seconds (5 minutes). This is the single most useful thing you can do to shrink downtime — it means when you do flip records, resolvers worldwide pick up the change fast instead of caching the old answer for a day.
Once your SkyServer hosting account is provisioned, upload your site files and import your database (our cPanel backups and restore guide covers this if you're migrating an existing site) before changing a single DNS record live.
Step 2: Cut Over DNS — Not the Registrar Yet
With hosting ready and TTL already low, update the records that matter, in this order:
| Record | Change | Why first |
|---|---|---|
| A record | Point to SkyServer's server IP | Gets the website live on the new host |
| MX records | Point to SkyServer's mail servers (if hosting email here too) | Keeps mail delivering without a gap |
| SPF/DKIM/DMARC | Update to reference SkyServer's sending infrastructure | Prevents mail landing in spam mid-switch |
| CNAME/subdomains | Repoint any that serve live traffic | Covers staging, mail.yourdomain.com, etc. |
Watch propagation with a quick check:
dig yourdomain.com A +short
dig yourdomain.com MX +shortRun that from a couple of different networks (your office wifi and your phone on mobile data give you two different resolver caches) until both show the SkyServer values consistently. Give it a few hours before moving to the next step even with a low TTL — some ISP resolvers ignore TTL and cache longer than they should.
Step 3: Unlock the Domain and Get Your Auth Code
Now that traffic is confirmed live on SkyServer, initiate the actual registration transfer at your current (losing) registrar:
- Log in to the current registrar's panel and find Transfer Lock or Registrar Lock — switch it off. Every domain ships with this on by default to stop unauthorized transfers.
- Request the EPP code (also called an auth code or transfer code). It's usually emailed to the domain's registrant contact address within a few minutes, sometimes up to an hour.
- Confirm WHOIS privacy isn't blocking the transfer email — if your registrant email on file is stale, update it first or you'll never receive the code.
- Check the domain isn't inside a lock window: ICANN blocks transfers for 60 days after initial registration and 60 days after a previous transfer. If you registered or last transferred recently, you'll need to wait it out.
None of this touches your live site. DNS is already pointed at SkyServer, so the site and mail keep running exactly as they were in Step 2 while you sort out the registrar side.
Step 4: Initiate the Transfer to SkyServer
With the domain unlocked and EPP code in hand, submit the transfer request through your SkyServer account, entering the auth code when prompted. From here:
- You'll get an approval email at the registrant address — confirm it promptly, since most registries auto-cancel unconfirmed transfers after 5 days.
- The losing registrar may also send a "someone is transferring your domain away" notice with a link to approve or reject. Approving it speeds things up; ignoring it usually means the transfer auto-completes after 5-7 days anyway (ICANN's default), unless the losing registrar deliberately rejects it.
- The transfer typically completes in 1-7 days depending on the TLD and how fast both sides respond. Country-code TLDs like
.insometimes use a different process — a direct "change of registrant/registrar" form instead of the ICANN EPP flow — so check what your specific TLD requires.
Since DNS was already moved in Step 2, nothing changes on the visitor-facing side while this processes in the background.
Step 5: Verify and Clean Up
Once the transfer confirms in your SkyServer account:
- Check
whois yourdomain.comshows SkyServer (or your chosen registrar) as the new registrar of record - Confirm nameservers/DNS records are still exactly what you set in Step 2 — some registrars reset DNS to their own defaults during transfer, which would silently take your site down
- Restore your TTL to a normal value (3600 or higher) once everything's stable — there's no need to keep it at 5 minutes long-term
- Set the new domain to auto-renew so you don't relive any of this by accident next year
If your site or mail does go down mid-transfer, it's almost always the DNS records reverting to a registrar default, not the transfer itself. Check your A and MX records first before assuming something bigger broke.
What About Domains That Only Need New Nameservers, Not a Full Transfer?
If you're happy keeping your domain registered where it is and just want it pointed at SkyServer hosting, you don't need any of the EPP code process above — that's a much simpler nameserver or A record change, which we cover separately in our "Pointing Your Domain to SkyServer" guide. Use the full transfer process in this article only when you actually want the registration itself — renewals, billing, management — to move to SkyServer.
Frequently Asked Questions
How long does a domain transfer actually take?
Most gTLDs (.com, .net, .org) complete in 5-7 days by default under ICANN rules, though approving the confirmation email promptly can shorten this. Some registrars offer expedited transfers that finish in a few hours once the auth code is verified. Country-code TLDs vary widely — some complete same-day, others take longer.
Will my email stop working during the transfer?
Not if you follow the sequence above. Email delivery depends on your MX records, not on who your registrar is. As long as MX records already point to SkyServer before you start the registrar transfer, mail keeps flowing throughout.
What if I can't get the EPP code from my old registrar?
Some registrars require you to disable privacy protection or verify your identity before releasing it. If the registrant email is outdated, update your WHOIS contact details first, then re-request the code. As a last resort, most registrars have a support ticket process specifically for stuck EPP code requests.
Can I transfer a domain that was registered less than 60 days ago?
No — ICANN enforces a mandatory 60-day lock after initial registration (and again after any transfer) during which the domain can't move registrars. You'll need to wait out the lock period before initiating a transfer.
Do I need to change my nameservers before or after the transfer completes?
Before. Get your A, MX, and other DNS records pointed at SkyServer and fully verified while the domain is still with your old registrar. The registration transfer itself should be the last step, once you've already confirmed everything resolves correctly.
