Moving from Hostinger/Bluehost shared hosting to a VPS: a step-by-step guide

To migrate from shared hosting to a VPS, you need to export your files and database (using plugins like All-in-One Migration or Duplicator for WordPress), rent a server with minimum specs of 2 vCPU and 4 GB RAM, deploy a control panel (HestiaCP or FastPanel), and update the A records in your DNS panel to point the domain to the new IP address—this process takes between 30 to 60 minutes and completely eliminates issues with slow loading times and load-based suspensions.

Why migrating from shared to VPS is inevitable for a growing business?

Shared hosting from giants like Hostinger or Bluehost is like a communal apartment where up to 1,000–2,000 websites can reside on a single physical server. The main problem lies in LVE (Lightweight Virtual Environment) limits. As soon as your site starts consuming more than 512 MB of RAM or creates a CPU load exceeding 10-20%, the server returns a 508 error (Resource Limit Is Reached). This kills your SEO rankings and conversion rates.

Bluehost and Hostinger limitations that slow down your site

On shared hosting plans, you are limited not only by RAM but also by the number of concurrent processes (Entry Processes), the number of files (Inodes), and disk read/write speeds (I/O). If your server neighbor is under a DDoS attack or running heavy scraping, your site starts to "lag" because the network channel and disk subsystem are shared. Shared to VPS migration solves this problem by allocating guaranteed resources that belong only to you.

Feature Comparison: Shared vs VPS

If you feel you are overpaying for infrastructure, check out the case study on migrating from AWS Lightsail/EC2 to dedicated, where savings reach thousands of dollars per month for the same power.

Preparing for Migration: Hostinger to VPS and Bluehost to VPS

Before starting the transfer, you need to conduct an audit of the current site. Most Hostinger users use their internal hPanel, while Bluehost clients use the standard cPanel. The main task during a Hostinger to VPS move is to extract the data without losing the link structure or database settings.

Exporting the site via WordPress plugins

For WordPress sites, migration plugins are the most reliable method. They package files and the DB into a single archive, automatically changing paths if necessary.

• All-in-One WP Migration: Ideal for beginners. Creates a .wpress file. The free version has an import limit (usually 512MB), which can be bypassed by editing the plugin code or purchasing an extension.
• Duplicator: Creates two files: an archive (zip/daf) and an installer.php script. It allows you to deploy the site on a new server even without pre-installing WordPress.
• UpdraftPlus: Allows you to back up to the cloud (Google Drive/Dropbox) and restore from it at the new location.

Manual Export (cPanel migration)

If you don't use WordPress or prefer full control, use cPanel migration tools. In the Bluehost panel, go to "Files" -> "Backup Wizard" and select "Full Backup". This will create a tar.gz archive with all your data, emails, and configurations. However, remember: you cannot restore a cPanel "Full Backup" directly to a clean VPS without cPanel (which costs from $15/mo)—you will have to unpack the files manually.

When choosing a new provider, it's worth considering a DigitalOcean alternative to get more resources for the same money you were paying for shared hosting.

Choosing a VPS Configuration and Setting Up the Environment

For a typical WordPress or Laravel site with traffic up to 50,000 visitors per month, the optimal configuration is a server with 2-4 cores and 4-8 GB of RAM. On Valebyte VPS, these resources cost significantly less than similar "Cloud" solutions from marketing giants. A detailed comparison can be found in the article Hostinger VPS vs Valebyte.

Which Operating System to Choose?

The recommended standard is Ubuntu 22.04 LTS or Ubuntu 24.04 LTS. These are the most documented systems, for which ready-made optimization scripts exist. Debian is also an excellent choice for those who value maximum stability and minimal resource consumption "out of the box."

Installing a Control Panel

To avoid configuring Nginx, Apache, PHP, and MySQL via the console, use free panels. They turn your VPS into a user-friendly tool similar to cPanel, but without the unnecessary "bloat."

1. HestiaCP: Lightweight, fast, supports PHP-FPM, and has a built-in file manager.
2. FastPanel: Very easy to learn, one-click installation, excellent SSL support.
3. CyberPanel: Uses OpenLiteSpeed, which provides a huge speed boost for WordPress via LSCache.

