Paste and parse
Comma, space or tab separated, straight from a spreadsheet.
Submit a whole list at once, each line carrying a domain and its auth code.
Moving dozens or hundreds of domains one at a time is how mistakes happen: one gets missed, the codes end up on the wrong lines, and a refusal arrives with no explanation.
Bulk transfer puts the whole job in one table. Paste the domains with their codes, submit once, and each domain is tracked separately with its own result.
Export the domains from your current registrar and collect each transfer code.
Paste the list, read the pre-check warnings, then submit.
Each domain shows its current stage and what it is waiting on.
Correct the cause - unlock, new code, wait out the 60 days - and resubmit only the failures.
Comma, space or tab separated, straight from a spreadsheet.
Malformed, duplicated or unsupported entries are flagged first.
Waiting, in progress, completed or refused, line by line.
Locked, wrong code, too new, or not confirmed.
Successful transfers extend the term by a year.
There is no need to move everything at once.
Three lines cause most failures
Do not post the list, or a screenshot of it, anywhere public. The whole list is the key to the whole batch.
Match the message to the cause
| Message | Cause | Fix |
|---|---|---|
| Domain is locked | The current registrar still has transfer prohibited set | Turn the lock off there, then retry |
| Invalid transfer code | The code expired or was regenerated | Generate a new code and retry |
| Registered less than 60 days ago | A registry rule that cannot be waived | Wait until the 60 days are up |
| Domain has expired | It is in redemption or pending delete | Renew it at the current registrar first, then transfer |
| Ending not supported | That ending does not use the standard flow | Use the manual route - ask us what is needed |
Keep the risk small
With more than about fifty domains, move them in batches. Start with three to five to prove the process - how unlocking works there, how the codes are issued, whether the confirmation emails actually arrive - then work in groups of twenty or thirty. A problem in the first batch stays a small problem.
Expect your current registrar to limit outbound transfers or to review them manually. If a whole batch is refused for the same reason, fix the common cause rather than retrying each domain.
One list, deduplicated and format-checked.
Status and reason shown against each line.
One place to review and export them.
A year added on each successful transfer.
Resubmit only what did not go through.
A convenient moment to verify the registrant data.
The page states the limit for the current batch. For large numbers, split the work - it makes faults easier to find and avoids tripping your current registrar transfer limits.
Domain,transfer code per line is the reliable one. Tabs and spaces also work, but a code containing a space will be truncated, so commas are safer.
Once the request has gone to the registry we cannot withdraw it, but the confirmation email from your current registrar usually offers a decline option.
Those are the pre-checks: the name is malformed, it appears twice in the batch, the ending does not support a standard transfer, or the domain is already in your account.
A transfer that does not complete is not charged. If a charge was taken and then refused, the amount returns to your account credit and you can resubmit.
Open the page for this service and finish in a few steps. If you would rather ask first, a ticket reaches a person.