Before you move a website to a new host, confirm what is moving, what must stay working, and who can put things back if a test fails. Those decisions belong in the plan before anyone changes where your domain points.
This website hosting migration checklist is for business owners coordinating a move with a provider. You do not need to edit server settings yourself. You do need clear answers about your website, business email, access, and the point at which the move is considered complete.
Separate the services before you change anything
Several services can arrive on the same invoice and still do different jobs:
- Domain registration: the registrar manages the registration and renewal of your domain name.
- DNS: these records direct traffic for the domain to the relevant services.
- Website hosting: this is where the website’s files and supporting systems run.
- Email hosting: this handles mailboxes and email delivery for your business.
ICANN explains the distinction between a domain name and services such as hosting and email. A website hosting move does not automatically require transferring your domain registration or moving your mailboxes.
Ask the person handling DNS to document which records will change and which will stay. If email is bundled with the old hosting account, establish its future home before canceling that account.
Build an inventory of what the site depends on
List the things a visitor can do, along with the services behind them. A simple brochure website might still send inquiries to a separate system, display an external booking tool, or rely on a licensed plugin.
- Important pages, downloads, images, and existing redirects
- Contact forms, their recipients, and any stored submissions
- Booking, payment, newsletter, or customer-management integrations
- Analytics and search-monitoring access
- Website software, custom code, themes, plugins, and license arrangements
Beside each item, record who understands it and what a successful test looks like. Name a business approver, a technical lead, and a contact at the outgoing provider. “Someone has the login” is unfinished planning.
Agree on the scope and protect existing addresses
A hosting move is easier to review when the pages and their addresses stay the same. Keep a separate list for redesign ideas, new copy, and features you want later. Combining every improvement with the move makes problems harder to trace.
If a page address must change, have the technical lead map the old address to the appropriate new one and plan the redirect. Google’s guidance for moves with URL changes covers this additional work. Record existing redirects too, so they are not quietly left behind.
Ask for a usable backup and a rollback decision
Confirm that a current backup will be taken before the move. For WordPress, a complete backup normally needs both the database and site files. Ask where the copy will be held, who can access it, and how the provider will check that it can be restored.
Then discuss rollback, which means returning to the previous setup if the new one cannot be used. A backup file alone does not answer these questions:
- What failure would make you stop the move?
- Who makes that decision and carries out the recovery?
- How will new inquiries, orders, or edits made during the move be reconciled?
- What old services need to remain available while testing continues?
Restoring an earlier copy can exclude information created afterward. If the site accepts transactions or important submissions, agree on how that information will be protected before choosing a move window.
Choose a window people can actually support
Pick a time when the people needed for testing and decisions are available. Avoid launching a campaign or sending customers to a new offer during the same window.
Confirm whether content editing needs to pause, when the final copy will be taken, and who will tell the team when editing can resume. Ask the provider to explain the expected transition and possible disruption for your setup. Do not treat a general promise of a smooth move as a site-specific plan.
Test the new copy, then test the live site
Before the switch, ask to review the new copy in a test environment. After the switch, repeat the important checks on the public website. Google’s hosting-change guidance recommends testing the copied site and monitoring the transition before retiring the old hosting.
Business acceptance checks
- Open key pages on a phone and a larger screen.
- Follow menu links, buttons, old bookmarked URLs, and downloads.
- Submit clearly labeled test inquiries and confirm receipt at the correct destination.
- Check booking or other connected tools through an agreed safe test.
- Confirm business email still sends and receives.
Questions for the technical lead
Ask them to verify the HTTPS certificate, image and file loading, redirects, monitoring, and any temporary restrictions used for testing. A page appearing in your browser does not prove that every feature works or that search engines can reach the intended pages.
Close the move with a written sign-off
Keep a short list of test results and unresolved issues. Agree when the old hosting can be closed, who handles cancellation, and which services must remain active. Also confirm the new maintenance, backup, and support responsibilities.
Imbark offers managed hosting with proactive maintenance and backups, alongside ongoing website support. If you are considering a move, send us your website address and current hosting questions. Include any email or booking services that depend on the existing setup, and we can discuss the work your site needs.