# Example of installing HestiaCP on clean Ubuntu
wget https://raw.githubusercontent.com/hestiacp/hestiacp/release/install/hst-install.sh
bash hst-install.sh --interactive no --email [email protected] --password YourStrongPassword --hostname vps.yourdomain.com -f

Step-by-Step Guide: Transferring Files and Database

Once the server is ready and the panel is installed, the main stage of the Bluehost to VPS migration begins. We will look at the method using the Duplicator plugin, as it is the most universal and minimizes 500 errors after the move.

Step 1: Creating an Archive on the Old Hosting

1. Install the Duplicator plugin on the old site.
2. Go to "Packages" -> "Create New".
3. Wait for the scan to complete (ensure there are no file size errors).
4. Download the "Archive" and "Installer" to your computer.

Step 2: Creating the Site and Database on the VPS

In your control panel (e.g., HestiaCP), create a new Web domain. Be sure to create an empty database and a user. Note down these details:

• Database Name: vps_site_db
• User Name: vps_user
• Password: ********

Step 3: Uploading Files

Use FileZilla or the panel's built-in file manager to upload the archive and the installer.php file to the site's root directory (usually /web/yourdomain.com/public_html). If you prefer the console, use scp:

scp installer.php archive.zip root@your_vps_ip:/home/admin/web/yourdomain.com/public_html/

For those migrating from more complex platforms, it will be useful to read about smooth cutover when moving from DigitalOcean to minimize downtime.

DNS Setup and Let's Encrypt SSL

After the files are uploaded, the site will not yet work on your domain because the domain still "points" to the old Hostinger or Bluehost IP address. You need to change the DNS records.

Updating A Records

Log in to your domain management panel (where you bought it—Namecheap, GoDaddy, or Bluehost itself) and find the DNS Management section. Change the value of the A record for the main domain and the www subdomain.

Remember that DNS propagation can take anywhere from 1 to 24 hours. To check where the domain is pointing, use the nslookup yourdomain.com command in your console.

Issuing an SSL Certificate

Once the DNS has updated, find the "Enable SSL" or "Let's Encrypt" button in your VPS control panel (Hestia/FastPanel). Unlike shared hosting, where you are often asked for money for SSL after the first year (Bluehost is particularly known for this), on a VPS you get permanent free certificates. The server will automatically renew them every 90 days via a cron job.

Fine-Tuning and Performance Optimization

Moving to a VPS is only half the battle. To make the site run truly fast, you need to configure the software stack for your needs. Unlike shared hosting, where PHP settings are "set in stone," here you are free to change everything.

PHP-FPM and MySQL Optimization

For high-traffic sites, standard PHP settings might be too weak. Edit the config /etc/php/8.x/fpm/pool.d/www.conf (path depends on the PHP version):

pm = dynamic
pm.max_children = 50
pm.start_servers = 5
pm.min_spare_servers = 5
pm.max_spare_servers = 10
pm.max_requests = 500

This will allow the server to handle more simultaneous connections without delays. It is also recommended to install Redis for Object Caching, which will reduce the database load by 70-80%.

Benchmarks and Verifying Results

After completing the migration, compare the loading speed. Use Google PageSpeed Insights or GTmetrix. Typically, the server response time (TTFB) on a VPS drops from 800-1200 ms to 100-200 ms. If your project requires specific solutions, for example, for backend operations with minimal costs, check out AWS EC2 alternatives.

Don't forget to set up backups. On a VPS, you are responsible for data safety. Set up automatic backup uploads to remote storage (e.g., S3 or another server via rsync) at least once a day.

Conclusions

Migrating from Hostinger or Bluehost shared hosting to a VPS is a necessary step for any project that has grown beyond 500 unique visitors per day. It allows you to gain full control over resources and speed up the site several times over. For a successful migration, it is enough to use the Duplicator plugin, choose a reliable VPS with NVMe drives, and set up a free control panel, which in the long run will save your budget and improve SEO performance.