A safe website migration comes down to five phases: audit and benchmark the current site, plan the URL map and redirects, build and test on a staging site, launch at a quiet time with a rollback plan, then watch search and security data for at least a month. Skip any one and you risk lost enquiries, broken forms, exposed data or a drop in Google visibility. The checklist below works whether you are moving to a new host, changing platform, switching domain or redesigning the whole site.

Techbug
Keep Your Business Technology Secure
TechBug provides Australian businesses with managed IT services, cybersecurity, cloud solutions and computer repairs, backed by a vendor-agnostic approach.

TL;DR

  • Before you change anything, crawl the current site and record traffic, rankings, conversions and tracking so you can prove afterwards what changed.
  • Map every old URL that changes to its closest new page and put 301 redirects in place before go-live.
  • Test forms, integrations, redirects and speed on a staging site that is blocked from search engines.
  • Launch outside business peaks with named roles, a rollback plan and a fresh backup in hand.
  • Monitor Search Console and your analytics daily for the first month, and keep the new site patched and backed up.

Table of Contents

What counts as a website migration (and why the type matters)

The checklist changes slightly with the type of move, so name yours first.

Type of move What changes Biggest risk
New host, same site Server, DNS, sometimes email routing Downtime, lost email, broken SSL
New platform or CMS Templates, URLs, plugins Changed URLs, lost functionality
New domain Domain name everywhere Lost search visibility, broken links
Redesign Layout, structure, content Pages removed or renamed, slower templates
HTTP to HTTPS or URL tidy-up URL format Redirect chains, mixed content

Most real projects combine two or more. A redesign that also moves to a new host is the common small business case, and it carries the risks of both. Google’s own guidance treats changing URLs, domains or paths as a site move with five stages: general preparation, building and testing the new site, mapping URLs, redirecting, then monitoring. The phases below follow that shape and add the business and security steps that small teams tend to miss.

Phase 1: Plan before you touch the site

Migrations go wrong most often because nobody owned the plan. Start with people and scope, not software.

  1. Name an owner and a working group. Someone has to approve content, someone has to control the domain and hosting logins, and someone has to say “go”. In a small business that may be three hats on two people, which is fine as long as it is written down.
  2. Write the objective and the success measures. “Faster site” is vague. “Contact form submissions equal to or above last quarter, and pages loading under three seconds on mobile” can be checked.
  3. Assess what you are moving. The NSW Government’s migration guidance suggests checking whether the site has been audited, how complex it is, what staff time is available and what approvals apply, along with other organisational changes happening at the same time. It is written for government, but the questions suit any business.
  4. Check contracts and dependencies. Who holds the domain registration? When does the current hosting term end? Does a third party (payment gateway, booking tool, CRM) need to whitelist a new server address?
  5. Agree a timeline and rollback plan. Put dates, responsibilities and a test sign-off step in one short document.

If the new site will serve audiences in more than one country, settle your international SEO strategy at this stage, because it decides your URL structure and is painful to change after launch.

Phase 2: Audit and benchmark the current site

You cannot say a migration worked without a “before” picture. Capture it while the old site is still untouched.

Crawl and inventory

Run a crawler across the live site and export every URL with its title, meta description, status code, redirects and internal links. Add anything a crawler may miss: PDFs, downloadable forms, videos, calculators, landing pages used only in ads, and content hosted elsewhere. Record an owner and a purpose for each item.

An inventory only describes what you have. The next step is an audit that decides what happens to each page: keep, improve, combine, retire or migrate. Pages with no traffic, no links and no business purpose are candidates to retire, which makes the move smaller and the new site cleaner. Sampling a representative set of pages is acceptable when time is short, as the Australian Public Service content audit guidance notes for partial audits.

Record the baseline

Export and save:

  • Organic traffic by landing page, from Google Analytics and Search Console
  • Top queries, positions and click-through rates
  • Conversions: calls, form submissions, quote requests, online sales
  • Backlinks pointing to your key pages
  • Page speed and Core Web Vitals for your main templates
  • A list of tracking tags, pixels, CRM connections and email integrations

That last item matters. Lead-tracking scripts and form-to-CRM connections are quietly lost in rebuilds, and the first sign is a month of “no enquiries” that is really a broken tag.

Back up everything

Take a full copy of the files and the database, plus your DNS records and email settings. Store it somewhere other than the current server, and test that it restores. If your site runs on WordPress, our WordPress maintenance checklist covers how to verify backups on a daily, weekly and monthly rhythm.

