Moving hosts is the step most people delay for a year after they have already decided to leave. That is understandable: a website that is quietly earning enquiries feels too fragile to touch, and every host’s migration page glosses over the part that actually goes wrong. The transfer of files is easy. Loss of email, a missing database and a DNS record nobody wrote down are what turn a two-hour job into a two-day outage.
This guide is the process we would follow ourselves when moving a Kenyan site between cPanel hosts. It is written for the person who is not a server administrator — a business owner, a freelancer, or the one person in the office who “does the website”. Every step can be done in order, and nothing in it requires the old provider’s cooperation.
What actually breaks during a migration
Four things cause almost every failed move we hear about.
Email. A website can be down for an hour without anyone noticing. Email cannot. The moment mail records point at the new server, every mailbox has to exist there with the same address, the same password and enough history to look normal. This is the single most common casualty.
Databases. Copying files without the database gives you a WordPress site that loads and then shows a connection error, or worse, opens with the installer asking to create a new admin account.
DNS records that only existed in one place. SPF, DKIM, DMARC, verification TXT records for Google Search Console, a subdomain someone set up for a booking tool. None of these live in your files. If nobody exported the zone, they vanish at cutover.
Propagation timing. A record with a 24-hour TTL is still cached by some resolvers a day after you change it. Plan for that instead of being surprised by it.
Before you start: a thirty-minute checklist
- Download a full backup from cPanel — files and databases — not just a WordPress plugin export.
- Inventory your mailboxes. Addresses, aliases, forwarders, and the ones that only receive.
- Export the DNS zone or screenshot the record list from the old provider.
- Note the renewal date and refund terms on the old plan. Cancelling mid-term rarely refunds anything, so the cheapest move is often to finish the term and let it lapse.
- Check what your current plan includes that you may be using without realising: extra domains, subdomains, SSL, cron jobs, scheduled tasks.
Step 1 — Take a real backup
Do this from the old host’s cPanel file manager and phpMyAdmin, or through the host’s backup tool if it produces a downloadable archive. A plugin-level export of just `wp-content` is not a backup: it leaves out the database, which holds every post, page, product and user.
Keep the archive until a month after the old account is closed. It costs nothing but disk space and it is the only way back if something surfaces late.
Step 2 — Set up the new account and copy the site
Order the new hosting first, and copy the site to it while the old server is still serving the live traffic. At no point should visitors be directed at a half-populated account.
On the new host:
- Create the account and add the domain, but do not change nameservers yet.
- Upload the files into the correct document root — usually `public_html` — and import the database through phpMyAdmin.
- Update the site URL and database credentials in `wp-config.php` and, for WordPress, in the `wp_options` table.
- Install a fresh SSL certificate on the new account.
If you are moving to HostCloud, send your cPanel login and the domain to support and the migration is carried out for you; the copy happens on our servers, not yours.
Step 3 — Test before anyone can see it
Your DNS still points at the old host, so the new copy is invisible to visitors. Test it without waiting for propagation in one of two ways:
- Hosts file override. Add a line to your computer’s hosts file pointing the domain at the new server’s IP. Only your machine sees the new site; everyone else still gets the old one.
- Preview URL. Many panels generate a temporary URL for the account, such as a server hostname path, which serves the site before DNS moves.
Walk through the site as a visitor: homepage, a deep page, a form submission, a login, an image-heavy page. Then log into WordPress and confirm the dashboard, plugins and media library all behave.
Step 4 — Move email before DNS
Recreate every mailbox on the new server with the same address and password, then migrate the messages. cPanel’s own mail migration tools handle this between cPanel accounts; if the old host is not cPanel, use IMAP sync, which copies mail folder by folder without touching the live service.
Do not change the MX record yet. Email should keep flowing to the old server until every mailbox exists and has been tested on the new one.
Step 5 — Cut DNS over
Lower the TTL on your A and MX records to 300 seconds at least 24 hours before the switch. Then change, in this order:
| Record | Points to | Why it matters |
|---|---|---|
| A / CNAME | new server IP | Serves the website |
| MX | new mail host | Delivers email |
| SPF, DKIM, DMARC | copied or regenerated | Without them, mail lands in spam |
| TXT verifications | copied | Search Console and other tools stay verified |
Keep the old records written down. If something misbehaves, restoring the previous A record returns the site to the old server within minutes — which is only true because you lowered the TTL first.
Step 6 — Watch for a week, then cancel
Leave the old account active for at least seven days. Check three things daily: the site loads, mail arrives and sends, and no client reports a missing message. Only after that should you cancel — and cancel deliberately, in writing, with confirmation. An account left to expire on its own can be renewed automatically or, worse, suspended with your old mail on it.
How long the whole thing takes
A typical small business site — a few pages, a WordPress install, two or three mailboxes — is two to three hours of actual work spread over two days. The waiting is DNS. A large shop with thousands of products and a busy mailbox takes longer, mostly on the mail sync.
The part that is genuinely outside your control is propagation. With a 300-second TTL on the day of the switch, most visitors reach the new server within ten minutes and stragglers within a few hours. That is why the TTL step comes first, not last.
What this costs
There is no separate migration fee at HostCloud: moving a cPanel account is part of the support we provide. What you pay is the new plan, billed annually — shared hosting from Ksh 1,999 per year with a free .co.ke domain in the first year, or WordPress hosting if you want the stack managed for you. The old provider keeps whatever is left on the current term, which is why the renewal date on your checklist matters.
If you are still deciding whether to move at all, the arithmetic is in our price comparison, and each provider has its own write-up:
- Truehost alternative — the plan that costs Ksh 4,000 in year two.
- HostPinnacle alternative — what 16% VAT does to the advertised rate.
- HostAfrica alternative — the Ksh 210 offer that renews at double.
- Safaricom hosting alternative — where a 2 GB plan runs out of room.
- Free .co.ke domain with hosting — what the first-year domain offer really covers.
Frequently asked questions
Will my site go down while DNS propagates? No, if you copy the site before changing records. Visitors on the old DNS keep reaching the old server, visitors on the new DNS reach the new one. Both are complete copies of the same site, so nobody sees a broken page.
Do I need to move my domain too? No. A domain and the hosting it points at are separate. You can leave the registration where it is and only change nameservers, or transfer the registration for tidier renewals — the .co.ke renewal price is usually the deciding number.
Can I keep my email addresses? Yes, provided you recreate the mailboxes before the MX record changes. The address is yours; the server behind it is what moves.
What if I am not on cPanel already? The process is the same, but a panel-to-panel migration tool may not apply. Files, database and mail move by hand or by IMAP sync, which takes longer and is worth paying someone to do.
Ready to move? Open a ticket with your cPanel details and we will copy the account, test it, and tell you when it is safe to switch DNS.
One Response
best web hosting company in kenya