This guide outlines the essential steps to prepare a domain for transfer between registrars. It focuses on checking lock settings, validating owner contact information, and retrieving the necessary authentication code to ensure a smooth migration process.

Assessing Domain Eligibility Before Initiating Transfer

As a hypothetical illustration, picture an author preparing a small portfolio of names for a possible move between two registrars. The working folder holds a plain spreadsheet, a copy of the registration record from the current registrar, and a short written list of questions for whoever manages the account. Nothing is filed yet; the point of the exercise is to decide which names are even eligible for a transfer request.

The first sheet in the folder is a candidate register with three candidate labels the author invented for the exercise: "harborlight ledger," "quaynote index," and "tidepath archive." None refer to a real registration. The author records each one with four columns: lock state, authorization-code availability, registrant contact last verified, and admin contact last verified. Two fictional rows show how the sheet works. For "harborlight ledger," the lock column reads transfer-locked, the authorization-code column reads not yet requested, the registrant contact reads verified last month, and the admin contact reads unverified. For "quaynote index," the lock reads client-transfer-prohibited, the code reads unavailable until unlock, and both contact columns read verified. The second row is the easier case; the first shows why contact verification has to happen before anything else.

A second sheet is a short eligibility worksheet with a header block and repeated field lines: domain label, current registrar, registry lock status, auth-code holder, registrant email verified, admin email verified, and a final column for eligible yes or no. Below the header sit the same two invented records. The author marks "harborlight ledger" as not eligible with the reason "admin contact unverified," and "quaynote index" as not eligible yet with the reason "lock must be released first," keeping the status column honest rather than optimistic.

For the selection decision, the author makes one example trade-off: the three names stay grouped in one folder, but only those whose registrant and admin contacts are both verified go forward to the code-request step. Names with an unresolved contact stay in a holding tab, with the missing item written in plain words beside them. The reason is simple bookkeeping—an unverified contact is a question to settle, not a reason to send a request, and separating the two groups keeps the next action visible.

These mock entries exist only to show how the author would categorize names; they are not a record of any real transfer, registration history, or outcome.

Verifying Unlock Status and Removing Transfer Locks

The cited official guide lists a dedicated Domain Transfer Lock page in its domain management documentation. Its stated purpose is to enable or disable the transfer lock on your domains so that unauthorized outbound transfers are prevented. Use that documented entry to check a name's lock setting rather than relying on a general assumption about lock state.1

The same guide's Domain Transfer Out page describes initiating an outbound transfer and obtaining the transfer authorization code. Unlock status and the authorization code sit on separate documentation pages, so treat the lock check and the code request as distinct steps before any transfer request is filed.1

For the mock portfolio, take the sheet that already records each candidate and add two short columns beside the existing entries: one for the lock wording shown in the current registrar's record, and one for the action you plan to take before any request goes out. The three sample names stay as they are; you are only deciding, per name, whether the record suggests the name is held in a way that blocks a move and whether a separate lock you control needs attention. This is preparation, so write it as a plan rather than a completed check.

When you read the record, separate two things you may see described as a lock. One kind is a setting on the account that you can usually change yourself; the other is a status that may sit outside your account and require a different step. For "harborlight ledger," you might write "account-level lock – plan to switch off before requesting" in the first column and "confirm with account manager" in the second. For "quaynote index," the note might read "no account lock found; check whether any registry-side hold appears" — a question to ask, not a conclusion. Keep these as your own readings of the document in front of you, since the wording varies and you are not yet confirming anything with the registrar.

You can then choose which names to carry forward. One reasonable approach is to sort the sheet so that names with a clear, self-controlled lock sit together and names with unclear status sit below them, so the second group becomes your question list rather than your request list. You might also note beside each unlocked name the date you expect to revisit it, purely so the folder reflects a sequence. Nothing needs to be sent; the value here is a folder where every candidate has a stated lock reading and a next action you chose.

Confirming Owner Contact Details and Email Validity

The transfer code and all key notices are sent to the domain owner's email address, so that address must be confirmed as correct and able to send and receive mail. The basic information page of the domain list is where this confirmation takes place, per the Alibaba Cloud transfer-out guide.2

If the address needs correcting, the guide points to its procedure for modifying domain owner information. It adds an important condition: when submitting that change, the option stating that transfer out is prohibited for 60 days after a successful domain information modification must be unchecked. Otherwise, the name cannot be transferred out for 60 days after the change succeeds.2

The same email requirement resurfaces later in the flow. The page instructs users to confirm the owner email and complete phone verification before the code is issued, offering change email and change phone links when either is wrong.2

You can add a contact-verification column to the same spreadsheet that already records your candidate names, rather than starting a separate document. Take one mock entry from your working folder—say the invented name "quaynote index"—and write the registrant name, the admin contact, and the email address exactly as they appear on your copy of the registration record. Then write beside each one the source you checked it against and the date. For quaynote index, the mock line might read: registrant name as shown, admin email as shown, checked against the registrar record on a date you note, with the note "matches."

The next action is to decide, name by name, whether the owner contact details are current enough to rely on before you request a transfer. You can compare the email on the record with an inbox you actually control; if the address looks stale, you might write a short note in the same row saying what you plan to update and when. This is a prepared step, not a completed check, so keep the wording in the sheet tentative. For a second mock name, such as "harborlight ledger," the same row could carry a different note—perhaps "email domain retired, plan to update before transfer"—which gives you a visible reason to hold that name back while quaynote index moves forward.

