How to Move Your Website to a Kenyan Host Without Downtime

Server racks in a data centre where a Kenyan-hosted website runs

The last time I moved a client’s site, the lights stayed on the whole time. Nobody browsing it saw an error page, and the only person who knew anything had happened was me, refreshing a DNS checker at 11pm.

That is what it actually looks like to move your website to a Kenyan host without downtime. It is not magic, and it is not a five-minute job. It is a short, boring sequence of steps done in the right order.

Almost every disaster I have seen came from skipping one of them. Here is the whole thing, including the part most tutorials leave out: your email.

There are two versions of this job. One is moving the files and the database yourself. The other is paying somebody to do it while you watch. Both need the same five checks, and this post covers both.

Server racks in a data centre where a Kenyan-hosted website runs
Photo: Carl Lender, CC BY 2.0, via Wikimedia Commons

What “without downtime” actually means

Every guide on how to move your website to a Kenyan host promises zero downtime. I have never read one that also explains how DNS caching works, and that is exactly where the promise quietly breaks.

Here is the honest version. There is always a window where some visitors still reach the old server. That is not a failure; it is how the internet looks up names.

What you can genuinely control is whether anybody sees an error page. That is the real target, and it is completely achievable on a normal Kenyan small-business site.

The mistake that causes an outage

An outage during a move almost never comes from DNS. It comes from pointing the domain at a server that is not ready yet.

I have watched that happen twice with small businesses in Nairobi. Both times the site was dark for most of a day, and both times somebody was trying to save an hour by skipping the test step.

The fix is ordering, not talent. Build and test first, switch last, and the old site keeps answering while you work.

What downtime costs a Kenyan business

Downtime sounds abstract until you put a number on the lost hour. A shop loses Saturday orders. A school loses enquiry forms. An NGO loses donations during the campaign it spent a month planning.

For most small businesses here the website is not the main sales channel. It is the place a customer checks before deciding to trust you. An error page at that exact moment costs more than the hour did.

That is why I treat a move as a weekend job rather than an evening one. You want room to stop and fix something without a queue of customers watching.

What the window really looks like

Expect about an hour of your own attention, spread over two days. Expect a few hours where some visitors reach the old server and some reach the new one.

That overlap is fine as long as both servers show a working site. Two working copies of the same site is a safe state; one broken copy is not.

Downtime and your search rankings

Search engines do not punish you for a short outage. They do notice if your site returns errors every time they crawl it for a week, and they can quietly start showing a different page in your place.

A move done in this order never gives them a reason to. A move done in a panic, with the domain pointed at an empty folder for two days, does.

The one thing that genuinely needs careful watching is email, and I will come to that properly later.

Before you move: five checks on your current host

Before you move your website to a Kenyan host, do all five while the old site is still alive. Two of them become impossible once the account is closed, and one of them is the difference between keeping your email and losing it.

Check 1 — control panel access

You need working control panel credentials, and they must be yours. Not the web developer’s, not an old intern’s, not an address that stopped receiving mail in 2023.

Most Kenyan sites were built by somebody who has since moved on to a full-time job. If you cannot log in to the current host, fix that before you shop for a new one.

Ask the host to reset the password to your own email address. If the account is in someone else’s name, that conversation needs to happen first, not on moving day.

Check 2 — export the DNS zone

Write down every record: A, CNAME, MX, TXT, SPF and DKIM. Better still, export the zone file if the panel allows it.

This is the whole ballgame. When you change nameservers you move everything with them, including mail, and the records you did not note down are the ones that vanish. If the domain itself is also changing hands, that is a separate job from transferring your domain to Host Kenya, with its own paperwork.

Check 3 — write down every mailbox

List every address that currently receives mail. Include the ones nobody remembers: info@, accounts@, the address of a former employee that still forwards to the director.

Those forgotten mailboxes are where the complaints come from a week later. A missing mailbox does not bounce loudly; it silently swallows enquiries.

Check 4 — disk usage and database size

Check how much space the site actually uses and how big the database is. That tells you whether the new plan fits and whether the backup will download over your current connection.

A site with years of unoptimised images can easily be several gigabytes. Knowing that now is better than discovering it at midnight.

Ask the host whether file-count limits apply as well as space. A gallery-heavy site can hit those long before it runs out of room.

Check 5 — versions

Note the PHP version, the WordPress version, and any plugin that only works on the old stack. Hosts run different PHP versions, and an old plugin can break on a newer one.

If something is already fragile, deal with it before the move rather than discovering it after.

If the panel asks you to confirm the account owner’s email address, sort that out now. A password reset that goes to an address you cannot read is the same as having no access at all.

