Your domain is often the part of your online setup that appears everywhere: on your website, email addresses, business cards, invoices and marketing material. That makes a domain transfer feel more serious than a simple change of provider.
The good news is that a registrar transfer and a website migration are separate things. Transferring a .co.za domain changes which registrar manages the domain. It does not, by itself, copy your website files, move your mailboxes or change where your website is hosted.
The main risk comes from changing several services at the same time without knowing which part controls what. A careful transfer starts by identifying your current registrar, checking the registrant details and understanding which DNS records are currently in use.
If you are only changing the registrar, there is usually no reason to move your website or email at the same time. A separate hosting migration can be planned before or after the domain transfer.
What a .co.za transfer actually changes
A registrar is the organisation through which your domain is registered and managed. When you transfer the domain, the registrar responsible for the domain changes.
For .co.za and other South African second-level domains, the transfer process is handled through the ZA Central Registry (ZACR). ZARC's published .co.za policies describe a transfer as a change from the releasing registrar to the gaining registrar, initiated at the request of the registrant.
The domain can continue using its existing website and email services. If the DNS configuration remains appropriate, changing registrars does not inherently require you to move those services. South African registrar guidance also distinguishes a domain-only transfer from a simultaneous website or email migration.
- Registrar: manages the domain registration.
- DNS: tells services where the domain should point.
- Hosting: provides the website or email service.
Before you start
Before requesting a transfer, make a note of how the domain is currently configured. This is especially important if you did not originally set up the website or email yourself.
Check which company is the current registrar and confirm that the domain is active. Also identify where the DNS is managed and where the website and email are hosted.
ZACR's published policies state that a registrant can transfer a domain to another registrar, subject to the applicable transfer rules. A locked domain cannot normally be transferred without a manual transaction through the registry administrator.
It is also sensible to avoid making unrelated DNS changes while the transfer is being prepared. If you need to change the website host, email provider and DNS at the same time, the number of moving parts becomes much larger.
Check your registrant email
The registrant email address is particularly important for a .co.za transfer. The transfer approval request is sent to the registrant associated with the domain, and that person must be able to approve the request.
Before starting, confirm that the email address listed for the registrant is current and accessible. If it is outdated, contact the current registrar about correcting the details before requesting the transfer.
This is not something to leave until the transfer request has already been submitted. If you cannot access the relevant mailbox, the transfer approval may not reach the person who needs to accept it.
South African registrar guidance states that .co.za and other listed .za domains do not use authorisation or EPP codes for transfers. The transfer uses the ZACR approval process instead.
Understand the transfer process
Once you have chosen the new registrar, the gaining registrar initiates the transfer request. For .co.za domains, a transfer request generates a voting or approval request for the registrant.
The registrant then needs to approve the request using the process provided by the registry. The current registrar and new registrar may provide status updates while the transfer is being processed.
The approval window matters. For example, xneelo's current guidance states that the registrant has five days to accept a .co.za transfer request before it expires. The exact presentation of the request can depend on the registrar's workflow, so follow the instructions included in the registry email.
If the request is declined or expires, the domain is not simply transferred anyway. The issue needs to be resolved and the transfer submitted again if necessary.
Prepare your website and email
If you are transferring only the domain registration, your website and email can normally remain where they are. The key is to avoid accidentally replacing or removing the DNS configuration that connects the domain to those services.
Before the transfer, record the important DNS information. This might include the records used for your website, mail service and email authentication. Keeping a copy gives you something to compare against if a DNS problem appears later.
If you are also moving the website or email, treat that as a separate migration project. The website should be prepared on the new host, and mailboxes should be created and tested on the new service before you change the records that direct traffic or email.
Do not assume that transferring the domain automatically transfers your website files or mailbox contents. A domain transfer changes domain registration; service migrations require their own preparation.
What happens to DNS?
DNS is one of the most important parts of keeping the services connected to your domain. It determines where systems look for services such as your website and email.
A registrar transfer does not inherently mean that your website or email must change servers. However, you should know where the DNS zone is hosted and which nameservers the domain is using.
If the DNS zone is managed by a separate provider, that arrangement can remain in place. If the new registrar also provides DNS and you decide to move the DNS management there, the existing records need to be recreated accurately before changing nameservers.
Before changing nameservers, make a record of the existing DNS configuration. Website records, MX records and authentication records can all matter. Missing an important record can affect website access or email.
DNS changes can also take time to appear consistently because DNS information is cached by recursive resolvers. There is therefore no useful promise that every user will see a DNS change at exactly the same moment.
Transfer the domain
Once the domain details and registrant email have been checked, the transfer can be initiated with the new registrar.
- Confirm the current registrar. Make sure you know who currently manages the domain.
- Check the registrant details. Confirm that the registrant email is correct and accessible.
- Choose the gaining registrar. Use a registrar accredited for the relevant .ZA namespace.
- Submit the transfer request. Follow the new registrar's process for starting the .co.za transfer.
- Watch for the registry approval email. Check the registrant mailbox and spam or junk folder.
- Approve the transfer. Follow the approval link or instructions supplied by the registry.
- Wait for completion. Check the transfer status with the new registrar rather than repeatedly submitting new requests.
The exact screens and wording will differ between registrars, but the underlying process is governed by the South African registry's transfer procedures.
After the transfer
Once the transfer is complete, log in to the new registrar and check the domain details. Confirm that the domain is active, the registration information is correct and the nameservers are what you expect.
Test the services that matter to your business. Visit the website, send and receive a test email and check any other important domain-dependent services.
If the website and email remained with their existing providers, they should not require a migration merely because the registrar changed. If something is not working, compare the current DNS and nameserver configuration with the information you recorded before the transfer.
It is also worth checking the domain's renewal date and keeping your new registrar's contact details somewhere accessible. The registrar will normally be responsible for renewal notifications and domain management after the transfer.
When you are also changing hosting
A domain transfer and a hosting migration can be combined, but doing both at once makes the process harder to troubleshoot. If there is a problem, you have to determine whether it comes from the registrar, DNS, the website migration or the new email service.
If possible, prepare the new hosting environment before changing the live DNS. For a website, that can mean copying the site, importing the database and testing the new environment. For email, it can mean creating the mailboxes and planning the mailbox migration before changing the relevant mail records.
If the domain transfer itself is the only change, keep the existing hosting and email configuration intact. This creates a much clearer boundary around the work being performed.
Our guide toDomain, Web Hosting and Email Hosting Comparedexplains how these services fit together. If you are also moving a WordPress website, seeMoving WordPress Without Downtimefor the separate website migration considerations.
The simple version
A .co.za domain transfer changes the registrar managing the domain. It does not automatically move the website or email.
Before starting, check the current registrar, make sure the registrant email is accessible and understand where the DNS is managed. For .co.za domains, the transfer uses a registry approval process rather than the EPP authorisation-code process used by many other domain extensions.
If you are only changing registrars, keep your website and email configuration unchanged. If you are also changing hosting, prepare those services separately and test them before making the relevant DNS changes.
The goal is not to promise that every transfer will be completely disruption-free. The safer approach is to understand which service is changing, preserve the existing configuration where possible and test the important services after the transfer.
If you are planning to move a South African domain to PalmHost, you canview PalmHost Domain Transfer for more information about the service.
