How to Transfer a Domain Without Downtime

Transferring a domain name to a new registrar should be straightforward. Yet a poorly planned transfer can lead to website downtime, interrupted email delivery, broken subdomains or unexpected renewal problems.

The problem is often not the transfer itself, but the way it is coordinated with DNS changes, hosting migrations and email configuration.

The good news is that a registrar transfer does not normally require you to change where your website or email is hosted. If your existing DNS service remains active and your nameservers stay unchanged, you can often transfer the registration without interrupting those services.

This guide explains how to prepare, transfer and verify a domain while minimising the risk of downtime.

1. Understand the Difference Between a Domain Transfer and a Hosting Migration

Before starting, establish exactly what you want to move.

A domain transfer changes the registrar responsible for managing your domain registration. A hosting migration moves your website, application or email services to another provider. A DNS change alters where the domain directs traffic.

These are separate operations.

If you are only changing registrars, you may not need to change your hosting or DNS configuration at all.

If you are also moving hosting, plan the hosting migration separately and confirm that the new environment is ready before switching traffic.

2. Audit Your Existing DNS Records

Before initiating a transfer, document the DNS configuration that currently supports your website, email and other services.

DNS records are often overlooked because they may have been configured years earlier and are not necessarily stored with the company hosting your website.

Your audit should include:

Not every domain uses every record type. Record what actually exists in your DNS zone, including records for subdomains.

How to Perform the DNS Audit

1. Sign in to the provider currently managing your DNS zone.

2. Export the DNS zone if the provider supports it.

3. If an export is unavailable, copy the records into a spreadsheet or document.

4. Record the current nameservers, TTL values and any custom records.

5. Identify which provider manages DNS separately from the registrar.

6. Confirm that you have access to the DNS provider and that the service will remain active throughout the transfer.

A screenshot can help as a reference, but an export or written record of the actual DNS values is more useful when you need to recreate the zone.

Important: A registrar transfer does not automatically guarantee that your DNS zone will be copied to the new registrar. If your current registrar also hosts your DNS, confirm how that service will be handled before initiating the transfer.

3. Prepare the Domain at Your Current Registrar

Once you have documented the existing configuration, prepare the domain for transfer.

Check the Domain's Eligibility

Some domains cannot be transferred immediately after registration or a previous transfer. For many generic top-level domains, ICANN rules generally impose a 60-day transfer restriction after initial registration and, in applicable cases, after a registrar transfer. Certain ownership-change situations can also trigger restrictions.

However, these rules do not apply identically to every domain extension. Country-code domains such as .co.ke may have different eligibility requirements.

Check the current status and rules for your specific extension before proceeding.

Unlock the Domain

Many domains have a registrar transfer lock to prevent unauthorised transfers. Where required, remove the lock through the current registrar's control panel.

Do not confuse a transfer lock with domain expiry protection or account security. Unlocking a domain does not mean you should leave it unprotected after the transfer.

Verify the Administrative Contact Email

Transfer approvals or verification messages may be sent to the registered contact email or handled through the registrar's approved process.

Make sure the relevant mailbox is accessible and monitored. If the contact email is outdated, follow the registrar's procedure to update it before starting the transfer.

Obtain the EPP or Authorisation Code

Many domain extensions require an authorisation code, commonly called an EPP code or transfer code.

Request it from your current registrar and keep it secure. The receiving registrar will typically ask for it during the transfer process.

Not all extensions use the same authorisation process, so follow the requirements for your particular domain.

4. Prepare the Destination Before Initiating the Transfer

If you are moving only the registration, confirm that the new registrar supports the domain extension and that you understand its renewal and management options.

If you are also moving hosting or DNS, prepare those services before switching anything.

If You Are Moving Hosting

1. Create the new hosting account.

2. Transfer the website files and database, where applicable.

3. Configure the application, environment variables, SSL certificate and any required background jobs.

4. Test the website using the hosting provider's recommended temporary URL, preview method or local hosts-file override.

5. Confirm that forms, login functions, checkout flows and other critical features work.

6. Verify that the new environment can handle the expected traffic.

For dynamic websites, plan how to handle database changes made while both environments are running. A simple file copy may not capture orders, form submissions or account updates created after the initial migration.

If You Are Moving DNS

If your goal is to move DNS management to another provider, recreate the required DNS zone at the destination and validate the records before changing nameservers.

Pay particular attention to MX records, SPF, DKIM, DMARC and domain-verification records. Missing these can disrupt email or other services even when the website appears to work.

Do not shut down the old DNS service until you have confirmed that the new authoritative DNS setup is working and the transition is complete.

5. Should You Lower Your DNS TTL Before the Transfer?

TTL, or time to live, determines how long DNS responses may be cached before they are refreshed.

A shorter TTL can be useful when you plan to change DNS records or nameservers. For example, reducing relevant TTL values to 300 seconds—five minutes—at least a day before a planned DNS switch may help some resolvers pick up the changes sooner.

However, lowering the TTL is generally unnecessary for a registrar-only transfer if your nameservers and DNS records are not changing.

Keep these points in mind:

• Lower the TTL before a planned DNS change, not simply because the registrar is changing.