Keep these notes in one document as you go. Half an hour of writing saves an evening of guessing later.

External hard drive holding a full website backup before a hosting move
Photo: Coyau, CC BY-SA 3.0, via Wikimedia Commons

Step 1: take a backup you can actually restore

Not “take a backup”. A backup you have never opened is a hope, and hope is not a recovery plan.

Two parts, always

A complete copy means the files and the database. Files alone give you a site with no posts, no pages and no settings.

The files are everything in your site folder, especially the uploads and plugins. The database holds the words, the menus and the users.

If the database export fails because the file is too large, export it table by table. It is slower and duller, but it works on hosts with tight limits.

Doing it without plugins

Use the control panel file manager to compress the site folder into a single archive. Then export the database as a SQL file.

Name both with the date, so that in three weeks you know which one is current. That small habit has saved me more than once.

Doing it with a plugin

A backup plugin will produce one archive, which is easier. Check that the settings include the database, because several default to files only.

Download the archive to your own machine. A backup that exists only on the server you are leaving is not a backup.

The restore test

Open the SQL file in a text editor and look for your post titles. If you can see real rows with real headlines, the dump is good.

If the file is tiny, or the tables are empty, stop and take it again. This is the one step where a second attempt costs nothing and skipping costs everything.

A restore test does not have to be a full rebuild. Opening the database file and comparing the row counts to the live site is usually enough to catch a bad export.

Two copies, two places

Keep one copy on the old host until the move is finished, and one on your own drive or cloud storage.

Then delete the archive from the old host when you are done. A publicly reachable zip of your entire site is a gift to anyone who guesses the filename.

Label the copies plainly, for example site-files-2026-11-10.zip and site-database-2026-11-10.sql. Future you will not remember which is which.

The Kenyan reality of big backups

A site with heavy galleries can be several gigabytes. Do the download over office Wi-Fi rather than a phone hotspot, and start it early.

If the connection drops halfway, a download manager or a fresh attempt beats a corrupted partial file you trust by mistake.

Step 2: build and test on the new host before touching DNS

This is where moving your website to a Kenyan host without downtime is actually earned. The new site goes up while the old one is still answering, and nobody notices anything yet.

Cardboard moving box taped closed, a stand-in for moving a website
Photo: HireAHelper, CC BY 2.0, via Wikimedia Commons

Upload to the right folder

Files go into the document root, usually public_html. Not into a subfolder inside it.

The classic mistake is uploading into public_html/site/ and then wondering why the domain shows a directory listing. Check the path before you upload, not after.

If the upload stalls halfway, start again rather than resuming. Half a site is harder to debug than none.

Create the database and import

Create a database and a user on the new host, then import the SQL file through the database tool in the panel.

Edit the configuration file with the new database name, user and password. Get one character wrong and you get a blank white page instead of a site.

If the site shows a database error instead of loading, that file is the first place to look. Nine times out of ten it is the password or the host name.

See the new site without changing DNS

Add the domain and the new server’s IP address to the hosts file on your own computer. Only your machine sees the new site, which is exactly what you want.

Some hosts give you a temporary URL instead. Either way, you are looking at the future site while the public still sees the old one.

If you are moving WordPress specifically, our WordPress hosting plans cover the setup side. The same test-first order applies, and the official WordPress guide to moving a site is worth reading for how the folders are laid out.

What to test

Test the things that actually break: every form, the cart if there is one, image galleries, the login, and one page buried deep in the menu.

Test the homepage last. The homepage almost always works, which is why people who only check it think the move went fine.

Check that a form actually sends before the switch, not after. A contact form that silently fails is the most common thing people discover a week later.

Clear the old domain out of the database

A site built with a page builder often carries the old absolute address inside widgets and settings. Search the database for the old domain and fix what you find.

If you skip this, you get a site that looks correct until somebody clicks a button and lands back on the old host.

Do not enable caching yet

Leave caching and any CDN switched off on the new host until the switch is done. You want to see the raw site while you are still fixing it.

Caching comes back on afterwards, once you know the site itself is right.

Step 3: lower the TTL, then make the switch

The cutover itself is the shortest part of the job. The preparation is what makes it short.

A day before, lower the TTL

Drop the time-to-live on the relevant records to 300 seconds, a day before you plan to switch.

Long TTLs are what turn a five-minute change into a two-day one. A record set to 86400 stays cached for up to 24 hours, and you cannot recall it.

If you cannot find the TTL setting, ask the current host rather than guessing. Editing the wrong record at this stage is how a domain goes missing for a day.

Nameservers or records, not both

If your domain uses the registrar’s nameservers, you are editing records. If it uses the old host’s nameservers, you are changing the nameserver entries themselves.

