Move or Stay
Domain transfer vs renewal — when moving the name beats renewing it where it sits
Every renewal notice is also a decision point. For most gTLDs a transfer carries a year of term with it, which makes moving registrar a form of renewing — somewhere better.
The short answer
Renew in place when your registrar is treating you well: honest renewal rates, no fees to leave, DNS you can edit freely. Transfer instead when any of those fail — because for most gTLDs the transfer itself extends the registration by a year, so you are not paying to move, you are choosing where next year's renewal lives.
Timing is the whole craft. Start a transfer well before expiry, never inside the final days; respect the sixty-day locks after registration and after any previous transfer; and know that ccTLDs like .uk play by different rules, moving by IPS tag without the year attached. The rest of this page is that craft written down.
By the Hosting & Domains team · Reviewed 25 August 2026
+1 year
Term extension on most gTLD transfers
60 days
Lock after registration or transfer
10 years
Registry ceiling on total term
Zero
Downtime a correct transfer causes
Registrars meet two kinds of leavers: the ones moving towards something — better rates, saner DNS tools, one consolidated account — and the ones fleeing a renewal notice that bore no resemblance to the price they registered at. Both are well served by understanding what a transfer actually is: a change of which company manages the registration, with the registry record, the delegation and the website untouched.
The comparison with renewal is closer than most owners realise, because under ICANN's transfer policy a gTLD transfer includes a year's extension of the term in most cases. That single fact reframes the renewal notice: the question is not 'shall I pay to keep the name' but 'who deserves to be holding it when I do'.
What a transfer moves, and what it leaves alone
A transfer changes one thing: the registrar of record. The registry entry persists, the nameserver delegation persists, and therefore the website and mail keep resolving exactly as before, throughout.
What can change as a side effect is DNS hosting. If your zone was hosted on the old registrar's nameservers, plan its move deliberately — copy the records first, or the transfer completes and the zone that answers for you is still sitting at a company you have just left.
The mechanism for gTLDs is the auth code (EPP code): request it from the current registrar, present it to the new one, approve the confirmation, and the registries do the rest over a few days.
The year that travels with the transfer
For most generic endings, a completed transfer extends the registration by one year, added to whatever term remained. Transfer a name with eight months left and it emerges with a year and eight months.
That is why transferring near — but not at — renewal time is the classic move: the renewal you were about to buy happens as part of the transfer, at the receiving registrar's rate.
The exception to file away: country codes make their own rules. A .uk moves by IPS tag change, usually within hours, with no year attached and no code involved — the renewal there stays a separate transaction.
The locks and the calendar
Two sixty-day locks govern gTLD moves: one after initial registration, one after any previous transfer, both registry policy rather than registrar spite. A change to the registrant's name or email can trigger a similar hold at many registrars, so make contact-detail changes well clear of any planned move.
The dangerous window is the final fortnight before expiry. A transfer initiated too late can straddle the expiry date, and an expired name adds grace-period complications no one enjoys. The rule: start moves at least a month out, or renew first and transfer at leisure — the remaining term travels with the name.
Unlock the name and disable privacy-forwarding hiccups before requesting the code: the commonest transfer failures are a still-enabled registrar lock and a confirmation email lost behind a privacy service's forwarding.
When staying put is right
A registrar that renews at the rate it advertised, releases codes promptly, and gives you full control of the zone has earned the renewal — consolidation for its own sake is churn, and every move is a small operational event.
Renew in place, too, when inside a lock window, when the name is mid-dispute, or when expiry is close enough that transfer timing gets tense: renew first, then move calmly if you still want to.
The test that settles it: ask your registrar what the name renews at and whether they release on request. Straight answers, stay if it suits you. Hedged answers — that is the renewal notice telling you where next year should live.
The renewal notice, read as an invitation
Owners treat the renewal notice as a bill; registrars read it as the annual moment the market gets to compete for a name. Because the gTLD transfer carries a year with it, accepting a better registrar's offer is not an extra cost on top of renewing — for most endings it largely is the renewing.
So run the annual check: current renewal rate against the rate elsewhere, code released without ceremony or not, zone editable or held hostage. Twenty minutes, once a year, and the name spends its life at whichever registrar keeps earning it.
- Transfers priced with the year of term shown plainly
- Auth-code and IPS-tag moves both handled start to finish
- Zone records copied before the switch, never after
- Renewal rates published where you can check them first
Why Hosting & Domains
Standard on every plan
The term arrives with the name
On most gTLD transfers the year's extension is part of the move — visible in your panel the moment the transfer completes.
No downtime by design
Delegation is untouched by a correct transfer; we copy DNS records across first so the zone's new home answers identically.
Locks checked before you start
We flag sixty-day windows, expiry proximity and privacy-forwarding traps before initiating, so moves complete first time.
Exit as easy as entry
Codes released on request, IPS tags changed same day, no departure fee — the standard we hold ourselves to, and you should hold anyone to.
Quick Start
Order placed to site online
- 1
Audit the incumbent
Renewal rate, release policy, DNS control. If all three pass, renew in place with a clear conscience.
- 2
Prepare the move
Copy the zone, unlock the name, confirm the registrant email works, request the auth code — a month or more before expiry.
- 3
Transfer and verify
Approve the confirmation, watch the term extend, then check nameservers, mail flow and WHOIS all read as expected.
Built In
Fitted to every plan
- Renewal rate at the current registrar checked against the market
- Sixty-day registration and transfer locks confirmed clear
- Zone records exported and rebuilt before any move
- Auth code requested with the registrant mailbox working
- Transfers started at least a month before expiry
- Term length verified in the panel after completion
Frequently Asked
The questions that come up most
Will my website or email go down during a transfer?
Not from the transfer itself — it changes the managing registrar, not the delegation, so resolution continues uninterrupted. Outages during transfers almost always trace to DNS hosted on the old registrar's nameservers being switched off after departure. Copy the zone to its new home first and the move is invisible to visitors.
Does transferring really add a year, or do I lose the time I already paid for?
For most gTLDs you keep the remaining term and gain a year on top when the transfer completes, up to the registry's ten-year ceiling. You lose nothing you have paid for. Country codes differ — a .uk transfer moves the name without touching the term — so check the ending's rules before assuming.
My registrar is slow releasing the auth code. What are my rights?
ICANN policy requires gTLD registrars to provide the code and not obstruct transfers; delay tactics are a compliance matter, not a negotiation. Request it in writing through the account, escalate to a complaint if it stalls, and treat the behaviour as confirmation the move is right. Legitimate holds exist only for the sixty-day windows and disputes.
Can I transfer a domain that has already expired?
Sometimes, but it is the hard road: during the grace period many registrars require renewal before release, and in redemption the name must be restored first at a steep registry fee. Far better to renew or transfer before the date — expiry is the most expensive place to make this decision.
How is transferring a .co.uk different?
Nominet's system uses IPS tags: the current registrar retags the name to the receiving registrar, and the move typically completes the same day, no auth code, no sixty-day lock, and no year added — renewal remains separate. It is one of the friendliest transfer systems anywhere, which is why UK names change registrar so casually.
Keep reading
Transfer a Domain
The transfer flow itself — auth codes, IPS tags, and the term extension shown before you start.
Multi-Year vs Annual Registration
The other lever on the same term: how far ahead to pay the registry at once.
Domain Prices
Transfer and renewal rates published per ending, so the annual audit takes minutes.
Jargon Buster
Auth codes, IPS tags, redemption, delegation — the vocabulary of moving names, defined.
Changing hosts? Run through our checklist first.
A plain order of work for a move nobody visiting will notice: which files go over first, how to carry the mail across without losing a message, when exactly to repoint DNS, and the two mistakes behind nearly every outage we are asked to rescue.
Renew where the name is treated best.
Bring the name over with its term intact and a year added on most endings — zone copied first, no downtime, exit always open.
View Transfer a Domain plans