10% off every plan until October — because my rent's due.
BasicBS.
Back to blog

Transfer a Domain Without Downtime for UK Small Businesses in a Week

Decorative domain transfer title card

Start a transfer by choosing your new registrar and asking your current registrar for an AuthInfo or Transfer Authorisation Code, that single action begins the process. A clean transfer means the domain moves registrars without your website or email dropping offline, and it typically finishes within a handful of days once the code is confirmed. Before you touch anything, check for locks or recent registrant changes and sort those first, they’re the most common reason transfers stall.

TL;DR:

  • Removing a transfer lock and ensuring the registrant and admin emails are monitored are crucial steps to prevent delays in the process.
  • Most domain transfers, including .UKs, take about a week from FOA approval to completion, but DNS caching delays can cause temporary visibility issues.
  • Registrar fees for transfers typically include a renewal extension equal to the remaining registration period, with additional costs usually minimal for code unlocking.
  • Country-code domains like .UK now follow a pull-style TAC system, making transfers similar to generic domains, though extra verification may apply for premium names.
  • Leaving DNS records unchanged during transfer ensures website and email continuity, with optional TTL reduction and overlap testing recommended for a smooth switch.
BasicBS
Keep Your Website Moving
BasicBS builds high performing websites with managed UK hosting, SSL and ongoing updates for straightforward online continuity.
Visit BasicBS

Table of Contents

Step-by-step transfer checklist you can follow in order

Domain transfers follow a predictable sequence, and most delays come from skipping a step rather than the process itself being difficult. Work through this in order and you’ll avoid the usual headaches.

  1. Open an account with your chosen new registrar and read its transfer terms, including any renewal-on-transfer policy.
  2. Check that the registrant and admin contact emails on the current registration are live inboxes you actually check.
  3. Request the AuthInfo code (called a Transfer Authorisation Code, or TAC, for .UK domains) from your current registrar and ask how long delivery usually takes.
  4. Start the transfer with the new registrar using that code, and pay any transfer fee requested at this stage.
  5. Watch your inbox for confirmation emails from both registrars and reply promptly, delays here are the single biggest cause of failed transfers.
  6. Keep a record of every message and timestamp in case anything needs disputing later.
  7. Decide whether you want a year added to your registration during the transfer, most registrars offer this as an option and it’s worth confirming rather than assuming.

None of this is complicated, but it’s unforgiving of inattention. A code that sits unused, or a confirmation email that lands in spam, can turn a two-day job into a two-week one. If you’d rather someone else run this checklist for you, that’s a service worth asking about when you’re choosing a new host, more on that further down.

Pre-transfer checks that stop delays before they start

Most stuck transfers trace back to one of a handful of avoidable problems. Run through these before you request a code.

  • Make sure the registrant and admin email addresses are correct and monitored, every confirmation step depends on them.
  • Check the domain’s status code for ClientTransferProhibited, this is a standard lock and needs removing at the current registrar before a transfer can begin.
  • Look out for pendingDelete or redemption status, these mean the domain has lapsed and needs restoring first, not transferring.
  • Remember the 60 day change-of-registrant lock: if you’ve recently updated the owner’s name or organisation on the registration, wait it out rather than trying to transfer straight away.
  • Confirm the domain isn’t tied up in a dispute or subject to a court order, either of which will block a transfer outright.

Sorting these first means the transfer itself becomes a formality rather than a fight.

How AuthInfo codes and FOAs actually work

An AuthInfo code, known as a Transfer Authorisation Code (TAC) for .UK domains, is a unique password proving you control the domain and authorise its move. Without it, nobody can take your domain away from you, which is the whole point. Under ICANN’s transfer policy, your current registrar must hand over this code, or remove a transfer lock, within five calendar days of your request if it doesn’t offer instant self-service access.

Codes are generally single-use and often time-limited, so request one only when you’re ready to move. The gaining registrar will usually also send a Form of Authorisation (FOA), a confirmation email you need to approve before anything proceeds.