Know which one you are doing before you start. Doing both at once is how people create a domain that resolves nowhere.

Do not delete the old records until the new ones have been answering for a day. Deleting first and adding later leaves the domain with nothing to point at.

Point only what you mean to move

The website and the email do not have to live in the same place. You can move the web records and leave the mail records exactly where they are.

That single decision is what keeps email alive, and it is covered properly in the next section.

Screenshot the DNS screen before you change anything. It sounds fussy, and it has rescued me twice.

If you are still choosing a name, start with registering a .co.ke domain before you plan the hosting move.

Network switches and patch panels in a server rack during a DNS cutover
Photo: Dsimic, CC BY-SA 4.0, via Wikimedia Commons

Verify with real commands

Run a lookup on the domain and compare the answer to the IP address the new host gave you. A DNS checker website does the same job if you prefer a screen to a command line.

Check the nameservers too, not just the address. If the nameserver names are still the old ones, nothing has actually changed yet.

The mobile data check

Load the site on mobile data rather than office Wi-Fi. Phone networks usually use a different resolver, so they often show the new server sooner.

If it loads on your phone but not on the office connection, that is caching, not a broken site. Time fixes it.

Keep the old host paid until this finishes

Do not cancel the old account on switch day. Keep it live and paid until the new site has been answering properly for a day or two.

KeNIC’s own guidance for .co.ke puts propagation at roughly 30 minutes. Anything already cached on a long TTL can take considerably longer than that.

Step 4: keep your email alive during the move

This is the section that generates the support tickets, and the one most guides compress into a single sentence.

Changing nameservers moves mail too

Mail records live in the same zone as the website. Switch the nameservers and you have moved email as well, whether you meant to or not.

That is the single most common self-inflicted wound in a hosting move. Somebody moves the site, and three days later discovers that nobody has received an enquiry since Tuesday.

The safe pattern

Leave the mail records pointing at the current mail provider, and move only the web records. The website and the email can live on different providers indefinitely, and plenty of businesses do exactly that.

If you are not confident about which record is which, move the website and leave email completely alone.

In practice this is also cheaper, because you are not paying twice for a mailbox that already exists somewhere else.

If mail has to move as well

Recreate every mailbox on the new host before you switch anything, using the list you wrote down in the checks.

Then import the old mail, and reset passwords, because mailbox passwords do not transfer. Send the new passwords to the right people before the switch, not after.

Keep the old mail account open until the new one both receives and sends, even if that costs a little for a few weeks.

SPF and DKIM are TXT records

Copy them exactly, character for character, quotes included. A missing quote or two strings merged into one turns valid mail into spam.

This is the failure people miss for weeks. Mail does not bounce; it just quietly stops being read.

Ask whoever set up the mail where those records live. If nobody knows, treat it as a mail migration and plan it as its own job.

Test it from outside

Send a message from a Gmail account to a company address, then reply back. Test an address nobody uses much, because that is where the missing mailbox hides.

Ask a colleague on a different network to do the same. Two tests from two networks catch most record problems.

The first 48 hours

Watch for bounce-backs for two days. If the business cannot afford a missed enquiry, forward a copy of everything to a second address while things settle.

For the mailbox side, our email hosting plans cover the setup. The hours are 8am to 6pm, Monday to Saturday, if you need a person to check a record with you.

Step 5: the first 48 hours after the move

Once you have moved your website to a Kenyan host, these checks take about an hour in total. They catch almost everything that a move quietly breaks.

Person checking a newly migrated website on a laptop at a desk
Photo: Shixart1985, CC BY 2.0, via Wikimedia Commons

Confirm the address and the redirect

Visit the http and www versions of the site. One should redirect cleanly to the live address, not serve a second copy or throw a security warning.

If both versions load independently, you have just created duplicate content by accident.

Re-check the certificate

Force the site to load over https and confirm the certificate covers both the bare domain and www. Then click through a few pages looking for security warnings.

Mixed content warnings are common after a move, because old pages often point at images over plain http.

Re-submit the sitemap

Submit the sitemap again and watch the coverage report for a week. A move should not create new missing pages.

If it does, you have missed a URL, and finding it in the report is faster than clicking the menu looking for it. Our post on how web hosting in Kenya boosts SEO and rankings explains why these signals matter more than most people think.

Re-point what lived on the old host

Anything that pointed at the old server needs re-pointing: scheduled tasks, forms that send mail through an external service, a payment gateway’s list of allowed addresses, and any verification records.

Changing your domain records can break a verification token you set up two years ago and forgot about.

Send a real message through the contact form and confirm that it arrived. A form that looks fine can be pointing at an address that no longer exists.

Test speed from Kenya

