Transfer operational control of a company domain when an employee leaves

1. List the domain-registration, DNS, hosting, email and billing accounts the person administers.
2. Identify personal credentials, shared credentials, API keys, scheduled jobs and recovery factors connected to those accounts.
3. Confirm the business's authorised replacement and the actual registered-holder details.
4. Transfer operational records, renewal dates, zone exports and pending support cases to the approved company location.
5. Check that the replacement can use the legitimate account and recovery process.

Revoke the departing person's individual sessions, invitations and permissions through the relevant service. Where they knew a shared secret, rotate it and update each approved consumer. For Domain Nexus reseller credentials, coordinate the connector and scheduled environment before verifying the new credential with a read-only request.

Update recovery email, phone and multifactor arrangements under the provider's supported process. If a registrant field also changes, check its transfer-policy consequences before submitting the update. Do not assume that renaming an account user automatically changes the registration record.

Use the provider's account-recovery process with the organisation's authorisation and registration evidence. Explain which account and domain are affected and provide a reachable approved contact. Do not ask support to disclose the former employee's password or bypass verification because the request is urgent.

Check for expiry and active service incidents while recovery is assessed. Preserve existing DNS where possible; an unnecessary emergency migration can create an additional outage.

Verify that the replacement receives relevant notices, can inspect the next renewal and can manage the intended service within their permissions. Review recent registration, DNS and API activity for unexplained changes. Confirm that automated renewals and integrations still work after rotations, and record which old credentials were revoked.

Repeat the same process when an external agency contract ends. The aim is a documented change of authorised access, with working services and a clear owner for the next renewal.

• Register a business domain under the right accountable owner
• Prepare a domain renewal calendar that survives staff and payment changes
• Rotate Domain Nexus API credentials across web and scheduled integrations
• Fix missing DNS controls, read-only zones and limit messages

• ICANN SSAC: Protecting domain registration accounts
• ICANN: Registration contact information questions