Moving a business domain away from a former website supplier should leave the business with clear control and dependable renewal arrangements. It should also preserve the website and email services that use the name. Those outcomes require a coordinated handover, because transferring domain management and changing hosting are different pieces of work.
Before requesting a transfer, establish what is currently registered, who is authorised to act and which services depend on the existing setup. This guide explains how to prepare the handover, ask the right questions and verify the result without relying on an outdated set of instructions for every domain extension.
Define the change you actually need
Write down the intended outcome. You may want the domain in a business-controlled account while keeping the website and email where they are. You may also be changing supplier for those services, but that should be an explicit part of the plan. Avoid allowing the phrase “transfer everything” to hide several separate decisions.
Identify the current registrar, the supplier that manages the account, the DNS provider, the website host and the email provider. One company may perform several roles, or the arrangement may involve different companies. The handover needs the actual responsibilities rather than assumptions based on whose name appears on an invoice.
Choose a business owner for the change and a technical coordinator for the service checks. If an incoming supplier is assisting, agree what they are authorised to manage. Keep responsibility for renewal and account access visible within the business, even when technical tasks are delegated.
Confirm the domain and authority to act
Record the exact domain, including its extension, and check the registration information available through the registrar or relevant registry route. Ask the current supplier to confirm the account arrangement and the registered details through the appropriate process. A remembered renewal email is a useful lead, but it is not the complete handover record.
Check who is authorised to request the change. If the information is unclear or disputed, resolve that with the registrar and the relevant business decision-maker before attempting a transfer. Do not assume that access to a supplier's website control panel answers every question about the domain registration.
Keep supporting correspondence organised. Record the people involved, the agreed scope and the requests made. Avoid putting passwords or transfer codes into a widely shared project document. The business needs a clear account of the process without unnecessarily exposing the means to control the domain.
Use the current process for the domain extension
Transfer procedures differ, so ask the incoming registrar which process applies to your exact domain and what is required from the current provider. Confirm eligibility, relevant locks, verification steps and any renewal effect before setting the transfer date.
A transfer may require an authorisation code and can be restricted in some circumstances under the applicable registry or registrar rules. Ask the registrar how those rules affect your domain, particularly if registration or contact details have recently changed. Do not assume a process described for one extension applies to every other extension. Our domain ownership and transfers guide provides the related checks.
For .UK domains, check the current registrar instructions and confirm the process in operation when you transfer. Registry processes can change, including the use of transfer authorisation codes. Do not follow an old instruction to change a tag without checking the requirements for your extension and intended transfer date. Our registrar transfer planning guide provides the related checks.
Ask what happens to DNS during the transfer
Get a written explanation from the incoming provider about nameservers and DNS. Will they remain as they are, or does the provider's transfer workflow change them? What happens to existing records? Do not infer the answer from the fact that the request is described as a registrar transfer.
Have the technical coordinator record the current DNS arrangements and the services they support. Include the website, email and relevant verification or connected-service records. Agree where the approved record is kept and who can compare it with the result after the change.
If DNS management is moving, prepare that as a separate, reviewed task. The technical owner should explain how records will be reproduced, what needs testing and how unexpected results will be handled. The business should understand which changes are intended and which services should continue using their existing providers.
Protect renewal and contact arrangements
Check the current renewal date and the incoming provider's renewal terms. Ask whether the transfer affects the registration period, charges or billing responsibility for this particular domain. Avoid treating a promotional transfer price as the complete cost of maintaining the name.
Prepare the business contact and billing arrangements in the destination account. Use people and addresses the business can continue to access, with appropriate account security and a backup responsibility. Confirm how renewal notices and operational messages will reach the relevant owner.
Consider the handover date alongside upcoming renewal work. If the domain is close to expiry or has an unresolved account issue, ask the registrar to explain the appropriate sequence. Keep the agreed advice and actions in the handover record instead of guessing how a particular status will affect the transfer.
Give the former supplier a precise handover request
State the domain, intended destination and authorised business contact. Explain which services are moving and which should stay where they are. Request the information or action the incoming registrar has confirmed is needed. A specific request is easier to fulfil than a general instruction to “release the website”.
Agree how any required transfer code will be supplied to the authorised recipient. Use the provider's supported secure process and limit access to the people carrying out the change. The code should not become an incidental attachment in a broad conversation about design or content.
Keep the communication professional and factual. If the supplier cannot complete a step, ask for the exact reason and the next supported route. A process problem may require information from the registrar rather than repeated requests to the same person.
Verify control and service continuity after the change
Confirm that the domain appears in the intended destination account and that the authorised business owner can manage the agreed functions. Check the registration details, renewal date, billing arrangement and operational contact route. Record any remaining task rather than calling the handover complete because one confirmation email arrived.
Have the technical coordinator compare the DNS result with the approved plan. Then test the public website and relevant email tasks. Follow an important customer journey, submit an agreed controlled enquiry and confirm that staff receive it. Check the services that were meant to remain with their existing providers.
Verify permissions and responsibilities in the destination account through the supported management process. The business should know who has access, who approves changes and who handles routine renewals. A successful transfer should improve clarity rather than simply move dependence from one unnamed individual to another.
Handle incomplete transfers through the appropriate support route
If the process stalls, record the domain status, the request date, the provider's stated reason and the steps already completed. Ask the incoming and current registrars to clarify the next action. Avoid making unrelated DNS or account changes while the transfer question remains unresolved.
Where there is a dispute about authority or registration details, use the relevant provider or registry support process and obtain appropriate advice for the circumstances. Keep the evidence factual. The operational checklist should not be treated as a substitute for resolving a disputed ownership or contractual issue.
Giraffe Digital's digital strategy services provide a starting point for reviewing how domains, hosting and customer journeys connect. A well-planned domain handover leaves the business with verified control, understood renewal arrangements and tested continuity for the services customers use.
Frequently asked questions
How should we define the change you actually need?
Write down the intended outcome. You may want the domain in a business-controlled account while keeping the website and email where they are. You may also be changing supplier for those services, but that should be an explicit part of the plan. Avoid allowing the phrase "transfer everything" to hide several separate decisions. Identify the current registrar, the supplier that manages the account, the DNS provider, the website host and the email provider. One company may perform several roles, or the arrangement may involve different companies. The handover needs the actual responsibilities rather than assumptions based on whose name appears on an invoice. Choose a business owner for the change and a technical coordinator for the service checks.
How should we use the current process for the domain extension?
Transfer procedures differ, so ask the incoming registrar which process applies to your exact domain and what is required from the current provider. Confirm eligibility, relevant locks, verification steps and any renewal effect before setting the transfer date. A transfer may require an authorisation code and can be restricted in some circumstances under the applicable registry or registrar rules. Ask the registrar how those rules affect your domain, particularly if registration or contact details have recently changed. Do not assume a process described for one extension applies to every other extension. Our domain ownership and transfers guide provides the related checks. For.UK domains, check the current registrar instructions and confirm the process in operation when you transfer.
How should we protect renewal and contact arrangements?
Check the current renewal date and the incoming provider's renewal terms. Ask whether the transfer affects the registration period, charges or billing responsibility for this particular domain. Avoid treating a promotional transfer price as the complete cost of maintaining the name. Prepare the business contact and billing arrangements in the destination account. Use people and addresses the business can continue to access, with appropriate account security and a backup responsibility. Confirm how renewal notices and operational messages will reach the relevant owner. Consider the handover date alongside upcoming renewal work. If the domain is close to expiry or has an unresolved account issue, ask the registrar to explain the appropriate sequence. Keep the agreed advice and actions in the handover record instead of guessing how a particular status will affect the transfer.
How should we give the former supplier a precise handover request?
State the domain, intended destination and authorised business contact. Explain which services are moving and which should stay where they are. Request the information or action the incoming registrar has confirmed is needed. A specific request is easier to fulfil than a general instruction to "release the website". Agree how any required transfer code will be supplied to the authorised recipient. Use the provider's supported secure process and limit access to the people carrying out the change. The code should not become an incidental attachment in a broad conversation about design or content. Keep the communication professional and factual. If the supplier cannot complete a step, ask for the exact reason and the next supported route.
How should we handle incomplete transfers through the appropriate support route?
If the process stalls, record the domain status, the request date, the provider's stated reason and the steps already completed. Ask the incoming and current registrars to clarify the next action. Avoid making unrelated DNS or account changes while the transfer question remains unresolved. Where there is a dispute about authority or registration details, use the relevant provider or registry support process and obtain appropriate advice for the circumstances. Keep the evidence factual. The operational checklist should not be treated as a substitute for resolving a disputed ownership or contractual issue. Giraffe Digital's digital strategy services provide a starting point for reviewing how domains, hosting and customer journeys connect. A well-planned domain handover leaves the business with verified control, understood renewal arrangements and tested continuity for the services customers use.