Measure load time on a Kenyan connection, not from a tool that defaults to Europe or America. Testing from a European data centre tells you nothing about the point of a local host.

If the site feels slower than before, say so early rather than accepting it. That is a support question, not something to live with.

Wait a week, then cancel in writing

Export one final backup the day you cancel. Then cancel in writing and keep the confirmation.

Keep the old account a week after you are happy. It costs a little and it is the cheapest insurance in this whole process. For the destination side, compare shared hosting plans and cloud hosting plans before you commit to a year.

Tell nobody

If the move worked, there is nothing to announce. If you feel you have to warn customers about disruption, that is a signal the move was done badly.

How long it takes to move your website to a Kenyan host

Nobody quotes a realistic timeline, so here is one. Times are for a normal small-business site, not a shop with a custom application.

Stage Realistic time Who does it
Five checks and a full backup 1 to 2 hours You
Building and testing on the new host 1 to 3 hours You or the host
The switch itself 30 to 60 minutes You
Watching propagation A few hours to a day Nobody, mostly
Post-move checks About 1 hour You
Final backup and cancellation 30 minutes You

Spread over two days, that is a weekend. Crammed into one evening, it is a gamble.

What it costs in money

You are buying hosting you needed anyway. Current verified plans are SharedBasic at Ksh 2,000 a year, SharedAdvanced at Ksh 3,500, SharedEnterprise at Ksh 4,000, and CloudStarter from Ksh 449 a month.

Those are the only figures I will quote, because they are the ones on the live site today. Do not budget from a number somebody mentioned in a WhatsApp group last year.

The full breakdown of web hosting cost in Kenya covers what each plan includes and which costs the price list leaves out.

Pick a quiet period for the switch. A Sunday morning in Nairobi is calmer than a Friday afternoon.

Whether migration help is included with a plan is a question for the sales conversation, not for a blog post. Ask directly before you pay, and get the answer in writing.

If your domain is registered somewhere other than the host, a nameserver change can take an extra day to be accepted. Do not plan the move for the morning of a launch.

When to pay somebody instead

Pay for help if you run a shop in the middle of a campaign, if the site has a custom application, or if nobody on your team can follow a control panel screen.

There is nothing wrong with that. A botched move costs more than the help does.

Ask what happens if the site breaks the next morning, and who fixes it. A cheap migration with no follow-up is not cheap.

When not to move at all

If your current host is fine and the site is slow because of too many plugins, moving will not fix it. You will pay for a move and keep the same slow site.

Fix the site first, then decide whether the host is still the problem.

If you are moving more than one site, do them one at a time. Two half-finished migrations in one weekend is how people lose a domain.

Final checklist: move your website to a Kenyan host without downtime

Print this, or keep it open on a second screen. It is the whole post compressed into the order that matters.

Move your website to a Kenyan host in this sequence and the job stays uneventful. Skip the middle of it and you will spend the weekend fixing what you skipped.

Two days before

  1. Confirm you can log in to the current control panel with your own credentials.
  2. Export the DNS zone and write down every MX, TXT, SPF and DKIM record.
  3. List every mailbox, including the ones nobody remembers.
  4. Note disk usage, database size, PHP and WordPress versions.
  5. Take a full backup of files and database, then open the database file and confirm it holds real rows.
  6. Keep a second copy somewhere that is not the old host.

The day of the switch

  1. Drop the TTL on the records you are changing to 300 seconds.
  2. Upload the files to the document root, not a subfolder.
  3. Create the database, import the dump, then fix the configuration file.
  4. Test the new site through the hosts file, including forms, login and one deep page.
  5. Search the database for the old domain and replace what you find.
  6. Point only the web records, and leave mail where it is.
  7. Verify with a lookup, then check the site on mobile data.

The week after

  1. Confirm the http and www versions redirect to a single address.
  2. Force https and confirm the certificate covers both names.
  3. Re-submit the sitemap and watch for new errors.
  4. Re-point scheduled tasks, forms and any old verification records.
  5. Test speed from a Kenyan connection, not from a European data centre.
  6. Take one final backup, then cancel the old account in writing.

That is the whole job. Nothing on the list is difficult, and nothing on it takes more than an hour.

The one step people skip

The step most people cut is the test before the switch. It is also the only step that actually delivers the promise in the title.

Everything else on this page can be fixed afterwards. A domain pointed at a broken site cannot, because customers are watching while you fix it.

If you would rather not do it alone, choose the destination first. Start with shared hosting plans for a normal business site, or WordPress hosting plans if you are moving WordPress.

Then message us with your current host and platform, and we will tell you what the move involves before you pay anything. We answer between 8am and 6pm, Monday to Saturday.