17 June 2026
How we migrate WordPress sites to Cam Cloud without downtime
A plain-English look at our WordPress migration process: what we check, how we stage the site, when DNS changes, and how we avoid the usual migration drama.
By Lewis Cornwell
Moving a WordPress site should not feel like defusing something under a timer. The site is just files, a database, DNS records, forms, plugins and a few quiet assumptions that nobody wrote down. The trick is not magic. It is doing the work in the right order.
At Cam Cloud, WordPress migration is free on every hosting plan. We move the site, test it, then switch traffic only when the new version is ready.
Here is what that actually means.
First, we audit the current site
Before we copy anything, we check the basics:
- WordPress version
- PHP version
- Theme and plugin list
- Storage use
- Database size
- Existing caching
- Contact forms
- WooCommerce or membership features
- DNS records
- SSL state
- Email records, especially SPF, DKIM and DMARC
This catches the common migration problems early. For example, a very old plugin might only run on an old PHP version, or a contact form might depend on SMTP settings hidden inside the current host.
If the current site is unusually fragile, we say that before the move starts.
Then we copy the site to staging
We do not point your domain at Cam Cloud straight away. We copy the WordPress files, database and uploads onto a staging URL first.
That staging copy lets us test the site without disturbing visitors on the live domain. We can check pages, menus, images, forms, logins, admin screens and anything business-critical while the current site continues to run on the old host.
For normal brochure sites, this is usually straightforward. For WooCommerce, booking systems or membership sites, the final database timing matters more because orders and user activity can change while the copy is being tested.
We test the boring journeys
The home page is not enough.
We test the things that actually matter:
- Contact forms submit correctly
- Email notifications arrive
- Login and admin screens work
- Important redirects still resolve
- Media files load
- SSL is valid
- Caching is not breaking dynamic pages
- Search engines can crawl the site
- Key pages return 200 status codes
If the site has WooCommerce, we also check basket and checkout behaviour. If it has a booking system, we check the booking journey. If it has custom post types or ACF fields, we check the templates that use them.
Most migration failures are not dramatic server explosions. They are small missed details. The contact form silently stops emailing. A redirect disappears. A caching rule serves the wrong thing. Those are the things we are trying to catch.
DNS changes only when the new site is ready
Once the staging copy is signed off, we agree a quiet window and switch DNS.
The exact route depends on how the domain is managed. Some sites already use Cloudflare, which makes the move quick. Others need nameservers, A records or CNAMEs updated at the registrar.
We keep the old host in place while DNS settles. That way, if an ISP or browser cache is still sending a visitor to the old server, they still see a working site.
We watch it after launch
The job is not finished the second DNS changes.
After cutover, we check:
- The live domain resolves to Cam Cloud
- SSL is valid on the real domain
- Forms still send
- WordPress admin works
- Error logs are quiet
- Uptime monitoring sees the site
- Cloudflare and caching are behaving
We also keep an eye on the old host for a short period so nothing important is missed during DNS propagation.
What you need to provide
Usually, we need:
- WordPress admin access
- Hosting control panel or SFTP access
- Database access, if not available through the control panel
- Registrar or DNS access
- Any SMTP or transactional email details the site uses
If you do not have all of that, we can usually help work out what is missing. The most important thing is not to cancel the old hosting until the migration is complete and checked.
Which hosts can we migrate from?
We can usually migrate WordPress sites from cPanel hosts, GoDaddy, 123 Reg, SiteGround, WP Engine, Kinsta, Cloudways and most agency hosting setups.
The host matters less than access. If we can get the files, database and DNS records, we can usually move the site cleanly.
The short version
A clean WordPress migration is not about rushing the DNS switch. It is about copying first, testing properly, moving at a sensible time and watching afterwards.
That is why free WordPress migration is part of every Cam Cloud plan. If we are going to host the site, we want it moved properly from day one.
If your current WordPress host is slow, awkward, expensive or just ignored, send us the URL and we will tell you the safest way to move it.
- wordpress
- migration
- hosting