Phase 3: Map URLs and redirects

This is the phase that decides whether your search visibility survives.

  1. List every URL that will change. Include old URLs with backlinks, URLs in your email signatures, printed material, Google Business Profile and social profiles.
  2. Match each to the closest genuine replacement. Relevance matters more than volume. Where a page has no real successor, let it return a 404 or 410 rather than forcing everything to the homepage.
  3. Use 301 redirects, one hop only. Chains (old to interim to new) waste crawl effort and slow users. Fix them in the map, not after launch.
  4. Update internal links so they point straight at the new URLs rather than relying on redirects.
  5. Update canonical tags and the XML sitemap to the new URLs.
  6. Plan to keep the redirects. Google notes that for medium-sized sites it can take a few weeks or more for a move to be fully processed. Keep redirects live for at least a year, and longer for URLs with strong backlinks.

A simple spreadsheet with columns for old URL, new URL, redirect type, status and tester initials is enough for a small site. For a larger one, generate the rules in bulk and test them as a batch.

If the domain name changes

Once the redirects are live, tell Google using the Change of Address tool in Search Console. You need to be a verified owner of both the old and new properties, and the tool works at domain level only. Keep the old domain registered and renewed; letting it lapse breaks every redirect and hands your old links to whoever buys it next.

Phase 4: Build the new site and test on staging

Phase 4: Build the new site and test on staging

Build on a staging copy that mirrors production. Block it from search engines and put it behind a password, then write down that the block must be lifted at launch (and that the production site must not inherit a “noindex” setting from staging). That one oversight has hidden many new sites from Google for weeks.

Staging test list

  • Redirects: crawl the staging site against your inventory. Each old URL should resolve in one hop to the right page.
  • Content: every important page has a title and a single H1; no orphaned pages; images and PDFs load.
  • Forms and integrations: submit every form, check the email arrives in the right inbox, and confirm the CRM, booking and payment tools receive the data.
  • Responsive design: test on real phones, not just a resized browser window.
  • Accessibility: check against WCAG 2.2 AA, including contrast, keyboard navigation and form labels.
  • Speed: test your main templates, not just the homepage.
  • Tracking: confirm analytics, conversion events and any ad pixels fire once, not twice.
  • Legal pages: privacy policy, terms and cookie notices are current.

Security before launch

A new site is a fresh attack surface. Websites are routinely probed by automated attacks, so harden it before it is public: unique admin accounts with multi-factor authentication, no leftover test users, current plugins, and a firewall or managed security layer. Our website security checklist lists the audited steps we work through.

Who patches what also depends on how the site is hosted. The Australian Cyber Security Centre explains that under the cloud shared responsibility model, the provider looks after its underlying infrastructure while you remain responsible for your data and, depending on the service, your credentials and configuration. business.gov.au makes a related point: self-hosted content management systems need current security patches, whereas cloud-based providers should keep sites safe from attacks on their side. Know which model you are buying before you sign.

Phase 5: Moving to a new host without losing email

Moving hosts is the part that frightens owners most, mostly because of DNS. The sequence that keeps risk low:

  1. Lower your DNS TTL (the caching time on your records) to a few minutes a day or two before the move, so changes take effect quickly and a rollback is fast.
  2. Set up the new hosting environment and copy files and the database. Check PHP or runtime versions match what the site needs.
  3. Preview the new server using a hosts file entry or a temporary URL, while the public still sees the old site.
  4. Document every existing DNS record before touching anything: A, CNAME, MX, TXT (including SPF, DKIM and DMARC) and any verification records. Missing an MX or SPF record is how business email quietly stops arriving.
  5. Confirm SSL. Issue the certificate on the new host before the switch so visitors never see a browser warning.
  6. Freeze content shortly before cutover, or plan to re-sync recent changes (orders, enquiries, blog posts) afterwards.
  7. Change DNS and keep the old host live and untouched until you are confident. Do not cancel it the same day.

A hosting move is also a good moment to ask where your data physically sits. If privacy obligations or customer preference make that matter, choose a provider that states it clearly. Our cloud migration checklist for SMBs covers the wider questions around moving business systems, and if email is changing platforms at the same time, the DNS steps in our guide to moving from Google Workspace to Office 365 apply.

Phase 6: Launch day

Choose a quiet window. For most Australian small businesses that means an evening or weekend, not the Monday morning rush or a sale period. Tell staff, your marketing agency, payment providers and anyone else who touches the site.