You might also test your own reading of the record: rewrite each email in plain words, then compare your phrasing with the original entry. If you cannot tell whether an address belongs to you, mark the row uncertain rather than guessing. Sorting the sheet by that mark lets you choose which names to prepare first; the others can wait until the contact question is settled.

Preparing Internal Records for Migration Tracking

Use NamesLink ’s Domain Transfer Lock and Domain Transfer Out pages to check which names in the portfolio are not locked against outbound transfer, then open Domain Transfer Out for any unlocked name to obtain the transfer authorization code for the receiving registrar. Keep a short written note of each name’s status and authorization code so you can later compare it with the copy of the registration record from the current registrar and your list of questions for the account manager.1

Retrieving Authorization Codes from Current Registrar

To retrieve the transfer password, Alibaba Cloud instructs signing in to the domain console's domain list, finding the domain to transfer, and clicking Manage in the operation column. From the left navigation bar, select Domain Transfer Out, then confirm the registrant mailbox and complete mobile number verification. If the email or phone number is incorrect, you can click edit email or edit mobile to change it. After verification passes, click Next, and the system sends an email containing the transfer password to the domain's registrant mailbox. The transfer code is the sole credential authorizing transfer, valid for 15 days, so it should be used promptly after retrieval. Domain transfer out does not support batch operations; each domain's management page must be entered separately to request the transfer code. For .hk domains, online transfer out is not supported, and the separate .hk domain transfer-out process applies.2

For the auth-code step, you can add one more field to the same candidate sheet: “auth code source and date.” Fill it in only when you have actually located the code in the current registrar's account area, and leave the cell blank for names where you have not. A hypothetical entry might read: harborlight ledger — code seen in account panel, copied to password manager, date noted. That is a preparation note, not proof that a transfer request was filed.

You might also record where you looked, not just the result. For example: account security page, then transfer-out section, then email inbox for a message from the registrar. If the code appears in an email, note the sender and the date so you can tell it apart from later messages. If you cannot find the code, write the exact menu path you tried and the wording on the page; that wording is useful when you ask your account contact for help.

Consider deciding, name by name, whether to request the code now or wait. One reasonable approach is to group names where the code is already stored and the owner email is current, and keep the rest in a “ask first” group. You can annotate each row with a short reason: “code stored,” “cannot locate transfer section,” “email possibly outdated.” These notes are your own working labels, not statements about registry status.

If you later move one name forward, compare the code's date with the date you plan to submit the request. Codes can expire, so an older entry may need to be retrieved again. Note that in the sheet rather than assuming the stored value is still valid. The next step is to choose one name from the ready group and confirm, in your own words, that its code and contact details are both current before you act on it.

Submitting Transfer Requests at Receiving Registrar

At the receiving registrar, open its official website and locate the domain transfer or “Transfer Domain” entry point. Following that registrar's instructions, enter the domain name you want to move and the transfer code obtained from the previous step. The source states this step usually involves paying a one-year domain renewal fee.2

After submitting the request and completing payment, check your email for a confirmation message from the receiving registrar. The source notes the current registrar receives the transfer request once it is submitted at the new registrar, and that ordinary transfers are expected to take five to seven working days while no further action is required.2

At the receiving registrar, you can begin with the transfer request form itself and treat it as a second record to compare against your folder, not as a fresh start. Before filling anything, note which fields the form asks you to re-enter and which it carries over from the auth code or the current registration record. For the harborlight ledger entry, for example, you might type the name, paste the stored code, and then pause on the contact section to check whether the receiving side shows the same registrant email your sheet lists.

One practical move is to keep a request log beside the candidate sheet, with four columns you fill in as you go: name, date submitted, code used and where it came from, and the wording of any confirmation the receiving side displays. Fill the first row with harborlight ledger only after you have actually sent that request; leave quaynote index blank if you decide to hold it. That way the log stays a record of what you did rather than a plan that looks finished.

You might also preview the form once without submitting, purely to see which questions it raises about your entries. If the form asks for a contact address that differs from your sheet, you can mark that discrepancy and resolve it before returning. For the archived example, the same four columns work: record when the older request went in and which code source it used, so a later reading of the folder shows how the two submissions differed.

Consider deciding, name by name, the order in which you will send requests. A reasonable approach is to submit the one whose code is freshest and whose contact details match first, then return to the others once you see what confirmation wording the receiving side gives you.

Frequently asked questions

If I have a sheet that records each candidate, what two short columns can I add beside the existing entries for the mock portfolio?

For the mock portfolio, take the sheet that already records each candidate and add two short columns beside the existing entries: one for the lock wording shown in the current registrar's record, and one for the action you plan to take before any request goes out. The three sample names stay as they are; you are only deciding, per name, whether the record suggests the name is held in a way that blocks a move and whether a separate lock you control needs attention.

How can I group candidate names so that unclear-status names become my question list rather than my request list?

You can then choose which names to carry forward. One reasonable approach is to sort the sheet so that names with a clear, self-controlled lock sit together and names with unclear status sit below them, so the second group becomes your question list rather than your request list.

Where should I fill in the auth code source and date on my candidate sheet, and when should I leave it blank?

For the auth-code step, you can add one more field to the same candidate sheet: “auth code source and date.” Fill it in only when you have actually located the code in the current registrar's account area, and leave the cell blank for names where you have not.