For .UK domains specifically, Nominet has moved the registry from a push-based system to a pull-style process built around TACs, bringing .UK transfers closer in shape to how most generic top-level domains already work, though the terminology and some steps still differ slightly.

How AuthInfo codes and FOAs actually work — overview diagram

How long a domain transfer takes and when to chase it up

A straightforward transfer usually completes within about a week from the moment you approve the FOA, though the exact timing varies by registrar and top-level domain. The stages are the request, the FOA approval window, the registry update, and then notification to both parties that it’s done.

Registry completion and visible completion aren’t the same thing. Even after a registry confirms a transfer, DNS caching can mean the change isn’t visible to every visitor straight away, a lesson borne out by the .gov.uk registry’s own migration, which needed staged testing precisely because of this lag.

If a transfer hasn’t completed within the expected window, contact both your gaining and losing registrars directly. For genuinely urgent cases, registrars can use the Transfer Emergency Action Contact (TEAC) route to resolve things faster between themselves.

DNS and email continuity: keeping your site and inbox alive

The safest move during a domain transfer is to leave your nameservers exactly as they are, the registrar changes but the DNS records pointing to your website and email don’t need to move at the same time.

  • If you do plan DNS changes, lower your TTL values 48 to 72 hours beforehand so any update propagates faster.
  • Have your destination host’s DNS records prepared and ready before cutover, not built on the day.
  • Keep a backup of your MX records and SPF/DKIM settings, and leave your old hosting live until you’ve confirmed everything works.
  • Check propagation from more than one location or ISP using tools like dig or nslookup, a single check from your own laptop can be misleading.

Pro Tip: Test your new DNS settings against the old hosting still running before you switch anything off, that overlap window is your safety net.

What to do if a transfer is denied or gets stuck

Registrars can legitimately refuse a transfer for a limited set of reasons, and under ICANN policy they must tell you why.

  • Common denial reasons include suspected fraud, a pending UDRP dispute, or the domain having been registered or transferred within the last 60 days.
  • If you believe a denial is wrong, gather your correspondence and timestamps, then push both registrars to use the TEAC route for a faster resolution.
  • For unresolved cases, you can file a compliance complaint with the registry or with ICANN directly, including your domain name, the registrars involved, and copies of the denial notice.

Keep every email. A paper trail is the difference between a five-minute phone call and a drawn-out dispute.

How BasicBS handles the technical bits for you

If all of this sounds like more admin than you fancy, that’s exactly the gap we fill. BasicBS handles domain sourcing and transfer as part of building your site, so you’re not juggling AuthInfo codes and FOA emails on top of running your business. We pair that with managed UK hosting, SSL included, AI search training, so your business shows up when people ask ChatGPT and similar tools for a local recommendation, and monthly updates that keep things ticking over.

Sites typically go live in 5 to 7 working days, with pricing kept transparent from the start rather than buried in a quote you have to chase. It’s the same “cut the rubbish” approach we apply to everything: no vague promises, just the fundamentals done properly.

What a domain transfer actually costs

Most registrars charge a transfer fee that usually includes a one year renewal added on top of your remaining registration term, so you’re not paying twice for the same period. Prices vary by registrar and by top-level domain, some charge nothing at all for certain TLDs while others bundle the fee into their standard renewal price. Nominet’s own .UK registry policy notes that transferring can be free at registry level, with individual registrars deciding whether to pass on their own handling charge.

Beyond the transfer fee itself, watch for anything charged by your current registrar to unlock the domain or release the code, this should be free or nominal, and any registrar demanding a steep fee just to hand over a code you’re entitled to is worth double-checking against ICANN’s rules. There’s rarely a reason to pay more than a modest, one-off amount for the move itself.

What a domain transfer actually costs — overview diagram

Transferring country-code domains and premium names

