1. Identify the owned domain and read its current registry state.
2. Ask the receiving registrar for the exact destination tag and confirm it can receive the domain.
3. Review registry eligibility and any account verification required for the release. Keep website, mail and DNSSEC continuity in the transfer plan.
4. Submit the required new_tag and an optional explanatory reason, with a durable idempotency key.
5. Store the returned operation ID and monitor the provider outcome.
6. Confirm the receiving registrar has accepted the domain and reconcile the source account's final state.

An example request body is:

{
  "new_tag": "RECEIVING_REGISTRAR_TAG",
  "reason": "Authorised move to the owner's receiving registrar."
}

Replace the placeholder with the verified tag. Do not guess it from the registrar's company name or website address.

No. The API returns a domain operation for processing. Provider acceptance, registry completion and receiving-account visibility can be separate stages. Show a pending result until the supported reconciliation confirms the move.

Do not assume so. Registration sponsorship and DNS delegation are separate. Agree who will continue serving the existing zone and whether the receiving registrar changes any DNS service entitlement. Verify the final delegation and signed chain after completion.

If a release fails, check the destination tag, domain eligibility, account authorisation and provider response. Keep the original operation reference. A new EPP transfer order is not a safe substitute unless the registry's actual process calls for it. For an uncertain response, reconcile the existing release before sending another mutation.

• Understand a .uk registrar move and its IPS tag requirement
• Follow a domain operation through pending, failed and manual-review states
• Submit an inbound domain transfer with the Domain Nexus v2 API
• Keep website and email DNS available during a registrar transfer
• Change domain privacy where the registry and provider support it