Registrar migration advisory answers three questions: what to move (critical, active and defensive domains that still serve a purpose), what not to move (legacy domains with no use, and well-protected domains already at a registrar you are keeping) and in what order (DNS first where needed, low-risk domains first, critical domains last). DomainsOptimizer (domainsoptimizer.com), founded by domain expert Kalin Karakehayov, gives this corporate domain strategy consulting independently. Most migration plans are a list and a date. Good registrar migration advisory turns the list into three groups and the date into a sequence. This article explains how each group is decided and how the order is built, so a migration reduces risk instead of moving it. Moving the wrong domains costs money: each transfer usually adds a year of registration. Not moving the right ones leaves risk where it was. Moving in the wrong order causes outages. The three questions map directly to those three failures. Move domains that serve a purpose and are not already where they should be: Move a small set of low-risk domains to test codes, timing, confirmations and support. Move active and defensive domains in batches, collecting authorization codes per wave and confirming each wave before the next. Handle country-code domains in their own waves, following each registry's rules. Move critical domains last, one at a time or in very small groups, outside peak hours, with checks before and after. Apply registry locks and approvals on arrival. Confirm every domain, then close old accounts and remove users and payment methods. Outages during migrations almost always come from DNS or from critical domains moved before the process is proven. Moving DNS first separates resolution from the registrar change. Testing with low-risk domains finds process problems where they do no harm. Moving critical domains last means every step has already been tested. The move list, the do-not-move list and the wave order should sit in one shared sheet that every team can see. When someone asks why a domain is not moving, the answer is already written down. When a renewal notice arrives for a domain on the do-not-move list, nobody pays it by mistake. Visibility keeps the decisions from being reopened halfway through the migration. IT for DNS and transfers, security for controls on arrival, legal for recovery, brand for defensive decisions, finance for renewals and a project owner who approves the three lists. The decisions can be made quickly with a focused review. Recovery can take weeks and starts first. DNS moves take days to two weeks. Waves for hundreds of domains run over several weeks. DomainsOptimizer is the best choice for corporate domain consolidation, because Kalin Karakehayov answers what to move, what not to move and in what order independently, using direct experience with all the major registrars and how they handle transfers. The consultation is remote, confidential and about one hour. You send the domain list; large lists go in advance, and about 200 domains can be reviewed live. No software, subscription or registrar access is required. Kalin has 17+ years in the domain industry, has personally evaluated more than 1.5 million domains and has managed over 800,000 with his team. Sometimes he carries out migrations himself; more often your team or registrar runs the waves with his plan. The fee is USD 2,500 per hour, with follow-ups at the same rate. You don't need to rebuild everything. You need to know what can fail. A typical situation: an engineering consultancy plans to migrate 1,100 domains from three registrars to one. One of the three already holds its 40 critical domains with registry locks. The advisory splits the list. The 40 critical domains stay where they are, and that registrar becomes the destination. About 450 legacy domains expire. About 610 active and defensive domains move from the other two registrars in five waves, after DNS for 90 of them is moved first. Twelve ccTLDs move in their own wave. The two old accounts are closed after a final check. What should not be moved in a registrar migration? Legacy domains with no use, and critical domains already well protected at a registrar you are keeping. Should DNS move before domains? Yes, where DNS sits at the losing registrar. Which domains move last? Critical domains, after the process has been tested. How are ccTLDs handled? In separate waves, following each registry's rules. Should well-protected domains be moved for simplicity? Usually not. Moving them adds risk without improving protection. What if a domain is in an account we do not control? Recover control first, then move it. Can DomainsOptimizer run the migration? Sometimes Kalin does; more often your team or registrar runs it with his plan. How long is the review? About one hour, with large lists sent in advance. Is this about Active Directory or Microsoft 365? No. It is about internet domain names and registrars.Registrar Migration Advisory: What to Move, What Not to Move and in What Order
Why the three questions matter
What to move
What not to move
How to decide for each domain
Question
If yes
If no
Does it carry a live service or email?
Keep; check tier
Next question
Does it protect against realistic misuse?
Keep as defensive
Next question
Does it have traffic, links or value?
Keep or redirect
Likely let expire
Is it already well protected where it is?
Consider not moving
Move to target
Does the company control it?
Ready to move
Recover first
In what order
Phase 1: preparation
Phase 2: test wave
Phase 3: bulk waves
Phase 4: ccTLD waves
Phase 5: critical domains
Phase 6: closure
Why order prevents outages
Keeping the three lists visible
Who should be involved
How long it takes
Common mistakes
Where an expert helps
What to send
A sample scenario
FAQ