Moving a WordPress site from one host to another involves far more than copying files across — database connection details, file paths, DNS records, and sometimes PHP or MySQL version differences all have to be reconciled, and getting any one of them wrong is a common way for a migration to result in a broken site or downtime that didn’t need to happen.
Host-to-host migration - single site
A full host-to-host migration, tested before cutover and verified after.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Access to both the current and new hosting accounts
- Your domain registrar access, or the ability to update DNS records when the time comes
- Confirmation of your preferred cutover window, ideally during lower-traffic hours
This or something else?
| You want your site moved from one host to another entirely | This fix covers it |
| You’re moving from HTTP to HTTPS specifically, not changing hosts | HTTP to HTTPS full migration |
| You’re moving from a subdomain to your root domain, not changing hosts | Subdomain to root domain move |
| You’re extracting one site from a multisite network, not migrating hosts | Multisite to single site extraction |
What we do
- Prepare the new hosting environment to match required PHP, MySQL, and server settings
- Transfer files and database completely and accurately
- Update configuration for the new environment’s specific details
- Test the site thoroughly on the new host before any DNS change
- Update DNS records to point to the new host at the agreed cutover time
- Confirm the live site is fully functional on the new host after cutover, and monitor briefly for issues
What is included
- A complete, tested migration to your new host
- DNS cutover managed at your agreed time
- Post-cutover verification and brief monitoring
- The pre-migration state preserved on the original host until you confirm success
Not included
- Purchasing or setting up the new hosting account itself, unless already arranged
- Resolving pre-existing site issues unrelated to the migration itself
- Ongoing management of either hosting account after migration
- Domain name changes, as distinct from a hosting move
Questions about this fix
Will my site experience downtime during this migration?
We test thoroughly on the new host before any DNS change, and DNS changes themselves typically propagate within a short window — meaningful downtime is uncommon with careful planning, though brief propagation delay is normal.
What happens to my old hosting account after the migration?
We recommend keeping it active and unchanged for a period after cutover, as a safety net, until you're fully confident the new host is working correctly.
Will my email still work during and after this migration?
Email is often hosted separately from your website, but we confirm this specifically for your setup, since a hosting migration handled carelessly can sometimes disrupt email if it's tied to the same account.
What if my new host has different PHP or MySQL versions than my old one?
We check compatibility beforehand and address anything that needs adjusting, since a version mismatch is one of the more common causes of a migration breaking something unexpectedly.
How long does a typical migration like this take?
It varies with site size and complexity, though we plan the cutover for a specific, agreed window to minimise any visible disruption regardless of how long the underlying preparation takes.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.