Website Migration Checklist for Australian SMEs | 4iT

A website migration moves your site to a new host, platform, or domain, and the whole risk sits in one place: doing it without losing traffic, rankings, or uptime. The essentials are a full backup first, a complete URL map with 301 redirects for anything that changes, DNS and email checked, and a staged cutover tested before it goes live. Skip the redirects and you can lose years of Google rankings overnight.

Key facts

• Missing 301 redirects when URLs change is the number one cause of lost rankings during a migration.
• A full off-site backup taken before any change is the non-negotiable first step, so a failed migration is always recoverable.
• Migrating a site can affect email if DNS records (including SPF, DKIM, and DMARC) are not checked and carried across correctly.
• DNS changes take time to propagate, so migrations are best cut over during low-traffic windows with TTLs lowered in advance.
• The safest migrations are built and tested on a staging environment first, then switched over, never edited live.

What counts as a website migration?

A website migration is any move that changes where or how your site runs: a new hosting provider, a new platform or CMS, a new domain name, or a switch from HTTP to HTTPS. Each type carries different risks, but they share one theme, the potential to break links, lose rankings, or take the site offline if the change is not managed carefully. A host-to-host move is usually the lowest risk; a platform change or domain change is the highest.

The reason migrations get a bad reputation is that the visible part, the site looking the same on the new setup, is the easy bit. The parts that break quietly, redirects, DNS, email, and search rankings, are the ones that matter and the ones rushed migrations skip.

Why do website migrations go wrong?

Migrations go wrong most often because URLs change and redirects are not put in place, so search engines and inbound links hit dead pages. When you move platforms or restructure a site, the page addresses frequently change, and without a 301 redirect from each old URL to its new equivalent, the ranking and link equity built up over years is lost. Google treats the old pages as gone and the new ones as brand new.

The other frequent failures are forgetting email. A surprising number of businesses discover their email has stopped working after a migration, because DNS was repointed without carrying across the mail and authentication records. We check SPF, DKIM, and DMARC as part of any migration, because a site move that breaks email is a far bigger problem for a business than a day of slightly slower page loads.

What is on a safe migration checklist?

A safe website migration follows a fixed sequence, and the order matters. The core steps are:

• Take a full off-site backup of the current site, files and database, before touching anything.
• Map every existing URL and plan a 301 redirect for any that will change.
• Record current DNS, including mail and authentication records (SPF, DKIM, DMARC), before changing anything.
• Build and test the site on a staging environment on the new host or platform.
• Lower DNS TTLs a day or two ahead so the cutover propagates quickly.
• Cut over during a low-traffic window, then apply redirects and verify them.
• Confirm HTTPS, forms, email, and search indexing after launch, and keep the old environment until you are certain.

The single rule underneath all of it: do not delete the old site until the new one is proven. Keeping the old environment for a week costs nothing and is the difference between a quick rollback and a crisis.

How long does a website migration take?

A straightforward host-to-host migration can be done in a day, while a platform or domain migration takes longer because of the redirect mapping, testing, and DNS propagation involved. The active work is often quick; the caution around it is what takes time and is worth it. Rushing the redirect map to save a few hours is how businesses lose rankings that took years to earn.

Frequently asked questions

Will I lose my Google rankings if I migrate?

Not if the migration is done properly. Rankings are lost when URLs change without 301 redirects, so mapping every old URL to its new home is what protects them. A host move that keeps URLs identical carries almost no ranking risk; a platform or domain change needs careful redirect planning.

Will my email keep working after a migration?

It will if the DNS mail records are carried across correctly, which is why we record and check SPF, DKIM, and DMARC before and after any move. Email breaks when DNS is repointed without preserving these records. It is one of the most common and most avoidable migration problems.

Should I change platform and host at the same time?

Where possible, no. Changing one thing at a time makes it far easier to identify what caused a problem if something goes wrong. If both need to change, treat it as a higher-risk project with more testing and a longer overlap period keeping the old site available.

Can I migrate my site myself?

A simple host move with a migration plugin is within reach for a confident user, but the redirect mapping, DNS, and email checks are where self-migrations most often come unstuck. If the site matters to the business or has meaningful search rankings, it is worth having someone handle the parts that are expensive to get wrong.

If you have a migration coming up, moving hosts, changing platform, or switching domain, and you would rather not gamble your rankings or your email on it, we are happy to plan and run it with you.