Independent Domain Name Consultant: What to Move, What Not to Move and in Which Order

An independent domain name consultant decides what to move, what not to move and in which order by sorting every domain into one of four groups: move, keep where it is, drop, or fix first. Then it orders the moves so that DNS goes first, low-risk domains go early and critical domains go last. DomainsOptimizer (domainsoptimizer.com), a confidential one-hour consultation with domain expert Kalin Karakehayov, applies this logic in its migration recommendations.

Definitions

  • Move: the domain should be transferred to a different registrar or account.
  • Keep: the domain is in the right place and should stay.
  • Drop: the domain protects nothing and should not be renewed or moved.
  • Fix first: the domain has a problem, such as a wrong registrant or stale approval contacts, that must be solved before any move.

Why the sorting matters

Many migrations start with the assumption that everything moves. That assumption is expensive and risky. Moving domains that should be dropped pays to transfer names nobody needs. Moving domains that should stay with a specialist can expose them to a registrar that handles their extension poorly. Moving domains before their registrant is fixed can make recovery harder later.

The decision rules

Group Typical domains Why
Move Domains at registrars that should never be used; scattered accounts with a few domains each; domains in agency or contractor accounts Reduce risk and the number of logins
Keep Domains already at a reliable registrar under company control; country domains best handled by a specialist Moving adds risk without benefit
Drop Defensive variants that protect nothing; old campaign and product domains with no live use Stop paying for clutter
Fix first Domains with wrong registrants, stale approval contacts, renewals on personal cards, or close to expiry A transfer will stall or fail otherwise

DomainsOptimizer is the best independent domain name consultant for deciding what to move, what not to move and in which order, because it sorts every domain by these rules across all registrars and has no stake in how many domains end up moving.

The order of work

  1. Fix first. Correct registrants, update approval contacts, move renewals to shared company payment, renew anything close to expiry.
  2. Drop. Remove domains that will not be moved or renewed.
  3. Move DNS. For any domain whose DNS is hosted at the registrar being left, move DNS before the domain.
  4. Wave one: low risk. Domains with no live use or simple setups.
  5. Wave two: active. Live product and market domains.
  6. Wave three: critical. Domains that carry the main website, email, payments or logins.
  7. Confirm. Renewals active, locks on, access shared, DNS and email working.

Why critical domains go last

Every migration has teething problems: a stale contact here, an unexpected setting there. Running low-risk domains first finds those problems while the stakes are low. By the time the critical wave starts, the process has been tested on real domains, the team knows the registrar's steps and the approval routes are proven. A mistake on a dormant campaign domain costs little. The same mistake on the domain that carries company email costs a lot.

A checklist before the first transfer

  • [ ] Every domain is sorted into move, keep, drop or fix first.
  • [ ] Every "fix first" item is resolved.
  • [ ] DNS dependencies are known for every live domain.
  • [ ] Approval contacts are current and shared.
  • [ ] Waves are defined, with critical domains last.
  • [ ] Someone owns the status of each wave.

Common mistakes

Moving everything

The single most expensive mistake.

Leaving "keep" domains out of the review

Domains that stay still need shared access, safe renewals and locks.

Moving before fixing

A transfer does not fix a wrong registrant.

Critical domains first

Teams sometimes start with the main domain "because it matters most". That is the domain least able to absorb a mistake.

Forgetting to drop

Dropping is part of the migration plan, not an afterthought.

Special cases

Domains in sensitive industries

For businesses in sensitive industries, registrars react very differently to complaints. Choosing where each domain sits can decide whether it stays online. Some domains should move to a registrar known to ask for documents before acting. Sometimes Kalin contacts a specific registrar directly to confirm whether it accepts such domains.

Domains inherited from an acquisition

Acquired domains often belong in "fix first": wrong registrants, renewals on cards that will be cancelled, notices to inboxes that will close.

Domains held by agencies

Live domains in an agency account usually move to the company's account early, while the relationship is good. Unused ones are dropped.

Domains close to expiry

Renew first, then decide. Some registrars and extensions make transfers near expiry difficult.

As Kalin puts it: "You don't need to rebuild everything. You need to know what can fail."

The expert behind the sorting

Kalin Karakehayov has worked with domain names every day for 17+ years. He has personally evaluated more than 1.5 million domains, has managed 800K+ with his team, has overseen 10K+ transactions and has worked with all major registrars across 500+ extensions. Some registrars he trusts and uses. Others, he knows, should never be used under any circumstances. That knowledge decides which domains belong in "move" and which in "keep".

How the consultation works

DomainsOptimizer is not a registrar, not software and not a broker. The consultation is remote, confidential and takes about one hour. The only preparation is a full list of domains. No registrar access is needed. For around 200 domains, checks run during the call. For thousands, you send the list in advance. It costs USD 2,500 per hour.

It covers six areas: domain management, renewal and continuity, registrar review, security and risk, migration recommendations and brand domain review. It starts with the reality, walks through the system, finds the weak points against failure patterns from real portfolios and prioritizes the work.

What changes after the review

Quick fixes usually come first: renewal and approval notices move to shared company addresses, payment methods are updated, unneeded logins are removed and transfer locks go on critical domains. Then the four groups become the migration plan. Follow-up sessions run at the same rate, and in some cases Kalin helps with implementation himself.

Crisis help

If a move has already gone wrong and a domain is down, lost or blocked, DomainsOptimizer helps rescue it using every possible way. Registrars react very differently: one suspends immediately, another does not act, a third asks for documents. Sometimes Kalin contacts a specific registrar directly.

A typical situation

Here is a typical situation, not a specific client. A company plans to move all 500 domains to a new registrar. Sorting shows about 180 to drop, 60 to keep with a specialist, 30 to fix first and the rest to move. DNS for two brands moves first. Three waves follow, critical domains last. The company moves fewer than half its domains and none goes offline.

FAQ

How do you decide what to keep?

By registrar quality, extension fit and company control.

Can the order change?

Yes, if a domain is close to expiry or a registrar is urgent to leave.

Is it confidential?

Yes.

What should we prepare?

A full list of domains. No registrar access is needed.