A registrar transfer changes who manages the registration; it does not require changing the website, DNS or email. Keeping those layers unchanged is the safest way to make the transfer uneventful.
Clarify what is being transferred
A registrar transfer is different from changing the registrant, moving the website or changing DNS hosting. Write down the objective. If the real problem is poor hosting, transferring the domain may not solve it.
Prepare the domain
- Confirm the business controls the current registrar account and recovery email.
- Check the domain status, expiry date and any transfer lock.
- Record nameservers and export the DNS zone.
- Check whether recent registration or contact changes affect transfer eligibility.
- Create the receiving registrar account under business control.
- Keep the existing website and email services active.
Follow the registry-specific process
The exact transfer mechanism differs between .UK domains and generic domains such as .com. Use the current instructions from the registry and both registrars. Do not copy an authorisation-code procedure from one namespace and assume it applies to another.
Verify before and after
| Check | Expected result |
|---|---|
| Nameservers | Unchanged unless a separate DNS move was approved |
| Website | Loads over HTTPS on important pages |
| Inbound and outbound delivery continue | |
| Registrant | Correct legal or business details remain |
| Renewal | Expiry and payment method are confirmed at the new registrar |
Close the old relationship carefully
Do not delete the old registrar account until invoices, transfer confirmation and historical records are saved. Remove obsolete payment methods and access only after the receiving account has been tested.
Choose the timing
Avoid transferring a domain immediately before a major campaign, renewal deadline or company closure period. Although a registrar transfer should not alter DNS, support delays, account locks or misunderstood approval messages can still create risk. Leave enough time to resolve identity checks without pressure.
If a wider migration is planned, transfer the registrar and move the website in separate stages. Confirm stability after the first change before starting the next. This keeps the cause of any failure visible and makes rollback simpler.
Final publication check
- The task is a registrar transfer, not an unplanned DNS or hosting move.
- The current zone and registration evidence are saved.
- Website and email work before and after the transfer.
- The old account is retained until confirmation and records are complete.
Sources and date checked
Technical and policy information was checked on 21 July 2026. Recheck provider-specific procedures before making a live change.
Keep the decision under your control
Retain the relevant accounts, source material, supplier terms and recovery information. Recheck changing prices, interfaces and rules before acting.