How to move a website to a new host and check the result
The hosting that suited a website at launch may stop fitting the project over time. The catalog gets larger, a CRM connection is added, or the software requirements change. Renewal terms or support needs may change too. That is when moving the website to another provider becomes worth considering.
A move takes time, so first identify what you want to improve. If a plugin bug makes the website slow, changing servers will not fix the bug on its own. If your current provider cannot offer the environment or service terms you need, it makes sense to compare alternatives. Our guide to choosing web hosting for a small business can help with that decision.
Once you have chosen a destination, the next question is how to move a working website. Visitors are still sending inquiries, customers are placing orders, and staff are using email while you prepare. Copying files is only part of the job: you need to understand which data changes and what must keep working at each stage.
It helps to divide the move into preparing a copy, testing it, and switching visitors over. The old website stays available while you prepare and test the new one. Bring across the latest changes before cutover, and close the previous account after checking the result. Some projects will need an agreed maintenance window.
We will follow that process from gathering access to checking email and new orders at the destination. This is a general guide for websites on different content management systems. With a website builder, check export options first: downloaded pages may not let you move the editor, forms, or store.
Choose a transfer method first
We will use a common example: a PHP website with a MySQL or MariaDB database moves to hosting with Plesk, keeps its domain, and leaves email with a separate provider. The checks are similar for other platforms, but the copying method may differ.
| Method | When it fits |
|---|---|
| Control panel wizard | It supports your CMS or the required files and databases, and you have access to the old host |
| CMS-specific tool | Your platform has a reliable migration method, and you understand its size and data limitations |
| Manual transfer or specialist help | The wizard does not support the database, or the project has custom settings, active orders, or several connected services |
You do not need to combine a website move, a domain transfer to a new registrar, and an email migration. In our example, only the website's hosting changes. If you are also changing the domain, CMS, or mail provider, plan those changes separately.
1. Prepare access, storage, and a backup
You need access to the old website's files and database, the destination hosting panel, and DNS management. If you do not know where DNS is managed, find out before starting: the domain registrar and DNS provider may be different companies. Give a contractor temporary access and disable it after the move.
Save the files, database export, and current DNS zone outside the old account. Check that the archive opens and that the database can be restored in a test environment using the chosen method. For an active website, files and the database must represent a consistent state. A backup at the host you plan to close should not be your only copy.
In the destination panel, add the existing domain, select compatible software versions, and check storage for the website and temporary files. Do not send visitors to the new server yet. If the destination domain already has data, save it separately: importing may overwrite it.
2. Transfer the first copy
For this example, use Plesk Site Import. Check that the extension is installed and the source is reachable from the new server. The steps use English interface labels.
- Open Websites & Domains, select the destination domain, and choose Website Importing.
- Enter the old website's address and FTP or SSH credentials with access to its files.
- After scanning, select the detected application or the required folders and database. If the wizard cannot find the data, check access and the website's contents before continuing.
- Run the import and check its result in the panel. Then verify the new database connection, PHP version, extensions, and permissions.
A wizard does not automatically transfer every server setting. Recreate required scheduled tasks, outgoing email, and integrations separately. If you import a database independently of the application, you may need to change connection settings in the CMS configuration. See the Plesk documentation for exceptions and advanced settings.
3. Test the copy under its usual domain
To visit the new server before changing public DNS, temporarily add 192.0.2.10 example.com www.example.com to your computer's hosts file. Replace the example IP with the destination server's address and the domains with your own; include www if your website uses it. On Windows, the file is C:\Windows\System32\drivers\etc\hosts; on macOS and Linux, it is /etc/hosts. Editing requires administrator privileges. Save it and refresh the local DNS cache if necessary. For a step-by-step Windows walkthrough, see how to check a website through the hosts file.
Open the usual website address and check the new server's access log to confirm your request reached it. If the panel does not show the log, ask support to confirm the request. A hosts entry affects only your computer: external payment notifications and other servers still use public DNS.
Arrange HTTPS before cutover. An existing certificate can be moved if you have the certificate, private key, and support for installing it; another option, where the provider supports it, is issuance through DNS validation. If a free certificate is only issued after the domain points to the new server, agree on the sequence with support in advance. Do not bypass browser warnings or disable HTTPS for testing. Let's Encrypt explains the validation methods.
Go through the main tasks:
- Open the home page, internal pages, images, and file uploads.
- Check CMS and customer account logins.
- Submit a form and wait for the recipient to receive the email.
- Check search, the cart, and an agreed safe payment test method, where applicable.
- Verify redirects, integrations, and prepared scheduled tasks.
During testing, keep production mailings, background jobs, and payment processing active only on the copy agreed with your team: running both can repeat actions. If a check fails, fix the new copy while leaving the old website working. Remove the hosts entry after local testing so you see the site through public DNS again.
4. Transfer the latest changes
For a website only you edit, you can stop editing during the final copy. For a store, an agreement with staff is not enough: customers, payment systems, and the CRM can also add data. You need a way to stop or correctly redirect all those writes; check it with the developer.
A common sequence is to enable the agreed maintenance mode on the old copy, stop jobs that change data, save a final backup, and transfer the latest changes. Site Import offers Re-sync for supported objects. Make sure a repeat import will not erase anything you need to retain on the new server.
Compare recent records and files. For a store, check order and payment statuses, not just counts. Do not reopen the old copy for new writes while DNS changes spread; open the new one after a final check. Complex integrations may require a different agreed cutover method.
5. Direct visitors to the new server
If the DNS provider stays the same, our example only needs website address changes. A sample zone could be handled as follows:
| Record | Action |
|---|---|
| A for the main domain | Replace the old IPv4 address with the destination server's address |
| AAAA, if present | Set the new IPv6 address, or remove the outdated record if the new host does not provide IPv6 |
| www | A CNAME to the main domain follows that domain; update separate A/AAAA records individually |
| MX and external email records | Preserve them if the mail service is unchanged and its addresses do not depend on the website being moved |
For a CDN or proxy, check its origin address settings too. If you change nameservers instead of website records, first prepare the entire zone, including email and service verification records. With DNSSEC, coordinate signing and the DS record with the provider and registrar.
Not every network sees the change at once. TTL defines a record's cache lifetime; lower it in advance, because doing so does not clear previously cached answers. After changing DNS, test from another network, check requests in the new server's log, and test incoming and outgoing email. A check from your own computer alone is not enough.
6. Finish the move and retain a recovery path
Close the old hosting account after testing through the public domain, confirming new data reaches the right database, and checking email and integrations. Make sure the old server no longer holds required DNS, archives, or background jobs. Save a backup and the original settings outside the account you are deleting.
If a problem appears after cutover, first establish whether the new copy has received data. If it already has orders or inquiries, pointing DNS back without reconciling databases can leave those records outside the live website. Save the new data and coordinate recovery with a specialist.
If the self-service route does not suit the project, you can ask Host4Biz to handle the move: any hosting plan includes transfer of up to three websites per hosting service at no charge. Timing is estimated after access is provided. Prepare the website address, the data to be moved, and email details to start the discussion.
A clear plan for the move
Whether you move the website yourself or work with support, start with a clear list of the data involved and an agreed cutover plan. That makes it easier to share the work and decide which steps to handle yourself and which to leave to specialists.
To discuss a move with Host4Biz, contact us with the current hosting details and what needs to move. Mention email and active integrations separately, so we can discuss the scope and your team's involvement in advance.
We wish you a successful move and a good start with your new hosting.