Not every domain moves the same way. Country-code top-level domains, like .UK, often run their own registry rules on top of the general ICANN framework. .UK domains use a pull-style TAC system rather than the older push method still used by some ccTLDs, which changes who initiates the final step and how long a TAC stays valid.

Premium domains, ones with a higher resale value because of their length or wording, transfer through the same mechanical process but often come with extra verification from the registrar to confirm you’re the legitimate registrant, given how often these names are targeted by scammers. If you’ve bought a premium domain from a marketplace or broker, check whether there’s an escrow step involved before the transfer proper even begins.

Domain privacy and WHOIS data during a transfer

If you’ve got WHOIS privacy switched on, most registrars will ask you to temporarily disable it before initiating a transfer, since the gaining registrar needs to verify the underlying contact details behind the privacy service. This isn’t a security risk in itself, it’s a verification step, and reputable registrars will let you switch privacy protection straight back on once the transfer completes.

Your WHOIS contact details themselves don’t usually change during a transfer unless you update them separately, but it’s worth checking they’re accurate beforehand. Outdated details are one of the quieter reasons transfers get held up, since confirmation emails simply go nowhere.

What to check once the transfer is complete

Once your registrar confirms the move, log in to the new account and check the domain’s expiry date, nameservers, and contact details all look right. Confirm your website and email are both still working from at least two different networks, not just the one in your office.

From here, treat renewal as the new registrar’s job, set a reminder or enable auto-renew so the domain doesn’t lapse under a system you’re not yet used to watching. If you’re also updating DNS settings now that the dust has settled, do it gradually and keep the old records noted down until you’re confident everything’s resolved.

Recurring mistakes we see, and one habit worth adopting

The mistake we see most often is people updating registrant details right before a transfer, not realising that triggers the 60 day lock and stalls everything. The fix is simple: check your registrant and admin emails are correct and monitored 72 hours before you start, not after. Keep a running note of every message and timestamp too, it costs nothing and saves real grief if anything gets disputed later.

— Rhys

Want the whole thing handled for you?

If you’d rather not be the one chasing AuthInfo codes and FOA emails, we’ll do it as part of building your new site. We handle domain transfer, provide managed hosting with SSL included, and aim to get your site live within a few working days, avoiding large agency fees.

BasicBS

Our Website Sale! plan offers low-cost monthly payments with no upfront cost and straightforward contract terms.

What you get Detail
Domain transfer handling Included as part of the build
Hosting Managed UK hosting with SSL
Turnaround 5 to 7 working days
Website Sale! plan £10 per month

Have a look at examples of sites we’ve built or head straight to the current website packages to get started. If you’re weighing this up against a DIY builder or a traditional agency quote, our page on why cheap website development fails is worth a read before you decide. And if you end up needing extra server capacity once your new site’s live, AceRDP’s VPS hosting is a solid option worth knowing about.

Sources

FAQ

Do I have to wait 60 days to transfer a domain?

Only if you’ve recently changed the registrant’s name or organisation on the registration, which triggers a 60 day change-of-registrant lock. If you haven’t touched those details, there’s no such wait and you can start a transfer as soon as you have your AuthInfo code.

How do I transfer one domain to another registrar?

Choose your new registrar, request the AuthInfo or TAC code from your current one, then use that code to start the transfer at the new registrar and confirm via the Form of Authorisation email. Most transfers complete within about a week once the code and confirmation are sorted.

Will I lose my email if I transfer my domain?

Not if you leave your nameservers unchanged during the move, since your email records travel with the domain rather than the registrar account. Keep your old hosting active until you’ve confirmed everything’s working on the new setup, just as a safety net.

Will my website go down during a domain transfer?

It shouldn’t, provided your DNS records and nameservers stay untouched throughout the process, since the transfer changes who manages the domain, not where it points. Any visible downtime usually comes from unrelated DNS changes made at the same time, not the transfer itself.

Back to blog