You can switch web developers in South Africa without losing your website, your emails or your Google rankings. The trick is order: secure your domain, your logins and a full backup before you give notice, then move.
Most switches that go wrong do not go wrong because anyone was malicious. They go wrong because the domain was registered in the developer’s name years ago, nobody knows the hosting password, and the website goes quiet the week the invoice stops being paid.
I’ll be honest about how I used to get this wrong. When I started building websites at scale, eight to ten years ago, I believed that taking on a new client meant taking everything away from the previous developer: the domain, the hosting, all of it, as quickly as possible. So that is what we did. Contract signed, domain moved, new site launched.
Then the real work started. Pages that had ranked on Google for years disappeared. Links pointing to the old site broke. Established businesses, some of them trading for decades, were suddenly starting online almost like brand new businesses, because the history they had built was gone.
It took me until around COVID to see what I had been missing. Clients rarely leave because of hosting. They leave because they want better: a better website, more enquiries, more sales. And the most valuable thing the old setup holds is its data. Even if the old website did not look great and sales were flat, its rankings, its links and its old campaigns show what worked and what did not. Some data, good or bad, beats starting from zero.
This guide walks you through the switch step by step, in the order that keeps your business online the whole way through.
The short answer: what you must own before you switch
Before you tell your current developer anything, make sure you have these five things in your own name or your own hands:
- Your domain (yourbusiness.co.za), registered to your business with an email address you can open
- Admin access to your website (for most SA sites, a WordPress administrator login)
- Your hosting account, or at least a full backup of your files and database
- Your email setup (Microsoft 365, Google Workspace or the host’s mail), with the admin login
- Your marketing accounts: Google Business Profile, Google Analytics, Search Console, Google Ads and Meta, with you as the owner, not just a user
If you have all five, switching is mostly admin. If you are missing any, sort those out first. The steps below show how.

