How to migrate WordPress from Hostinger to your own VPS

To migrate WordPress from Hostinger to your own VPS, you need to create a full site backup using plugins like All-in-One WP Migration or WP-Migrate, prepare a target Ubuntu-based server with an installed Nginx, PHP-FPM, and MariaDB stack, then import the data and update DNS records — this will provide a performance boost of up to 300% and full control over the server configuration at a rental cost starting from $5-10 per month.

Why migrate wordpress hostinger to vps becomes a necessity for growing projects

Switching from Hostinger shared hosting to a dedicated virtual private server (VPS) is driven by the technical limitations of shared plans. Despite the convenient hPanel, Hostinger imposes strict limits on the number of simultaneous PHP processes (usually 20 to 100), RAM (768 MB to 2 GB), and I/O limits. When your project outgrows these boundaries, the site starts returning 503 Service Unavailable or 504 Gateway Timeout errors. The decision to self host wordpress on your own instance gives you access to resources that aren't shared with server neighbors. On a VPS, you are free to choose the PHP version (e.g., 8.3), configure kernel-level caching, and use modern compression protocols like Brotli. This process is very similar to moving from cPanel shared hosting to a VPS, where you also trade a restricted environment for full root access.

Feature	Hostinger Shared (Business)	Valebyte VPS (Standard)	VPS Advantage
Processor (vCPU)	Shared (queue)	1-2 Dedicated Cores	No "noisy neighbors"
RAM	1.5 GB (limit)	2-4 GB (guaranteed)	Stability during traffic peaks
Disk Subsystem	SSD	NVMe	5x higher read/write speed
Configuration Control	Limited by hPanel	Full Root Access	Fine-tuning Nginx/PHP-FPM

Environment Preparation: Setting up the stack for wordpress migration vps

Before initiating the wordpress migration vps, you need to prepare the server side. We recommend using a clean Ubuntu 22.04 or 24.04 OS. Unlike managed platforms where everything is configured for you (similar to moving from AWS Lightsail to VPS), here you are responsible for security and the stack yourself.

System Update and Dependency Installation

Connect to your new VPS via SSH and perform the basic setup:

apt update && apt upgrade -y
apt install nginx mariadb-server php-fpm php-mysql php-curl php-gd php-intl php-mbstring php-soap php-xml php-xmlrpc php-zip certbot python3-certbot-nginx -y

After installation, ensure that MariaDB is secured. Run the mysql_secure_installation command and set a strong password for the database root user. This is a critical step for the security of a self host wordpress installation.

Database Setup for WordPress

Create the database and user that will be used by your site after migration:

mysql -u root -p
CREATE DATABASE wordpress_db DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
CREATE USER 'wp_user'@'localhost' IDENTIFIED BY 'Your_Strong_Password_2026';
GRANT ALL ON wordpress_db.* TO 'wp_user'@'localhost';
FLUSH PRIVILEGES;
EXIT;

Data Export: How to properly prepare the hostinger to vps wp transfer

There are two main paths for a successful hostinger to vps wp transfer: using plugins (suitable for beginners) and manual transfer (for experienced administrators).

Method 1: All-in-One WP Migration Plugin

This plugin creates a single .wpress archive file containing the database, media files, plugins, and themes. 1. Install the plugin on the Hostinger site. 2. Go to "Export" -> "Export to File". 3. Download the resulting archive to your local computer. 4. Note that if the site size exceeds 512 MB, the free version of the plugin may require an extension or using the FTP method.

Method 2: Manual Export via hPanel and FTP

If your site weighs tens of gigabytes, plugins may be unstable. In this case: 1. Go to the Hostinger File Manager, select all files in the public_html folder, and create a ZIP archive. 2. In the "Databases" section (phpMyAdmin), select your DB and click "Export" in SQL format. 3. Download both files. This method is often used when moving from Vercel/Netlify to a VPS for dynamic sites requiring a classic DB structure.

Nginx and PHP-FPM Configuration for Maximum Performance

One of the main reasons to migrate wordpress hostinger to vps is the ability to optimize the web server. Hostinger uses a hybrid of Apache and Nginx, which is not always efficient. We will set up pure Nginx with PHP processing via FastCGI. Create a configuration file for your domain:

nano /etc/nginx/sites-available/mysite.com