Launch runbook

  1. Take a final backup of the old site and database.
  2. Put the old site into maintenance mode if content or orders could change mid-move.
  3. Deploy the new site and switch DNS, or go live with the new build.
  4. Switch on the 301 redirects and remove the staging noindex setting.
  5. Check SSL, the homepage, your top ten landing pages and the main redirect paths.
  6. Submit every form and place one test order or booking.
  7. Submit the new XML sitemap in Search Console.
  8. Send a short status message to stakeholders, with a named person to call if something breaks.

Agree a rollback trigger beforehand: for example, if checkout or the contact form is not working within an hour, DNS reverts to the old host. Having the decision made in advance stops a stressful judgement call at 10 pm.

Phase 7: The first 30 to 90 days

Launch is the midpoint, not the finish line.

  • Days 1 to 7: check Search Console daily for crawl errors, coverage drops and 404 spikes. Re-crawl the live site and fix any redirect chains or broken internal links.
  • Weeks 2 to 4: compare organic traffic, rankings and conversions against your baseline. Some fluctuation is normal while Google reprocesses the site; a sustained fall on specific pages usually points to a missing or poorly matched redirect.
  • Month 2 to 3: review Core Web Vitals on real-user data, update any outside listings and directories still linking to old URLs, and ask partners with strong backlinks to update them.
  • Ongoing: keep the CMS, themes and plugins current, and keep verifying backups.

Do not decommission the old hosting or let the old domain lapse until the redirect period is well over.

Redesign best practices that make the migration easier

If you are redesigning at the same time, a few habits reduce risk:

  • Define purpose and scope first. Decide what the site must do for the business (generate quotes, take bookings, support existing clients) and design toward that.
  • Keep a logical structure. Group related content and keep key pages within a few clicks of the homepage.
  • Do not change everything at once. Changing URLs, content, design and host together makes problems hard to trace. Where you can, stage the changes.
  • Protect what already performs. Pages that bring in traffic and enquiries should keep their URLs, headings and core content unless there is a strong reason to change them.
  • Build security in. Multi-factor authentication, least-privilege accounts and patching are cheaper at build time than after an incident.

Our view: treat a migration as an IT project, not just a web project

We see migrations go wrong in the same quiet places. The site itself usually moves fine. What breaks is everything around it: the email that stops because an MX record was missed, the contact form that now sends to a mailbox nobody checks, the old admin account that nobody removed, the backup that was never tested, the domain registered under a former employee’s personal email.

That is why we handle migrations with the whole business technology picture in view, not only the website. We are vendor-agnostic, so the advice on hosting, platform and tooling is based on what suits your business rather than what we are tied to. Our rule of thumb is simple: if you cannot restore the old site from backup today, you are not ready to move it, and if you cannot name who owns the domain login, you are not ready to launch.

— Ru

Need a hand with the move?

Techbug is a Brisbane IT support company working with small and medium businesses across Australia. We can look after the technical side of a migration: backups, hosting and DNS, email continuity, security hardening and post-launch monitoring, with emergency support if something goes wrong on the day. See our IT services for business or get in touch to talk through your project.

Techbug

If you would rather have ongoing care after launch, our managed IT services cover proactive monitoring, patching and backups so the new site stays healthy.

FAQ

How long does a website migration take?

A small brochure site can move in a day once the new site is built and tested. The planning, audit and redirect mapping usually take longer than the move itself, often a few weeks. Google notes that for medium-sized sites it can take a few weeks or more for a move to be fully reflected in search.

Will I lose my Google rankings if I migrate my website?

Not necessarily. Rankings are most at risk when URLs change without proper 301 redirects, when pages are dropped, or when staging settings such as noindex carry over to the live site. Mapping every changed URL, testing on staging and monitoring Search Console after launch keeps the risk low.

Should I migrate to a new host and redesign at the same time?

It is possible, but each extra change makes problems harder to diagnose. If you can, move hosts first with the existing design, confirm everything is stable, then launch the redesign. If a single launch is necessary, test more heavily on staging and keep the old host running as a fallback.

What should I back up before migrating?

Back up the site files, the database, your DNS records, email settings and any configuration for integrations. Store the copy off the current server and test a restore before you start. Keep the backup until the new site has run cleanly for at least a few weeks.

How long should I keep redirects in place?

Keep them for at least a year, and indefinitely for old URLs that still attract backlinks or traffic. Removing them early breaks inbound links and can undo the work of the migration.

Sources