Transfer a domain between registrars: eligibility and service preservation

Define the move across six separate roles

Identify the TLD registry, current and gaining sponsoring registrars, registered holder, authoritative DNS operator, website host and mail provider. Write what should stay unchanged and what needs a separate decision. One company may fill several roles; that does not make their contracts, authority and acceptance evidence interchangeable.

The published ICANN gTLD policy assigns transfer approval authority to the Registered Name Holder. Changing registrant rights or material contact information is a distinct process. Before making a proposed contact correction, establish its consequences with the responsible registrar; do not treat an edit as a harmless prerequisite.[1]

Begin with a blank transfer handoff

For each row record dated source/locator ____, evidence owner ____, state/blocker ____ and next review ____. Use authorized private references; never put an authorization code, password or unnecessary identity document in the shared sheet.

A critical authority or eligibility unknown means HOLD. A favorable calendar gap or apparently healthy website cannot compensate for it. Preserve unresolved evidence openly rather than counting green service rows as permission to transfer.

Date the policy and classify restrictions

The ICANN policy displayed on October 14 is the February 21, 2024 update, with mandatory implementation by August 21, 2025. Its header still displays deferral of enforcement of the gaining registrar’s Form of Authorization (FOA) requirement. The June 7, 2026 Board adoption of 47 review recommendations directs implementation; the implementation page lists Transfer Policy Review in queue. Adoption does not make proposed replacement procedures effective. Recheck the applicable version before action.[1][2][3]

Under the published gTLD policy, initial-registration and recent-transfer circumstances in I.A.3.7 permit denial, while enumerated legal/dispute and change-of-registrant circumstances in I.A.3.8 require denial. II.C addresses a material-change lock, prior opt-out and qualified removal provisions including footnote 7. An ordinary clientTransferProhibited unlock is not evidence that every restriction disappeared. Do not apply one universal 60-day wait or promise every lock can be removed.[1]

Provider-specific authorization, notifications and completion evidence remain necessary. The policy’s conditional five-calendar-day assistance and registry-response provisions address particular obligations, not total delivery time. A request or payment receipt is not confirmation that sponsorship changed. This guide does not supply a universal email-form or token script.[1]

Document service preservation separately

For each dependency identify current owner/source ____, keep or separately migrate ____, acceptance evidence/operator ____ and hold or reversal decision ____. Six rows: the provider contract question is as important as the intended technical settings.

Cloudflare’s April 24, 2026 guide requires its own authoritative DNS for its registrar service. SIDN’s .nl page instead illustrates registry-specific contracts and coordination with a DNSSEC-capable new registrar. These narrow examples can reopen a preservation plan; they are not universal requirements. A qualified operator must choose the relevant DNS/DS sequence. Do not copy a provider’s DNSSEC-disabling recipe into every transfer.[4][5]

Fictional Paper Lantern Workshop: old dates do not clear the gate

Seven handoff fields and six preservation rows remain distinct from this six-row fictional summary. The 37/29-day differences are calendar cushion, not a transfer forecast, lock duration or SLA; the two-day review is not a policy deadline. If B required its own DNS, the unchanged-DNS assumption would fail and require a separately reviewed DNS plan. No provider is claimed to offer the fictional acceptance.

Separate policy entitlement from provider acceptance

The published gTLD policy does not make expiration alone a blanket denial ground; actual restrictions and unpaid-period conditions matter. Cloudflare separately documents renewal of an expired name at the current registrar as a prerequisite. Therefore a near-expiry or changed-status case needs its own status/renewal decision and exact provider evidence before transfer planning continues. No guaranteed recovery, free move or unconditional extra year follows.[1][4]

Require separate completion and service evidence

Hand over the qualified eligibility decision, private authority references, dated provider instructions, seven-field sheet and six-row preservation record. Later authorized evidence must distinguish accepted request, completed sponsorship and each operator’s service acceptance. In Paper Lantern the result remains HOLD. This guide does not execute the move or promise uninterrupted DNS, TLS, mail or event links.