Recommended Free Tools
Before changing hosts, inventory what the site depends on, make and verify a backup of both its files and database, confirm the new environment and credentials, test the copy before sending visitors to it, and keep the old installation available for rollback. Hosting, domain registration, DNS, email, and certificates can be managed by different providers, so plan and verify those services separately.
1. Define what is moving
Start by listing the parts of the site and the services attached to it. A hosting move can include more than page files: it may involve a database, the content management system (CMS), custom configuration, integrations, scheduled jobs, and related services. A clear inventory helps you distinguish what the new host will receive from what must be coordinated with another provider.
As an Amazon Associate I earn from qualifying purchases.
- Record the CMS and version, site files, database, custom settings, integrations, and scheduled jobs.
- Identify who controls hosting, DNS, domain registration, email, and TLS certificates. These may not all be handled by the same company.
- Decide whether you are keeping the same domain and URLs or changing them as part of the move.
- Note any separate services that connect to the site, so you can include them in testing and identify who can confirm their configuration.
That last distinction matters. Moving a site to a different server while keeping its domain is not the same task as changing the domain or moving WordPress to a different URL. WordPress’s Migrating WordPress guide describes different steps for these cases and warns that old URL references can remain in the database, affecting links or theme display.
Free tools Windows power users keep installed
One-click scans. No signup required.
Also identify which provider owns each decision. A hosting company may control the server but not the domain registration, DNS zone, email, or certificate. Do not assume that a change made for the website automatically updates those separate services. If the move includes a URL change, make that explicit in the plan; it affects WordPress settings and the handling of old URL references, not just the location of the files.
#1 Best Overall
- Slim durable design to help take your important files with you
- Vast capacities up to 6TB[1] to store your photos, videos, music, important documents and more
- Back up smarter with included device management software[2] with defense against ransomware
- Help secure your important files with password protection and hardware encryption
- 3-year limited warranty
2. Make a backup you can recover from
For WordPress, back up the WordPress directory, images, plugins, other files, and the database before the move. WordPress.org’s Developer Resources states: “Whether you are moving WordPress from one server to another or to a different location on your server, you don’t need to reinstall.” That does not remove the need to preserve the existing files and database before changing them.
- Make a copy of the site files and database before starting the migration.
- Store a copy somewhere separate from the destination host, so a destination-side problem does not leave you without the backup.
- Check that the backup contains both files and the database and that you can use them to restore the site. Merely seeing a backup file is not proof that it contains everything needed.
Think of the backup as a recovery point, not simply a migration package. The files and database are both part of the WordPress site; preserving only one leaves an incomplete fallback. Keep the copy distinct from the destination installation so a problem on that host does not also compromise the only backup. The cited WordPress handbook establishes the need to back up the files and database, but it does not prescribe a particular verification method or storage product.
An external hard drive is one possible place to store a downloaded backup, but it is only a storage option—not a substitute for checking that both the files and database are included. WordPress does not prescribe a particular storage medium or drive.
3. Confirm the new host’s environment and access
Before copying the site, obtain the destination database details and check the environment requirements for your CMS and site configuration. For a WordPress move, the database connection may need changes if the database has moved to a different server, has a new name, or uses a different database username.
Make sure you can access the information and accounts needed to complete the move: the source and destination hosting environments, database details, and the controls for any separate services that must be checked. When comparing hosts or migration help, ask what access and credentials are required and whether the destination is compatible with your current CMS and database environment. No universal compatibility list is available, so confirm the requirements for the specific site with the host or platform documentation.
Check WordPress database configuration
Review the database entries in wp-config.php, including the database host. WordPress specifically calls out checking that host entry when the database server changes. Make sure the destination database name and username match the values used by the configuration; a mismatch can prevent the site from connecting to its database.
Rank #2
- Slim durable design to help take your important files with you
- Vast capacities up to 6TB[1] to store your photos, videos, music, important documents and more
- Back up smarter with included device management software[2] with defense against ransomware
- Help secure your important files with password protection and hardware encryption
- 3-year limited warranty
Do not treat a successful file copy as proof that the database connection is correct. Confirm the values against the destination details supplied by the host. If the database remains on a different server, its host entry may differ from the source configuration; if the database has been renamed or assigned a different username, those values also need to match. The right settings depend on the actual destination rather than a generic migration template.
Check site URLs and rewrite rules
Confirm the WordPress Address and Site Address after the move. If the domain or URL is changing, do not run a blind replacement of every old URL in the database: WordPress warns that blanket replacement can damage serialized data and says GUID values must not be changed. Use a search-and-replace method compatible with WordPress data, and test redirects rather than assuming they work.
Preserve custom rewrite and redirect rules from .htaccess and test them on the destination. Permalink or rewrite configuration may also need to be reconfigured when the site goes live. URL handling deserves special care if the site’s location is changing: old references can affect links or theme display, while a blanket database edit risks damaging serialized content. Do not change GUID values as part of URL replacement.
4. Test the copied site before cutover
Check the new installation before directing public traffic to it. A pre-switch WordPress test may require temporarily changing the siteurl and home settings, according to the WordPress migration guide. The appropriate safe test method depends on the host and CMS, so confirm the method for your setup rather than assuming one testing approach fits every environment.
- Open important pages and confirm that images and other media load.
- Try forms, checkout flows, integrations, and other functions visitors rely on.
- Check redirects, custom rewrite behavior, and any scheduled jobs.
- Confirm analytics and search-engine settings where they apply.
- Check HTTPS and certificate behavior on the destination.
Use the inventory from the first step to make this test site-specific. For example, if the site depends on a scheduled job or an integration, include it in the checks rather than assuming that normal page loading proves it works. Likewise, test important pages and media, not just the home page. The list above is a practical QA checklist, not a universal official sequence or a guarantee that every site has the same tests.
When assessing a provider’s migration service, ask whether it lets you test the destination before public cutover and what support is available if an error appears. Confirm who is responsible for the test and who will make any necessary corrections. Use current documentation from the host, CMS, and relevant service providers for configuration-specific checks.
Rank #3
- 【Plug-and-Play Expandability】 With no software to install, just plug it in and the drive is ready to use in Windows（For Mac，first format the drive and select the ExFat format.
- 【Fast Data Transfers 】The external hard drives with the USB 3.0 cable to provide super fast transfer speed. The theoretical read speed is as high as 110MB/s-133MB/s, and the write speed is as high as 103MB/s.
- 【High capacity in a small enclosure 】The small, lightweight design offers up to 500GB capacity, offering ample space for storing large files, multimedia content, and backups with ease. Weighing only 0.35 Lbs, it's easy to carry "
- 【Wide Compatibility】Supports PS4 5/xbox one/Windows/Linux/Mac and other operating systems, ensuring seamless integration with game consoles,various laptops and desktops .
- Important Notes for PS/Xbox Gaming Devices: You can play last-gen games (PS4 / Xbox One) directly from an external hard drive. However, to play current-gen games (PS5 / Xbox Series X|S), you must copy them to the console's internal SSD first. The external drive is great for keeping your library on hand, but it can't run the new games.
5. Plan DNS, email, and certificates as separate services
Find out which provider manages the site’s DNS and whether email relies on records in that DNS zone. Confirm the records and change plan with the DNS and email providers before cutover. Do not assume that replacing nameservers or an entire DNS zone is harmless to email: site traffic and mail delivery may depend on different records.
DNS timing, records, and mail migration steps vary by provider and configuration. No universal propagation time, TTL setting, complete record checklist, or provider-independent email procedure can be applied safely to every move. Ask the providers responsible for those services what must be preserved and how they expect changes to be made. In particular, establish whether the change involves a specific DNS adjustment or replacing nameservers or the whole zone; the effect on email depends on the records and services in use.
After cutover, verify that HTTPS works and that the certificate is valid for the site. The certificate provider and setup determine the exact steps; confirm them with the provider responsible for certificates and the destination host. A host migration does not by itself establish that the certificate will behave correctly, so include HTTPS in the post-move checks rather than assuming it follows automatically.
6. Keep a rollback path
Retain the old installation and database while you check the new site. WordPress documents restoring the old files and database and cautions users to back up the database. Keep the old service available until the destination and attached services have been verified; cancelling it too early can remove a practical recovery option.
Before cutover, know which copy is authoritative and how you would restore the old files and database if the new installation fails. Avoid making untracked changes on both installations during the transition, because that can leave you unsure which copy contains the latest content. Agree in advance who will decide whether to roll back and what files and database are involved. This is particularly relevant if a migration service is doing the work: ask what rollback support means in practice instead of assuming it is included.
Do not treat the end of the file transfer as the end of the migration. Keep the prior installation available until the new setup and attached services have been checked, including the functions your site relies on. WordPress’s guidance describes restoring the old files and database; keeping that option available gives you a path back while you confirm the new environment.
Rank #4
- Slim durable design to help take your important files with you
- Back up smarter with included device management software[2] with defense against ransomware
- Help secure your important files with password protection and hardware encryption
- 3-year limited warranty
7. Treat a registrar transfer as a different job
Changing hosting does not require moving the domain registration. ICANN’s Transfer Policy describes a standardized process for domain holders transferring names between ICANN-accredited registrars. If you are changing registrars as well as hosts, manage that as a separate workstream and follow the current instructions from the registrar. The registrar-transfer process is not a guide to moving site files or configuring DNS.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteSo, if your goal is only to put the website on a different server while continuing to use the same domain, do not assume a registrar transfer is part of the task. If you are also changing registrars, coordinate that separately; the registrar’s current instructions govern that process. Keep the distinction clear when comparing migration offers, too: registrar transfer, hosting migration, DNS changes, and email work are not interchangeable services.
8. If you are using migration help, check the scope
A hosting provider’s migration service may cover only some of the work. Before relying on it, get a clear account of what it will move and what remains yours to coordinate.
- Does the service move files and the database, and does it also handle mail or DNS?
- Can you test the destination before public cutover?
- What credentials and access will it require?
- How does it handle rollback if the destination has errors?
- Is the destination compatible with your current CMS and database environment?
- What support is available if the site does not work as expected?
Compare services by scope, test-before-cutover support, rollback support, required access, compatibility, and what happens if errors appear. Ask who is responsible for each part of the work and which providers you must contact yourself. Do not assume that a migration service includes DNS, email, certificates, or a guaranteed rollback. Confirm the scope and responsibilities with the provider before scheduling the move; the evidence available here does not establish a universal price, guarantee, or provider ranking.
If you need help, a managed website migration or hosting provider migration service may be worth evaluating, but compare the promised tasks rather than relying on the label. Determine whether the service handles only website files and database or also coordinates mail and DNS, whether you can test the destination, and how it supports recovery. No individual provider or migration offer is verified here, so use the provider’s current written terms to establish what is included.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Pre-move checklist
- Inventory the site, its components, and the providers responsible for hosting, DNS, registration, email, and certificates.
- Clarify whether the domain or URLs are changing.
- Back up both the site files and database, store a separate copy, and check that they are usable.
- Confirm destination database details and update WordPress configuration if the database host, name, or user changes.
- Verify the WordPress Address and Site Address; handle URL replacement carefully and leave GUID values unchanged.
- Preserve and test custom rewrite and redirect rules.
- Test the copied site before cutover, including important pages and site-specific functions.
- Coordinate DNS, email, and certificate changes with the providers that manage them.
- Keep the old installation and database available until the new setup is verified.
- If using migration help, confirm the scope, required access, testing arrangements, rollback support, and responsibility for any excluded services.
Frequently Asked Questions
Do I need to transfer my domain registration when I change hosting providers?
No. Changing hosting does not itself require moving the domain registration. If you are changing registrars too, treat that as a separate process and follow the current instructions from the registrar. ICANN’s Transfer Policy covers transfers between ICANN-accredited registrars; it is not a guide to moving website files or configuring DNS.
Best Value
- World’s First 6TB 2.5” Portable Hard Drive
- Slim durable design to help take your important files with you
- Vast capacities up to 6TB[1] to store your photos, videos, music, important documents and more
- Back up smarter with included device management software[2] with defense against ransomware
- Help secure your important files with password protection and hardware encryption
What should I back up before moving a WordPress site?
Back up the WordPress directory, images, plugins, other site files, and the database. Keep a copy separate from the destination host and check that both files and database are included and usable. An external hard drive is one optional storage location, not a replacement for verifying the backup.
What should I check in wp-config.php after moving WordPress?
Check the database connection values, including the database host. If the database moved to another server, was renamed, or has a different database username, the configuration may need updating to match the destination. Also confirm the WordPress Address and Site Address after the move.
Can I replace every old URL in the WordPress database when the domain changes?
No. WordPress warns that a blanket replacement can damage serialized data and says not to change GUID values. Use a WordPress-compatible search-and-replace method, then test redirects and verify links and theme display.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →What should I do about DNS and email during a hosting migration?
Find out who manages DNS and whether email depends on records in that DNS zone. Ask the DNS and email providers which records and changes apply to your setup. Do not assume that replacing nameservers or an entire DNS zone is harmless to mail; there is no universal record list, TTL, propagation time, or mail-migration procedure that fits every provider.
When can I cancel the old hosting service?
Keep the old installation and database available until the new site and its attached services have been verified. That preserves a practical recovery path if the destination has problems. Confirm the backup and rollback plan before ending the old service.
The Bottom Line
A safer hosting move begins with a site inventory and a usable backup of both files and database. Confirm the destination’s database and WordPress settings, handle URL changes carefully, test the copied site before cutover, and coordinate DNS, email, and certificates with their providers. Keep the old installation until the new setup is verified, and treat any registrar transfer as a separate task.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
