PC 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 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteThe safest way to move a WordPress site from Bluehost to a Linux VPS is to build and secure the VPS first, make a restorable copy of the files and database, transfer and configure them, test the new server privately, and change DNS only after the site passes an acceptance checklist. Keep the Bluehost account running until DNS propagation, email, HTTPS, and real-world requests are verified.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
This sequence avoids the most damaging migration mistakes: an incomplete database export, mismatched wp-config.php credentials, broken serialized URLs, missing cron or mail settings, and a DNS switch made before the destination is ready.
As an Amazon Associate I earn from qualifying purchases.
What you need before starting
Plan the move as a controlled change rather than a file copy. You need administrative access to the Bluehost account, the domain’s DNS provider, and the VPS; SSH access or another secure transfer method; database credentials; and a maintenance or content-freeze window for the final synchronization.
- Record the domain name, Bluehost document root, DNS host, PHP and MySQL/MariaDB versions, active plugins, scheduled tasks, mail routes, payment gateways, webhooks, external storage, and any server-specific rules in
.htaccess. - Confirm that the VPS has enough CPU, memory, storage, and bandwidth for the site, including its media library and database growth.
- Decide whether the domain will remain the same. A same-domain move normally needs no content URL rewrite; a domain change requires a serialization-safe search-and-replace.
- Choose who will perform the work. Manual migration gives the most control, while a guided tool or professional service can reduce shell and database work but may offer less control over unusual configurations.
Bluehost describes its self-service migration tool as designed for a success rate of at least 85% in collaboration with its partner team (2026). Treat that as the provider’s stated target, not a guarantee for your site or a substitute for your own backup and testing.
#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
Manual migration versus guided help
| Factor | Manual migration | Guided tool or professional service |
|---|---|---|
| Server control | Full control over Linux distribution, web server, PHP, database, firewall, and tuning. | Control varies; the provider may standardize the stack. |
| Unusual or large sites | Better suited to custom plugins, large databases, multisite, external storage, and bespoke cron jobs when you understand the dependencies. | Convenient for conventional single-site installations; confirm limits before starting. |
| Testing and rollback | You design the private preview, acceptance checklist, and rollback window. | Ask exactly how staging, DNS, SSL, email, and rollback are handled. |
| Skills required | SSH, Linux permissions, SQL import/export, web-server configuration, and DNS. | Less hands-on work, but you still need access and must validate the result. |
| Cost and coverage | Usually your VPS and any storage costs; your time is the main operational cost. | Pricing, geography, support hours, and program availability must be confirmed with the provider. |
For a business site that receives orders, bookings, comments, or form submissions, the deciding factor is not convenience alone: choose the method that gives you a verified backup, a private test path, and a practical rollback plan.
1. Inventory the current site and freeze changes
Make an inventory
Write down every service that must continue working after the move. Include the domain and subdomains, DNS records, mail providers and MX records, PHP extensions, database name, WordPress administrator accounts, active plugins and themes, scheduled jobs, payment callbacks, webhooks, CDN or object-storage endpoints, redirects, robots rules, and analytics or consent integrations. Note the current document root and whether the site uses a custom .htaccess file.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Schedule a content freeze
Arrange a short window in which editors stop publishing and visitors cannot create data that must be preserved. For an online store, pause new orders if necessary; for a community or lead-generation site, account for comments, registrations, and form submissions. The freeze must cover the final database export, otherwise transactions created on Bluehost after the export will not exist on the VPS.
2. Create and verify a restorable backup
Download the complete WordPress directory
Copy the entire installation, not just the active theme. The backup must include wp-content (uploads, plugins, and themes), wp-config.php, WordPress core files, hidden files such as .htaccess, and any server-specific configuration that the site relies on. WordPress.org’s migration guidance calls for backing up the WordPress directory, images, plugins, other files, and database before moving servers.
You can use the Bluehost file manager, SFTP, or SSH. If shell access is available, a compressed archive is convenient:
tar -czf wordpress-files.tar.gz -C /path/to wordpressDownload the archive to a local computer and keep a second copy on separate storage. An external hard drive or SSD is useful for the local recovery copy, but it should not be the only copy; retain an off-site copy as well.
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
Export the database as SQL
Use phpMyAdmin’s Export function or a command-line dump. Bluehost’s manual workflow identifies phpMyAdmin for exporting and SQL import for the destination.
mysqldump -u DBUSER -p DBNAME > wordpress.sqlReplace the database values with the real credentials; do not publish the password in shell history or documentation. For a large database, compress the dump after confirming it completed:
gzip wordpress.sqlCheck that the SQL file is non-empty, begins with normal dump statements, and can be opened or decompressed. Preserve the original unmodified export. A backup is only useful if you can locate it and restore it, so record where each copy is stored and who can access it.
3. Provision and secure the Linux VPS before DNS changes
Install the operating system and updates
Select a supported Linux distribution offered by the VPS provider. Apply all available security updates, create a non-root administrative user, and use SSH keys rather than sharing a root password. Configure a firewall that allows SSH from your administration path and permits HTTP and HTTPS traffic. Keep a documented recovery method in case an SSH rule locks you out.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Install the web stack
Install a web server, PHP, and MySQL or MariaDB. Many Linux servers use the LAMP pattern—Linux, Apache, MySQL, and PHP—but the exact stack can differ. Match the source site’s PHP behavior and required extensions before importing the production database; changing PHP and hosting at the same time makes failures harder to isolate.
Create the database and least-privilege user
Create a new database, a dedicated user, and a strong password. Grant that user access only to the WordPress database. Record the database name, username, password, and host because those four values will be needed in wp-config.php. Do not reuse an administrative database account for the public site.
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.
Create the virtual host or server block
Configure the domain’s virtual host (Apache) or server block (Nginx), set its document root to the WordPress directory, and enable the rewrite rules required for permalinks. Make sure the VPS can serve the domain before DNS points to it; private preview methods in the next section provide that test path.
4. Transfer files and import the database
Upload the files securely
Transfer the archive or directory with SFTP, SSH, or another encrypted method. Extract it into the destination document root and verify that wp-content/uploads, themes, plugins, and any custom files are present. Do not overwrite a known-good backup with an unverified transfer.
Recommended Free Tools
Import the SQL dump
Import the dump into the empty destination database. With a decompressed file, a typical command is:
mysql -u DBUSER -p DBNAME < wordpress.sqlFor a compressed dump, decompress it first or use a pipeline appropriate to your shell. Watch for permission, character-set, packet-size, or timeout errors; an import that stops partway through is not a valid migration.
Update wp-config.php
Edit the destination copy so DB_NAME, DB_USER, DB_PASSWORD, and DB_HOST match the new database. Preserve the table prefix and salts unless you deliberately intend to invalidate all sessions. Keep the file outside public downloads through correct web-server configuration and permissions.
Set ownership and permissions
The web-server user must be able to read the application and write only to locations that require it, normally the uploads directory and selected cache directories. Avoid making the entire WordPress tree world-writable. Check ownership after extraction because archives copied as an administrator can leave files that PHP cannot update.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →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
Handle URLs safely
If the domain stays the same, do not run a broad URL replacement merely because the server changed. WordPress stores serialized values in options and metadata; a naïve text replacement can corrupt lengths and break widgets or plugin settings. If the domain changes, use a serialization-aware tool such as a properly configured WordPress command-line search-and-replace, then inspect redirects, canonical URLs, media links, and plugin settings.
5. Preview the VPS privately and test it
Choose a private preview method
Use a temporary hostname, a staging domain, or a local hosts-file override. A hosts-file entry maps the domain to the VPS IP only on your test computer, so public DNS still sends ordinary visitors to Bluehost. Remove the entry after testing or update it when the VPS address changes.
Run an acceptance checklist
- Load the homepage, several posts, pages, categories, archives, and a representative media-heavy page.
- Open images, downloadable files, menus, search, pagination, feeds, and any custom post types.
- Sign in and out of the WordPress dashboard; verify that editors and administrators retain the expected access.
- Submit contact, registration, comment, and other forms. For stores or booking systems, test a complete checkout in the appropriate test mode and verify payment or webhook callbacks.
- Exercise important plugins, scheduled jobs, importers, caches, backups, and integrations with external storage.
- Resize the browser and test the mobile layout, redirects, robots and indexing settings, and error logs.
- Open Settings → Permalinks and click Save Changes once the site loads on the VPS. This refreshes rewrite rules; it does not require changing the permalink structure.
Issue and verify TLS
Obtain or stage the TLS certificate for the domain on the VPS before cutover. Test HTTPS, the canonical host, HTTP-to-HTTPS redirects, certificate-chain validity, and mixed-content warnings. A site that works over HTTP but fails over HTTPS is not ready for DNS.
6. Lower TTL and cut over DNS
Prepare the records
If your DNS provider permits it, reduce the domain’s record TTL to 300–600 seconds about 24–48 hours before the move. This can shorten the caching period for resolvers that honor the lower value, but it cannot force every network to update immediately.
Change the destination
At the scheduled cutover, change the domain’s A record (and AAAA record if you use IPv6) to the VPS address, or change nameservers if DNS is moving as well. Confirm that the web-server virtual host, TLS certificate, and mail records are already configured before saving the change.
Monitor both endpoints
Keep Bluehost active while caches expire. Check the site from multiple networks and resolvers, watch VPS access and error logs, test forms and checkout again, and verify that mail continues to flow. Some visitors will reach the old server during propagation; do not delete or alter its content until the rollback window has passed.
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
7. Finalize the migration and harden the VPS
When the new server consistently passes the acceptance checklist, take a fresh post-cutover backup and configure automated off-site backups. Confirm that updates, monitoring, cron jobs, HTTPS renewal, and email delivery work without manual intervention. Document SSH access, database credentials storage, firewall rules, backup locations, and the exact DNS records.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsOnly then should you cancel Bluehost or remove the old site. Before doing so, check the rollback window, domain registration, DNS billing, mail dependencies, and any service that still points to the old IP. If a serious defect appears, revert the DNS record to Bluehost, restore the last known-good database if required, and investigate on the VPS without extending the outage.
Common failure modes and fixes
“Error establishing a database connection”
Recheck the four database constants in wp-config.php, confirm the database user has privileges, verify that the host name is correct, and test a direct database login from the VPS. A successful SQL import does not prove that WordPress is using the same credentials.
Pages return 404 while the homepage works
Enable the virtual host’s rewrite support, confirm the document root, and resave Settings → Permalinks. Check that the migrated .htaccess rules are compatible with the new web server.
Images or uploads fail
Confirm that the files transferred completely, the upload paths are correct, and the web-server user can write to the uploads directory. Review PHP size and timeout limits if only large files fail.
Redirect loops or mixed content appear
Check the site URL and home URL, reverse-proxy HTTPS detection, canonical redirects, and hard-coded HTTP resources in themes or plugins. Do not apply a blanket database replacement without accounting for serialized data.
Forms, mail, or webhooks stop working
Recreate required mail transport settings, verify DNS authentication records and firewall egress rules, and update third-party callback allowlists to include the VPS address. Inspect application and mail logs rather than assuming the DNS switch is the only cause.
Cron tasks do not run
Compare the old scheduled jobs with the VPS configuration, confirm the system time zone and permissions, and run a job manually while watching logs. Some sites depend on a server-level cron entry rather than WordPress’s visitor-triggered scheduling.
Some users still see Bluehost
This is expected while cached DNS records expire. Check authoritative DNS and several public resolvers, keep both servers available, and do not declare success based on one network alone.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Minimum go-live checklist
- Complete files and SQL backups exist in local and separate off-site locations.
- VPS updates, SSH keys, non-root administration, firewall, web server, PHP, and database are configured.
- Database credentials, document root, ownership, and permissions are verified.
- Private preview passes content, login, forms, checkout, plugins, cron, redirects, mobile, logs, and HTTPS tests.
- TTL was reduced when feasible, DNS records are ready, and the old server remains available for rollback.
- Post-cutover backups, monitoring, mail, certificate renewal, and recovery documentation are active.
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.
