Moving a domain between registrars without breaking anything

Portfolios spread across three registrars with three payment methods and three sets of notifications are how names expire by accident. Consolidating is worth the afternoon. The transfer is routine; the collateral damage is not.

What actually breaks

Not the transfer. What breaks is DNS — because many registrars provide DNS hosting as part of the package, and when the name leaves, that hosting stops. Every record disappears with it: the site goes down and mail stops, simultaneously, and it is not obvious why.

The fix is to deal with DNS before the transfer, not after.

Before you start

Record every DNS entry. Every record, its type, name, value, priority and TTL. Screenshot it as well as writing it down. This list is what you will rebuild from.

Decide where DNS will live. Either move it to an independent provider first — which is the cleaner arrangement long-term — or recreate every record at the new registrar before switching nameservers.

Check eligibility. Names cannot transfer within a restricted period after registration or after a previous transfer. Check expiry too: transferring very close to expiry is asking for trouble, and renewing first is cheaper than recovering afterwards.

Check the registrant contact. Confirmation messages go to the address on the record. If that mailbox no longer exists, fix it before you begin, not during.

The sequence

Unlock the name at the current registrar. Obtain the authorisation code. Start the transfer at the new registrar and pay — which normally adds a year to the registration rather than being a pure fee. Approve the confirmation message. Wait out the defined period.

Then verify: the name appears in the new account, the expiry date is right, the registrant details are intact, and the DNS records are all present and correct.

The safe pattern

Move DNS to an independent provider a week before the transfer. Confirm the site and mail work from that provider. Then transfer the registration.

This decouples the two changes entirely: if the transfer has a problem, nothing is down, and if DNS has a problem, you find out while the registration is still where it was. The alternative — changing both at once — means any failure is both harder to diagnose and live.

After it completes

Re-enable the registrar lock, which the transfer clears. Set renewal on a payment method that will still work next year. Verify the notification addresses reach a role rather than a person. Record the expiry somewhere independent of the registrar.

When not to transfer

Within the restricted window after a registration or a previous transfer — it will simply be refused. Very close to expiry. During anything critical: a launch, a campaign, a season where downtime costs real money.

And not all at once. Moving fifty names in one afternoon means fifty simultaneous DNS changes and no way to tell which one caused the problem. Move a few, verify, then continue.