Step 1: Find out who actually owns your domain
Your domain is the one thing you cannot rebuild. A new developer can make a new website in weeks, but if someone else controls yourbusiness.co.za, they control where your website and email point.
Look it up on the ZA Central Registry WHOIS at registry.net.za. Check two things:
- Registrant name: it should be your business, not your developer or their company
- Registrant email: it should be an address you can open today
That email matters more than most people realise. When you move a .co.za domain, there is no transfer code. The registry sends an approval email to the registrant address, and the transfer only goes through when someone clicks to accept it. If nobody accepts within five days, the transfer fails.
If the registrant details are wrong, ask your current developer or host to update them first. Updating .co.za contact details takes about five days, so start early.
Step 2: Collect every login in one place
Make a simple list (a password manager is better than a spreadsheet) of:
- Domain registrar account
- Hosting control panel (cPanel, Plesk or similar)
- WordPress administrator login, in your own name, not a shared “admin” account
- Email admin (Microsoft 365 or Google Workspace)
- Google Business Profile, Analytics, Search Console, Tag Manager and Ads
- Meta Business Manager, plus any booking, payment or CRM tools connected to the site
For Google and Meta accounts, you want to be the owner, not just a user. An owner can add the new developer and remove the old one. A user cannot.
Step 3: Take a full backup you control
Ask for, or download yourself, a full backup of:
- The website files
- The database (this is where your pages, products, orders and form entries live)
- Your email mailboxes, if email is moving too
Store it somewhere that belongs to you, such as your own Google Drive or OneDrive. Then check the backup opens. A backup nobody has tested is a hope, not a backup.
Step 4: Read your agreement before you give notice
Look for three things:
- Notice period: 30 days is common
- Ownership: who owns the design, the code and the content once paid for
- Hosting terms: whether the site sits on the developer’s own server, and what happens when the account closes
If the website is still on a payment plan, settle or agree on the balance first. It keeps the handover friendly, and friendly handovers are fast handovers.
Step 5: Brief the new developer before the old one leaves
The safest switch overlaps. Your new developer should have the backup, the logins and a plan before your current developer stops.
A good migration plan covers:
- Where the site will be hosted, and in whose name
- Whether the site is being moved as is, or rebuilt
- When the DNS will be switched (ideally a quiet day, not month-end for an online store)
- Who checks forms, payments and email the moment it goes live
Done properly, visitors should notice nothing. Downtime for a simple site can be kept to minutes.
Step 6: Move the domain and switch the DNS
Once the new hosting is ready:
- Your new registrar requests the .co.za transfer
- The registry emails the registrant address
- You click to accept, and the transfer completes
- The DNS is pointed to the new hosting and email
Transferring a .co.za domain does not change its expiry date, and you do not lose any time already paid for.
Step 7: Protect your Google rankings
This is where a switch can quietly cost you enquiries for months. Ask your new developer to:
- Keep the same page addresses (URLs) wherever possible
- Set up 301 redirects for any page that moves or changes name
- Keep your page titles and meta descriptions, or improve them deliberately
- Re-submit the sitemap in Google Search Console after launch
- Check Search Console for errors in the first two weeks
Keep the history, not just the website. Do not delete your old Google Analytics property, Search Console account or old Google Ads and Meta ad accounts when you switch. Make sure you are the owner, and keep them. Past campaigns show which keywords brought enquiries and what each one cost. That is insight a new developer cannot buy, and it is the difference between improving your results and starting over.
If you are rebuilding the site at the same time, it is worth reading what a bad agency really costs you before you choose who does it.
What if your current developer will not cooperate?
It is rarer than people fear. Most developers are small businesses too, and many are simply busy. Start with a polite, written request listing exactly what you need: registrant change, logins and a backup, with a reasonable date.
If that does not work:
- Check what you can reach yourself. If you have the WordPress admin login, you can install a backup plugin and download the full site without anyone’s help.
- Talk to the host or registrar directly. If you can prove the business is yours (CIPC documents, invoices showing you paid for the domain), many will help update the registrant details.
- Know the formal route. For .co.za names, the .za Domain Name Authority (ZADNA) runs an Alternative Dispute Resolution process for domain disputes. It is a last resort, and worth getting legal advice before you use it.
In the worst case, where the domain truly cannot be recovered, a new domain and a properly redirected new site is a setback, not the end. But nine times out of ten, a clear, friendly request does the job.
How we handle it at Innovation by Design
We start from one rule: your business owns everything. When we build for a client, the domain is registered in the client’s name, the email is set up for them, and they get full access to every part of the site, including the technical backend. Our agreements say in writing that all intellectual property belongs to the client’s business.
We do it that way because we have seen too many businesses held back by a login they do not have.
It is also why, when we take over a website today, our first job is not to move it. It is to protect what is already there: the rankings, the links, the analytics history and the old campaigns. Then we improve from that base, instead of from zero.
Your switch checklist
- Domain registered to your business, with a registrant email you can open
- WordPress administrator login in your own name
- Hosting login, or a full tested backup of files and database
- Email admin login, and mailboxes backed up if email is moving
- Owner access to Google Business Profile, Analytics, Search Console, Ads and Meta
- Agreement read: notice period, ownership, hosting terms
- New developer briefed with a written migration plan
- Domain transfer approved and DNS switched
- URLs kept or redirected; sitemap re-submitted in Search Console
Frequently asked questions
How long does it take to switch web developers in South Africa?
For a simple business website, one to three weeks is typical. Most of that time goes to gathering logins and waiting for the domain transfer, which can take up to five days.
Do I need a transfer code to move a .co.za domain?
No. .co.za transfers do not use an authorisation code. The registry emails the registrant address, and the transfer completes once that email is accepted.
Will I lose my Google rankings if I change developers?
Not if the switch is planned. Keep your page addresses the same or redirect them with 301 redirects, keep your titles and descriptions, and re-submit your sitemap in Search Console.
Who owns my website if a developer built it?
It depends on your agreement. Check who the domain is registered to, who holds the hosting account and what the contract says about ownership of the design and content. If it is unclear, ask for it in writing before you switch.
Can I switch developers if my website is still on a payment plan?
Yes, but settle or agree on the balance first. It keeps the handover friendly and avoids delays.
What if my email is on the same hosting as my website?
Back up your mailboxes first, then move email and website together on a planned day, so nothing is lost when the DNS changes.
Not sure where you stand?
Run your site through our free Website Health Check. It checks speed, POPIA basics, Google and WhatsApp in plain language, and gives you a clear picture before you talk to anyone.
If you are thinking of switching and want an honest view of what to fix first, start with a Growth Roadmap, or book a free 20-minute call. Been let down before? Tell us what happened.


