How to transfer your domain to another provider without taking your site down

Yes, you can move a domain to another provider without taking your site down — but only if you understand one thing: a transfer moves the domain registration (who administers it and who pays the renewal), not the site or the email. The site stays online as long as the DNS records stay the same. The golden rule: first make sure that where the domain points (DNS, hosting, email) doesn't change, and only then start the transfer from one registrar to another.

What you're actually moving: domain, DNS, hosting and email aren't the same thing

Most "sites that went down" during a transfer come from this confusion. Let's separate them clearly:

• The domain = the name (e.g. firma.ro). A registrar administers it. The transfer only moves who owns it in which account.
• DNS = the "phone book" that says where the site and the email live (A, CNAME, MX, TXT records). The site lives or dies by DNS, not by the registrar.
• Hosting = the server where the site's files sit.
• Email = often at a different provider (Google Workspace, Microsoft 365, cPanel). It lives by the MX records.

If DNS stays unchanged during the transfer, the site and email don't even feel the move.

Why you need a transfer code (EPP / authcode)

The transfer code — called an EPP code, authcode or authorization code — is a one-time password your current provider gives you. Without it, the new provider can't legally take over the domain. You request it from the old registrar's panel or via a support ticket; it usually arrives at the domain's contact email within minutes to a few hours.

Watch out for .ro domains: the procedure at ROTLD (the national registry) differs from that of international domains (.com, .net). For many .ro domains the transfer is done via request and confirmation, not a classic EPP code. Ask your current provider explicitly what the procedure is for your extension.

The steps, in the right order

1. Check who the real owner is. Open the account at the current registrar and confirm you have access. If the domain is "with the company that built your site," ask them for access or the transfer before anything else.

2. Write down your current DNS. Take a screenshot of every record: A, CNAME, MX, TXT (especially SPF/DKIM for email). This is your safety net.

3. Unlock the domain. Turn off "Domain Lock" / "Transfer Lock" in the old panel.

4. Disable WHOIS Privacy (if active) — it can sometimes block receiving the code or the confirmation email.

5. Request the EPP / authcode.

6. Start the transfer at the new provider and enter the code.

7. Confirm from the contact email. You'll get an approval email — click the link. This is where most transfers stall: the contact email is old and nobody reads it.

8. Don't cancel payment / don't let the domain expire during the transfer.

9. Once done, check the DNS and, if needed, re-enter the records from step 2.

What to check before, during and after

How long it actually takes

For international domains (.com, .net) the transfer usually takes 5–7 days, because of a confirmation window imposed by ICANN — even if you confirm in 2 minutes. For .ro it can be faster or slower, depending on the provider's procedure. Importantly: the site is NOT offline during this time, as long as DNS stays unchanged. The transfer runs "in the background."

The real risks (and how to avoid them)

• DNS reset to default. Some providers, on receiving the domain, put their own empty DNS on it → site and email go down. Antidote: note the DNS before and check immediately after.
• Lost confirmation email. The contact email is old/nonexistent → the transfer silently expires. Antidote: update the contact email before you start.
• The domain expires mid-transfer. Renew it first, transfer afterward.
• The 60-day lock. A freshly registered or transferred domain can't be moved again for 60 days.
• Losing email (MX + SPF/DKIM). The most commonly forgotten. Without correct MX, you stop receiving mail. Check them explicitly afterward.

Since the domain is yours and you can move it anytime, it's worth treating this carefully — a lost domain is far more expensive to recover than to keep. If you want to understand at a deeper level why your own site, on your own domain, is safer than a page on a rented platform, read why do I need a website.

When it's worth doing the move yourself and when to ask for help

If you have a simple landing page with no email on the domain, you can do the move yourself with peace of mind. If the domain carries business email, an online store or multiple DNS records (Workspace, payments, verifications), a 5-minute mistake can leave you without email for a day. That's where a hand from someone who's done it before pays off.

At MPO Web Studio — a team in Cluj-Napoca, 100% remote across Romania — we do exactly this move for clients all the time: we take over the domain, keep the DNS and email intact, and check everything afterward. If you want us to move your domain stress-free, or you just want a second opinion before you hit "transfer," write to us on WhatsApp and we'll give you a free demo or check: wa.me/40750257140.