Skip to content
Godwin LawsonBUILDING WITH PURPOSE

Web Development

Moving Your Website to a New Host: A Practical Migration Checklist

Moving Your Website to a New Host: A Practical Migration Checklist

Move a website to a new host by preparing and testing the destination before directing visitors to it. Keep the old service available until you have checked the website, email arrangements and important business workflows.

A migration is more than copying a folder. The website may depend on a database, DNS records, business email, scheduled tasks and services that need their own transition plan.

Write down what is moving

Start with the domain, current host, DNS provider, website software, databases, email and integrations. Confirm what belongs to the organisation and who can authorise the changes.

A hosting move and a domain transfer are separate decisions. You may be able to change hosting while leaving the domain with its current registrar. Avoid adding extra changes without a business reason.

Area Before the move After the move
Website files and database Capture the required current information Check content and functions
DNS Record the relevant configuration Confirm intended destinations
Email Identify where mail is hosted Test sending, receiving and forms
External services List dependencies and restrictions Verify the connections
Recovery Prepare backup and rollback steps Retain them through verification

Check the destination against real requirements

Confirm software compatibility, storage, expected traffic, backups and support. A low introductory price does not establish that the plan suits an application portal or online store.

Ask about limits that matter to your site, including resource usage and file counts. Confirm which services are included and which need separate configuration. Keep the assessment tied to the problem the move is intended to solve.

If the reason is slow loading, investigate that first. Large images, inefficient code or third-party services can remain slow after a hosting change. A migration should address an identified limitation rather than serve as a guess.

Protect email and other DNS-dependent services

Your email may live with the old host or with a separate provider. Establish which arrangement applies before changing nameservers or cancelling a plan.

Preserve the records needed for mail delivery, authentication and other services. Do not replace the whole DNS configuration with only the website’s new address. Ask the person making changes to record the intended updates and retain the previous settings.

Test direct email and website notifications separately. A mailbox can work while the website’s sending configuration still needs attention.

Decide how to handle changing data

A brochure website may need a short content freeze. A store or portal may receive new records during the move and need a more careful cutover process.

Agree when the final copy is taken, whether submissions or orders pause and how the team will reconcile activity around the transition. Do not assume a copy made several days earlier is ready to replace the live database.

In a hypothetical application portal, an applicant could submit after the first copy was made. The migration plan must preserve that submission rather than quietly move everyone to an older record set.

Test before changing the public destination

Use an appropriate preview or test arrangement at the new host. Check representative pages, images, forms, administrator access and integrations. Make sure the test environment does not trigger unintended live messages or payments.

Retain existing public URLs where possible. If URLs must change, prepare the appropriate redirect plan and test it. A hosting move alone should not require discarding useful page addresses.

  1. Confirm backup coverage and recovery access.
  2. Test the destination against agreed tasks.
  3. Resolve identified problems.
  4. Schedule the final data transfer and DNS changes.
  5. Verify live behaviour after the switch.
  6. Monitor before closing the old service.

Allow for the transition across networks

Different visitors may reach old or new destinations during a DNS transition. Plan for that possibility, particularly if the site accepts changing data. Avoid promising an exact universal switchover time without considering the actual configuration.

Keep staff informed about the cutover and support route. If the business pauses a function, explain what visitors can do instead and when normal service is expected to resume.

Complete a proper handover

Record the new provider, billing owner, backup process and support contacts. Verify that the organisation can access the accounts it needs and that unnecessary old access is reviewed.

Only cancel the old arrangement after checking dependencies, retained data and the agreed recovery window. Confirm whether cancellation affects mailboxes, backups or other websites in the same account.

My hosting and website care support can help scope a migration. Where the move is part of a wider change, combine it with an appropriate digital systems review.

Frequently asked questions

Will moving hosting automatically improve search rankings?

No. The practical goal is a reliable transition that preserves useful pages and functions. Search performance depends on more than the host.

Do we have to move email too?

Not necessarily. Establish the current arrangement and change only the services included in the plan.

What should the migration proposal include?

Scope, dependencies, test criteria, current-data handling, timing, rollback and post-move verification.

Discuss your next step

For help applying this to your organisation, share a short description of your situation and the decision you need to make.

  1. Start on WhatsApp
  2. Send an enquiry through the contact page
  3. Email [email protected]
  4. Call +234 703 799 7791
Lawson Godwin Hezekiah

About Lawson Godwin Hezekiah

Technology entrepreneur, website developer and founder of Mita School and Techmita. I work with businesses, educational institutions, government organisations and NGOs.

Read my story ↗

Keep exploring

Let us work together

Put the ideas into practice.

If your website or digital strategy needs attention, let us discuss a useful next step.