Most people put off moving hosts for the same reason they put off moving house: the dread isn't the new place, it's the boxes. The half-day where nothing works and you're not sure where anything is. WordPress migrations have earned that reputation honestly, because plenty of them are done badly — in a panic, all at once, with the live site held hostage the whole time.
It doesn't have to feel like that. A WordPress site is just a few well-understood pieces, and if you move them in the right order, the scary part — the moment your domain starts pointing somewhere new — happens last, after you've already confirmed the new site works. Here's how a weekend move actually goes.
What actually moves
Strip a WordPress site down and there are really only four things to bring across. Naming them takes the mystery out of the whole job.
- Files. Your themes, plugins, and uploads — the
wp-contentfolder is the bulk of it. This is everything you've installed or uploaded over the life of the site. - The database. Every post, page, comment, setting, and user lives here. The files are the building; the database is everything that happens inside it.
- Mailboxes. If you run email on your domain, those inboxes and their existing messages need a home too. This is the piece people forget until a customer email bounces.
- DNS. Not a thing you move so much as a switch you flip — the record that tells the world where your domain now lives. We save it for the very end.
That's the entire job. Everything below is just doing those four in a sensible sequence.
The safe order of operations
The golden rule of a calm migration is that nothing about your live site changes until the new one is proven. You build the new site quietly, off to the side, on an address only you know about. Your visitors keep hitting the old site the whole time, none the wiser.
- Build on the instant subdomain first. Every new CloudPerch site gets a free
your-site.cloudperch.ioaddress the moment it exists, with SSL already in place. That's your staging ground. You copy the files and database onto it and you have a complete, working clone of your site living at a temporary URL — with your real domain untouched. - Bring the files and database across. This is the heavy lifting, and it's the part our team can do for you (more on that in a moment). The clone comes up at the subdomain looking exactly like your live site.
- Sort out mailboxes. If your email is moving too, set up the inboxes on the new domain so they're ready and waiting. Email and web traffic are steered by different DNS records, so you can prepare email without touching the website cut-over at all.
- Verify everything on the subdomain. Click around. Log in. Submit a form. Check a product page, a contact page, the checkout if you have one. This is the step that earns the calm — by the time you change DNS, there are no surprises left.
- Cut over DNS last. Only once you're satisfied do you point the domain at CloudPerch.
The whole trick is sequencing. Do the work while the old site carries the load, verify in private, and make the public switch a thirty-second formality instead of a leap of faith.
The DNS cut-over, demystified
This is the step people fear, and it's the gentlest one. Pointing your domain at CloudPerch means updating one or two records so that requests for your domain resolve to your new site. When your domain is registered with us, we handle those records automatically — DNS runs on Cloudflare under the hood, so changes take effect quickly.
There's a brief window called propagation, where the rest of the internet catches up to the new address. Some visitors see the new site immediately; a few may briefly still land on the old one as their network's cached copy expires. Because both sites are identical at that point, nobody notices a thing. If you want the longer story on records and propagation, our plain-words guide to DNS walks through it without the jargon.
Why the old site stays live
Here's the part that turns a migration from nerve-wracking into routine: your old site keeps serving traffic until the new one is verified. Nothing gets switched off on a hope. You build the clone, you check it over, and only then does the domain change hands. If something looked wrong on the subdomain, you'd fix it there — with zero impact on the live site your customers are still using.
It's the same instinct behind keeping good backups: never put yourself in a position where the only copy is the one you're actively changing.
Do it yourself, or let us carry the boxes
You can absolutely run a migration yourself — the migrate a WordPress site guide has the full step-by-step, from exporting the database to copying wp-content to flipping DNS.
But you don't have to. Free guided migration is part of what you're paying for. Our team brings the files and database across, stands the site up on the subdomain, and helps you verify it before the cut-over. If you're on a deadline, the priority migration add-on is $29 one-time and means we start within one business day rather than slotting you into the normal queue.
| Path | Cost | Best when |
|---|---|---|
| Do it yourself | Free | You're comfortable with WordPress internals and want full control |
| Guided migration | Included | You'd rather hand off the boxes and just verify the result |
| Priority migration | $29 one-time | You need it moved now, not next week |
Either way, the principle holds: old site stays up, new site gets proven first, DNS goes last.
A migration earns its weekend slot mostly because you do the careful part — the verifying — at your own pace, with nothing on fire. When you're ready to start, see the plans to pick your perch, then follow migrate a WordPress site or just tell us you're moving in and we'll carry the boxes for you.