How to Move Your Website to a Local Hosting Provider — Perth IT Care
Still putting up with a host that drops your site every couple of months? The fear keeping you where you are is costing more than the migration ever would. Your site is already going down on a schedule — the switch itself isn't the real risk.
The reason migrations feel scary is the mental image of everything happening at once while the live site hangs in some uncertain state and emails vanish. That's not how a well-ordered migration works. When you follow the right sequence, you're testing on the new environment before anyone but you can see it, and your live site keeps running right up until you flip the switch.
Here's how it actually works.
The Four Moving Parts of a Website Migration
A website isn't one thing — it's four:
Files — your theme, plugins, images, and everything in the WordPress (or other CMS) file structure. These transfer via FTP, cPanel's File Manager, or a migration plugin.
Database — the content: pages, posts, products, settings, user accounts. This is exported from the old host and imported to the new one.
Email — if your business email lives alongside your website (e.g. you@yourbusiness.com.au through cPanel), it needs to be set up on the new host and your messages need to be migrated or preserved before you point DNS away.
DNS — the settings that tell the internet where your domain lives. This is the last thing you change, not the first.
Understanding these as separate components means you can handle each one without touching the others. That's where most of the anxiety dissolves.
The Right Order: Don't Touch DNS Until You're Ready
This is where most DIY migrations go wrong. Someone transfers the files, then immediately updates the DNS — and spends the next 48 hours wondering why half their visitors are still seeing the old site while the other half hit a broken new one.
The correct sequence:
- Set up your account on the new host
- Transfer files and database
- Test the new site using a hosts file edit or a temporary URL
- Migrate email accounts and export any existing emails
- Set up email on the new host
- Update DNS
- Confirm everything is live and working
- Cancel the old hosting account
Step 8 is important. Don't cancel the old account until you've confirmed the new environment is fully working and DNS has propagated. Keep the old account active for at least a week after the switch — it's your safety net.
Why Australian-Hosted Servers Matter for Perth Businesses
We host our clients on Australian servers — not because of geography for its own sake, but because of what it means in practice.
When your website is hosted on Australian infrastructure, your data stays subject to Australian law. The Privacy Act 1988 and the Notifiable Data Breaches scheme apply to how your data is handled. When servers sit offshore, those protections get complicated fast. If something goes wrong and a data breach occurs, the question of whose jurisdiction applies — and who's actually responsible — becomes a mess you don't want to deal with.
There's also a latency argument. Australian visitors loading your site from Australian servers get faster response times than they would from a server sitting in Singapore, the US, or Europe. Google factors page speed into rankings, so this isn't just a user experience issue. If you want to go deeper on that, the post on website speed and SEO covers how hosting performance affects your rankings directly.
For businesses that hold client data — whether you're in legal, healthcare, finance, or really any professional services — keeping that data on Australian infrastructure isn't just sensible. It's increasingly expected. The overseas data storage risks post goes into more detail on the compliance side.
What to Check Before You Migrate
Before touching anything, get a clear picture of what you're moving:
Confirm where your domain is registered. Your domain registrar and your hosting provider are often two different companies. You're moving hosting — not the domain. The domain stays where it is; you'll just update its DNS records to point to the new host.
List your email accounts. Log into your current cPanel and write down every email address associated with your domain. Don't assume you know them all — it's common to find old addresses that are still receiving mail.
Check your site's PHP version requirements. If your WordPress site relies on plugins that need a specific PHP version, confirm the new host supports it. Most modern Australian hosting environments run current PHP versions, but it's worth verifying.
Back up everything before you start. Export a full cPanel backup if you can, or at minimum a WordPress backup using a reliable plugin. A solid backup before migration means a clean restore point if anything goes sideways. The post on why single backups fail is worth a read before you rely on just one copy.
Migrating Email Without Losing Messages
This is the part most guides skip, and it's the part that bites people hardest.
If your email is hosted in cPanel alongside your website, migrating is not just about setting up the new mailboxes — it's about getting your existing emails across before the old host goes dark.
Options:
- Use an email client like Outlook or Thunderbird to download all mail via IMAP before the switch, then re-upload to the new server after DNS propagates
- Use a tool like imapsync if you're comfortable with the command line
- Ask your new hosting provider if they offer assisted email migration
One thing worth considering: if your business email is still running through cPanel rather than a dedicated mail platform, a hosting migration is a good time to evaluate whether that's the right setup long-term. The post on why cPanel email isn't ideal for business use explains the limitations. Microsoft 365 email is a common step up, and if that's on your radar, the M365 email migration guide covers moving from cPanel to Exchange Online without losing your mind.
DNS Propagation: What It Means and How Long It Takes
When you update your DNS records to point to the new host, those changes don't take effect instantly everywhere. Propagation — the process of that change spreading across DNS servers globally — typically takes between 15 minutes and 48 hours, depending on your old TTL settings and your ISP's cache.
To reduce the wait, lower your DNS TTL to 300 seconds (5 minutes) at least 24 hours before you plan to switch. When you then make the change, it propagates much faster.
During propagation, some visitors will hit the old server and some will hit the new one. That's fine as long as both environments are serving the same content — which is why you complete the file and database migration before touching DNS.
Useful tools for checking propagation status: whatsmydns.net lets you see how your DNS is resolving from different locations around Australia and globally.
Common Mistakes That Cause Migrations to Go Wrong
Cancelling the old host too early. Keep it active until you've confirmed everything works on the new host and DNS has fully propagated.
Forgetting to update hardcoded URLs. WordPress sites sometimes have the old domain or server path hardcoded in the database. A search-and-replace in the database (or using a plugin like Better Search Replace) fixes this.
Not testing before flipping DNS. Always browse the new site using a hosts file edit or temporary URL before making it live. If you're not sure how to do this, it's worth getting help rather than guessing.
Assuming the migration plugin handles everything. Most migration plugins do a good job with files and database, but they won't move your email, and they don't always handle DNS or serialised data cleanly.
For WordPress sites specifically, keeping your WordPress installation up to date after migration matters too — a migration is a good reset point to make sure you're running current versions of everything.
When to Get Help
If your site generates revenue — bookings, enquiries, e-commerce — a botched migration has a real cost. Getting it done properly by someone who's done it before isn't extravagant, it's sensible.
We handle website migrations for Perth businesses: files, database, email, DNS, and confirmation that everything's working before we consider it done. Same time zone as you, so if something comes up during the cutover, you're not waiting for an offshore support team to start their day.
If you're ready to stop putting up with an underperforming host, get in touch and we'll work out what the migration looks like for your specific setup.
