Keep the registrar when you change hosts (transfer later, not on day one)

The most expensive domain mistake a local shop makes is not picking the “wrong” registrar. It is treating the domain like a feature of whichever website tool they tried this year. When the builder gets annoying, they transfer the name to the next host. Mail breaks. The old page lingers. Someone forgets to renew during the lock period. The name that should have been boring infrastructure becomes a project.

This guide is the policy we want you to adopt: the registrar is home. Hosts and builders are tenants. Namecheap, on this lander, is the default home. You can point at a new tenant without moving house. Transfers exist for real reasons. Day one is not a real reason. Neither is a chat agent who needs the name in their account to “finish setup.”

Why the name and the site should be separate

A website tool can be replaced in an afternoon: export the copy, rebuild a page, point DNS. A domain that expires, or that sits in an account whose password died with a former employee, can take the business’s public identity with it. Search listings, email addresses, and printed materials all assume the name is stable. Stability comes from a registrar account you still control, with auto-renew on, not from a host’s convenience transfer.

Hosts like transfers because a transferred name has friction on the way out. That friction is your future problem. ICANN rules give you a way out anyway — unlock, authorization code, wait — but “anyway” can include a 60-day transfer lock after a change of registrant. If you transferred last month in a hurry, you may not be able to transfer again this month. Pointing DNS has no such drama.

When a transfer is actually justified

• The current registrar account is genuinely unusable: owner is gone, two-factor is locked, support cannot recover it.
• The registrar is charging a renewal that you have compared, live, against Namecheap’s published renew, and the difference is worth the operational risk.
• You are consolidating many names into one account you will actually maintain — not a hobby of shuffling one .com.
• A legal or accounting change requires the name in a different entity’s account, and you have time to do it without a launch deadline.

“The host said I have to” is not on that list. Ask them for DNS records instead. If they cannot connect a domain you keep at Namecheap, they are a weak host, not a mandatory registrar. “I want one login” can be a real preference — that is the GoDaddy-shaped Saturday on Start A Site — but it is a reason to have bought there originally, not a reason to transfer a healthy Namecheap name this afternoon.

What a transfer feels like (without a fake tutorial)

At a high level, you unlock the name at the current registrar, disable privacy if the gaining registrar’s process requires it (rules vary; follow the current registrar’s transfer guide), request an authorization code, and start the transfer at the gaining registrar. Then you wait. There is often an email to approve. There is often a period where you should not also try to change DNS for fun. We will not paste a click-path that will be wrong next quarter. Namecheap documents incoming and outgoing transfers in their knowledgebase. Use that. If you are leaving somewhere else toward Namecheap, still wait until you are not also launching a site the same day.

Locks, 60-day windows, and expired names

Registrar lock exists to stop theft. Leave it on except during an intentional transfer. The 60-day inter-registrar transfer lock after registration or after certain contact changes is an ICANN-related rule, not a Namecheap prank. If you just bought the name, you may not be able to move it immediately. Good. You should not be moving it immediately.

Expired names enter a grace and then a redemption process that costs more and panics more. Auto-renew exists to keep you out of that process. If you are already in it, pay the registrar what they ask to restore, then turn auto-renew on, then consider whether you still want to transfer. Restoring and transferring at the same time is how people double-pay and still miss a week of mail.

A one-paragraph policy you can stick on the fridge

The .com lives at Namecheap unless we have a written reason to move it. Website tools may change. DNS may change. The registrar login stays in the password manager under the LLC’s name. Auto-renew stays on. Privacy stays on. We do not transfer to make a chat agent happy. We do not transfer in the same week as a launch. That policy will outlast this guide’s screenshots — which is why this guide has none — and it will outlast the host you are about to try next winter.

If you are still deciding whether Namecheap is the right home in the first place, read the comparison with GoDaddy. If you already bought elsewhere and the account is healthy, stay. This lander’s default is for people who need a first registrar, not for people who need a hobby.