Insert the following configuration, optimized for WordPress:

server {
    listen 80;
    server_name mysite.com www.mysite.com;
    root /var/www/mysite.com;
    index index.php index.html index.htm;

    location / {
        try_files $uri $uri/ /index.php?$args;
    }

    location ~ \.php$ {
        include snippets/fastcgi-php.conf;
        fastcgi_pass unix:/var/run/php/php8.3-fpm.sock;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include fastcgi_params;
    }

    location ~* \.(js|css|png|jpg|jpeg|gif|ico|svg)$ {
        expires max;
        log_not_found off;
    }
}

Activate the config and restart Nginx:

ln -s /etc/nginx/sites-available/mysite.com /etc/nginx/sites-enabled/
nginx -t
systemctl restart nginx

Site Import and Resolving Permission Issues

After the files are uploaded to the VPS (via SCP or SFTP to the /var/www/mysite.com folder), you need to restore the database and configure permissions. If you used the manual method, import the SQL dump:

mysql -u wp_user -p wordpress_db < backup_file.sql

Then edit wp-config.php, specifying the new database credentials you created earlier. A crucial point is access permissions. In Hostinger, the panel handles this; on a VPS, you must do it manually:

chown -R www-data:www-data /var/www/mysite.com
find /var/www/mysite.com -type d -exec chmod 755 {} \;
find /var/www/mysite.com -type f -exec chmod 644 {} \;

These commands ensure that Nginx and PHP-FPM can read the files, and WordPress can upload images to the uploads folder. Incorrect permissions are the most common cause of the "Forbidden" error after a wordpress migration vps is completed.

PHP-FPM and Caching Optimization for High Loads

To make your self host wordpress project run faster than on Hostinger, you need to configure the PHP-FPM pool. On shared hosting, you cannot control the number of workers, but on a VPS, this is the key to scalability. Edit the pool config (the path depends on the PHP version):

nano /etc/php/8.3/fpm/pool.d/www.conf

Recommended parameters for a VPS with 2 GB RAM:

• pm = dynamic — dynamic process management.
• pm.max_children = 20 — maximum number of simultaneous PHP processes.
• pm.start_servers = 5 — number of processes at startup.
• pm.min_spare_servers = 5 — minimum number of idle workers.
• pm.max_spare_servers = 10 — maximum number of idle workers.

Also, enable OPcache in php.ini. This allows storing compiled script bytecode in RAM, reducing CPU load by 2-4 times. Such optimizations make a VPS a more cost-effective solution than physical servers in some scenarios, as we discussed in the article Bare-metal vs VPS for ML inference on CPU.

Security and SSL: The Final Stage of Migration

After the hostinger to vps wp file transfer is complete, you must secure the connection. Using Let's Encrypt on your own server is free and automated. Run the command to obtain a certificate:

certbot --nginx -d mysite.com -d www.mysite.com

Certbot will automatically modify the Nginx configuration, adding a redirect from HTTP to HTTPS and paths to the SSL keys. Additionally, it is recommended to set up a basic UFW firewall:

ufw allow 'Nginx Full'
ufw allow OpenSSH
ufw enable

This will close all unnecessary ports, leaving access only for web traffic and SSH management.

Cost of Ownership Comparison: Hostinger vs Valebyte VPS

Many fear that self host wordpress will be more expensive due to hidden fees. However, when calculated over a period of 1-2 years, a VPS often proves to be more economical, especially if you have multiple sites.

Service	Hostinger (Renewal)	Valebyte VPS (Fixed)	Annual Difference
Rent (1 site)	~$12/mo	$5/mo	-$84
Rent (5 sites)	~$20/mo (Cloud)	$10/mo	-$120
Add. Resources (RAM/CPU)	Only by upgrading plan	Flexible scaling	Savings on upgrades

The figures show that migration is justified not only technically but also financially. You stop paying for the "marketing wrapper" and pay only for pure CPU and disk resources.

Conclusions

For a successful WordPress migration from Hostinger to a VPS, it is critical to correctly configure the Nginx + PHP-FPM stack and properly transfer the database, which ultimately gives you full control over the site's performance and security. We recommend using manual file transfer and setting up the configuration "from scratch" to achieve maximum speed and eliminate junk scripts accumulated on shared hosting.