A domain transfer changes the registrar that manages your domain. It does not move your website files, hosting account or mailboxes. If the current nameservers and DNS records stay in place, your website and email can continue working while the transfer is processed.
The risk comes from changing too many things at once. A registrar move, nameserver change and hosting migration may all involve the same domain, but they are separate jobs. Complete one controlled change at a time, starting with a record of the setup that already works.
How to transfer a domain in South Africa without downtime
Before requesting the transfer, confirm who controls the domain, where its DNS is hosted and which records keep the website and email online. Keep the existing nameservers unchanged unless a separate DNS migration has been planned and tested. Then follow the gaining registrar's process for the extension you own.
If Allanux Web is the registrar you want to move to, start with the domain transfer service page. The checks below explain what to prepare before placing the request.
What actually changes during a domain transfer?
These services are connected, but they are not interchangeable:
| Service | What it controls | Does a registrar transfer move it? |
|---|---|---|
| Domain registrar | Renewal, registration details, transfer status and registrar-level controls | Yes. This is the part being changed. |
| DNS and nameservers | Where the domain points for web, email and other services | Not automatically. Confirm the existing nameservers will remain assigned. |
| Website hosting | Website files, databases, applications and server configuration | No. |
| Email hosting | Mailboxes, stored messages, delivery and authentication | No. |
| Domain ownership | The registrant or holder responsible for the domain | Not necessarily. A registrar transfer is not automatically a change of owner. |
This distinction matters when a web developer, former employee or previous agency holds one of the accounts. Moving the registrar will not recover hosting access or transfer mailbox data. Sort out those access problems before the move.
Prepare the domain before you request the transfer
Build a small handover pack while everything is still working. It should contain:
- The domain name, extension, current registrar and renewal date.
- The registrant and administrative contact details, including an email address you can access.
- The current nameservers.
- A copy or screenshots of the complete DNS zone: A, AAAA, CNAME, MX, TXT, CAA and SRV records where present.
- The website host, email provider and any third-party services that rely on DNS.
- Current SPF, DKIM and DMARC records used for email authentication.
- The domain's transfer status, registrar lock status and authorisation code where the extension requires one.
Do not treat a screenshot of the home page as proof that the setup is documented. A website can look fine while an omitted MX or TXT record quietly breaks email delivery, Microsoft 365 verification, Google Workspace, an SSL validation method or another business service.
If the domain is close to expiry, first check the renewal and transfer rules for that extension. The domain name life cycle guide explains why expiry status deserves attention before you start moving providers.
The safest domain transfer order
- Confirm account and contact access. Make sure you can sign in to the current registrar and receive transfer messages sent to the authorised contact.
- Record the working DNS setup. Save the nameservers and every DNS record before changing a lock or submitting a request.
- Check eligibility. A lock, registry status, recent registration or recent transfer can delay some extensions. Ask the current registrar what applies to this specific domain.
- Get the required transfer credential. Many generic extensions use an EPP or authorisation code. A .za transfer may follow a different registry or registrar process, so use the instructions for the actual extension rather than assuming the .com workflow applies.
- Start the request with the gaining registrar. Enter the domain carefully and provide only the information requested for that extension.
- Approve legitimate transfer messages promptly. Check the domain and sender before clicking. Transfer emails are sensitive account actions, not routine marketing messages.
- Leave nameservers and hosting alone. Do not combine the registrar move with an unplanned nameserver, web-hosting or email migration.
- Verify the result. After completion, check the registrar account, registration period, nameservers, website, HTTPS and email in both directions.
That order reduces variables. If something fails, you know which change to investigate instead of untangling three migrations at once.
.co.za transfers are not always the same as .com transfers
An EPP or authorisation code is common for generic top-level domains such as .com, but do not assume every .za transfer uses the same mechanism. The process can depend on the extension, registry status and current registrar.
For example, ZARC publishes a specific voting process for domains still managed through its legacy or default registrar. That procedure uses contact approvals and its own timing rules. It is a special case, not a universal recipe for every .co.za domain. Your gaining registrar should identify the correct process after checking the domain.
The same caution applies to transfer locks and waiting periods. Restrictions can apply to some domains after registration, a previous transfer or certain account changes. Confirm the rule for the actual extension instead of relying on a generic “60-day rule” copied from a different registrar's help page.
Why websites and email go down during a transfer
| Cause | What you may notice | How to prevent it |
|---|---|---|
| Nameservers changed unexpectedly | The website or several services stop resolving | Record the current nameservers and confirm they will remain assigned after transfer. |
| DNS zone copied incompletely | The website works, but email or a subdomain fails | Export or record the whole zone, not only the website's A record. |
| MX or email-authentication records omitted | Mail bounces, lands in spam or fails authentication | Verify MX, SPF, DKIM and DMARC before and after any DNS change. |
| Registrar transfer combined with hosting migration | It becomes unclear whether the fault is at the registrar, DNS or server | Schedule the changes separately and verify one before beginning the next. |
| Transfer messages sent to an inaccessible address | The request stalls or expires | Correct contact access before starting; do not wait for the approval email to discover the problem. |
A registrar transfer is usually uneventful when DNS stays stable. The operational work is proving what “stable” means for your domain before anybody presses the transfer button.
When not to start a domain transfer
Pause the move if any of these are unresolved:
- You cannot access the registrar account or authorised contact email.
- The domain is extremely close to expiry and you have not confirmed the extension's renewal and transfer behaviour.
- The domain is locked or has a status the current registrar has not explained.
- A website, email or nameserver migration is already in progress.
- The domain is involved in an ownership dispute or suspected account compromise.
- You do not know where DNS is hosted or have no copy of the current zone.
Security deserves extra care. Keep transfer credentials out of shared tickets and public chat threads, review account access, and enable the protection options offered by the registrar.
What to check after the transfer completes
Do not stop at the “transfer successful” message. Confirm the operational result:
- The domain appears in the correct new account.
- The registrant details and renewal date are correct.
- The nameservers match the pre-transfer record.
- The main website and important subdomains load over HTTPS.
- Email can be sent to and from an external mailbox.
- MX, SPF, DKIM and DMARC records still return the expected values.
- Auto-renewal, billing contacts and expiry reminders are set deliberately.
- Registrar access is limited to the right people and protected with multi-factor authentication where available.
Run these checks from outside your office network too. Cached DNS can make one device appear healthy while other users are already seeing a problem.
How long does a domain transfer take?
It depends on the extension, the current and gaining registrars, the domain's status and how quickly required approvals are completed. Some requests complete quickly; others take several days. A delay does not mean you should change nameservers to “help” the transfer.
Plan around business risk rather than a best-case estimate. Avoid starting immediately before a product launch, payroll run, campaign or holiday shutdown. Keep the existing hosting and DNS services active until the new registrar confirms completion and you have passed the post-transfer checks.
Transfer fees and renewal effects also vary by extension. Check the current domain pricing and the exact transfer terms before ordering; do not assume that a price or registration extension quoted for one TLD applies to another.