• Existing cached responses may remain in circulation until their previous TTL expires.

• Some resolvers and systems may not behave exactly as expected.

• Restore an appropriate TTL after the migration is stable if you changed it temporarily.

A low TTL does not correct missing DNS records or guarantee zero downtime.

6. Initiate the Domain Transfer

After completing the preparation, you can start the transfer.

1. Sign in to the destination registrar's account.

2. Select the option to transfer an existing domain.

3. Enter the domain name and the required authorisation code, if applicable.

4. Review the transfer price, renewal terms and any additional requirements.

5. Submit the transfer request.

6. Complete any verification or approval steps required by the current registrar, receiving registrar or registry.

7. Monitor the transfer status until it is complete.

Transfer times vary by domain extension, registry, registrar and approval process. Some transfers may complete relatively quickly, while others can take several days or longer.

Do not assume a transfer will finish within a fixed period. Check the status with the receiving registrar and respond promptly to any requests for action.

Keep the Existing Services Running

During the transfer, keep your current website hosting, mail service and DNS provider active.

Where the nameservers remain unchanged, the registrar transfer alone should not require you to redirect website traffic or move email to another server.

This is one of the simplest ways to reduce the risk of disruption: avoid changing several infrastructure components at the same time unless there is a clear reason to do so.

7. Verify Everything After the Transfer

Once the receiving registrar confirms completion, review the domain and its associated services.

Confirm the Registration Details

Check that the domain appears in the new registrar account, the registration status is correct and the renewal date reflects the completed transaction.

Verify the domain's contact details and ensure that your team can manage the registration.

Check the Nameservers and DNS Zone

Confirm that the nameservers still point to the intended DNS provider.

If you deliberately moved DNS management, verify the new authoritative nameservers and inspect the records against your original audit.

A registrar transfer does not necessarily change nameservers, but some providers may offer additional configuration steps. Review the actual settings rather than assuming they remain correct.

Test the Website and Email

Open the website and test important functions, including forms, checkout, login and other business-critical features.

For email, test both sending and receiving. Check the relevant MX records and verify that SPF, DKIM and DMARC are still configured as intended.

Also test important subdomains and third-party integrations that depend on the domain.

Re-enable the Transfer Lock

After the transfer is complete, enable the receiving registrar's transfer lock where supported and appropriate.

Review account security settings, including multi-factor authentication if available, and ensure that renewal reminders go to a monitored mailbox.

Confirm Auto-Renewal and Billing

Review the new registrar's renewal settings, saved payment method and renewal price.

Do not assume that the previous registrar's auto-renewal configuration or payment details have carried over. Set up the new account's renewal arrangements and confirm the domain's actual expiry date.

8. Common Domain Transfer Mistakes to Avoid

Frequently Asked Questions

Will Transferring My Domain Cause Downtime?

A registrar transfer does not inherently require website or email downtime. If the existing DNS service remains active and the nameservers do not change, the transfer can often complete without interrupting services.

Downtime can occur if the DNS provider is changed incorrectly, required records are missing, hosting is moved prematurely or another configuration change is made during the process.

Does a Domain Transfer Change My DNS Records?

Not necessarily. A registrar transfer and DNS management are separate. If the nameservers stay the same and the existing DNS provider continues to serve the zone, the DNS records can remain unchanged.

However, if the old registrar also hosts DNS and the service is discontinued or migrated, you must confirm that the records are available and working at the destination.

What Is an EPP Code?

An EPP code, also called an authorisation code or transfer code, is a credential used to authorise many domain transfers. Obtain it through your current registrar's approved process and provide it to the receiving registrar when required.

Can I Transfer a Domain Registered Less Than 60 Days Ago?

For many generic top-level domains, an applicable 60-day restriction may prevent an immediate transfer after initial registration. Other restrictions may apply after a previous transfer or certain ownership changes.

Rules differ by extension, so check the eligibility requirements for your particular domain.

How Long Does a Domain Transfer Take?

There is no single completion time for every domain. The duration depends on the extension, registry procedures, registrar processing and any required approvals. Check the receiving registrar's guidance and monitor the transfer status.

Should I Change Hosting and Transfer the Domain at the Same Time?

You can, but separating the operations is often easier to troubleshoot. Transfer the registration while keeping existing DNS and hosting unchanged, then migrate hosting or DNS in a separately planned step.

If you must coordinate the changes, prepare and test the destination environment first and document a rollback plan.

Do I Need to Renew My Domain After Transferring It?

The transfer may include a renewal extension for certain domain extensions, but this is not universal. Review the destination registrar's terms and confirm the actual expiry date after completion. Configure auto-renewal and verify the payment method rather than assuming the domain has been renewed for a particular period.

Conclusion

A successful domain transfer is primarily about preparation and sequencing.

Document your DNS records, confirm eligibility, obtain the required authorisation code and make sure the destination is ready before starting. Keep existing hosting, email and DNS services running until the transfer is complete and all critical services have been verified.

If you are also moving hosting or DNS, treat those as separate changes with their own testing and rollback plans.

Explore the SteboHost domain services to review your domain management options. Before beginning a transfer, confirm the supported extension, transfer requirements, pricing and renewal terms for your specific domain.