How to Migrate WordPress to Hostinger in 2026 (Zero Downtime Step-by-Step Guide)

How to migrate WordPress to Hostinger in 2026 — zero downtime DNS cutover steps illustrated with migration method comparison
Zero Downtime WordPress to Hostinger Migration — 13-second motion explainer showing the five DNS cutover steps. Reduced-motion users: see the written steps in the article below. Transcript: Step 1 minus 48 hours lower DNS TTL to 300 seconds; Step 2 minus 24 hours build on Hostinger; Step 3 minus 6 hours test via hosts file override; Step 4 now switch DNS A record; Step 5 plus 24 hours verify and set up SSL LiteSpeed Cache.

Migrating your WordPress site to Hostinger doesn’t have to mean hours of downtime or a botched database import. With the right sequence—and a bit of DNS prep done 48 hours in advance—you can switch hosts while keeping your live site running the entire time.

This guide covers three migration methods (Hostinger’s free managed migration, the plugin-based approach, and manual), the zero-downtime DNS cutover sequence, and the most common errors that break sites during migration. It uses current documentation verified against Hostinger’s hPanel and official guides.

Before You Start: Choose Your Migration Method

There are three ways to migrate WordPress to Hostinger. Which one is right for you depends on your technical comfort and how much time you want to spend:

Three WordPress to Hostinger migration methods compared: Free Managed Migration easy 1 to 2 days; Plugin-based medium 1 to 3 hours; Manual advanced 2 to 4 hours
Three migration methods compared. Free managed migration is available on Hostinger Premium plans and above — Hostinger’s team handles the full transfer within 1–2 business days.

Method 1: Hostinger Free Managed Migration

Hostinger includes free website migration on Premium Shared plans and above as of 2026. You submit a request and their team handles the transfer—no technical work required on your end.

How to Request a Free Migration

  1. Log in to your Hostinger account and open hPanel
  2. Navigate to Account → Migrate Website
  3. Fill in your current host details, login credentials for that host’s control panel, and your domain name
  4. Before submitting: disable two-factor authentication and any anti-bot/CAPTCHA protections on your current host’s panel
  5. Submit the request. The migration typically completes within 1–2 business days

What Hostinger migrates: WordPress files, database, and most plugin/theme configurations. Verify SSL, email configuration, and permalink settings after the migration completes.

Method 2: Plugin-Based Migration (All-in-One WP Migration)

This is the most practical approach for most site owners who want hands-on control without the complexity of manual file transfers.

Step 1: Export Your Site from the Old Host

  1. Install the All-in-One WP Migration plugin on your current WordPress site
  2. Go to All-in-One WP Migration → Export → Export to File
  3. Wait for the export to complete. The free version exports sites up to 512 MB. If your site is larger, you’ll need the Unlimited extension or the manual method below
  4. Download the .wpress export file to your computer

Step 2: Install Fresh WordPress on Hostinger

  1. In hPanel, go to Websites → Add Website
  2. Choose WordPress installation. Hostinger installs a clean WordPress instance automatically
  3. Note your new site’s temporary URL or IP address — you’ll use this to access the new site before pointing your domain

Step 3: Import to Hostinger

  1. Log in to the WordPress admin on your new Hostinger site using the temporary URL
  2. Install All-in-One WP Migration on the new site
  3. Go to All-in-One WP Migration → Import → Import from File
  4. Upload your .wpress export file. This replaces the fresh WordPress installation with your actual site
  5. After import completes, log in with your original WordPress credentials (the import overwrites the temporary admin user)

Method 3: Manual Migration (phpMyAdmin + FTP)

Use this method for large sites, or when you want precise control over what gets moved.

Step 1: Export Your Database

  1. Log in to your current host’s cPanel and open phpMyAdmin
  2. Select your WordPress database from the left sidebar
  3. Click Export → Quick → Go. Download the .sql file

Step 2: Copy WordPress Files

  1. Connect to your old host via FTP (using FileZilla or similar)
  2. Download your entire public_html or www directory to your computer

Step 3: Set Up the New Host

  1. In Hostinger’s hPanel, create a new MySQL database under Databases → MySQL Databases. Note the database name, username, and password
  2. Upload all WordPress files to your Hostinger directory via FTP or hPanel’s File Manager
  3. Import your .sql file via hPanel’s phpMyAdmin: select the new database, click Import, and upload the file

Step 4: Update wp-config.php

Open wp-config.php in File Manager and update these three lines with your new Hostinger database credentials:

define( 'DB_NAME', 'your_new_db_name' );
define( 'DB_USER', 'your_new_db_user' );
define( 'DB_PASSWORD', 'your_new_db_password' );
define( 'DB_HOST', 'localhost' );

The Zero Downtime DNS Cutover

This is the part most guides skip—and it’s where sites get knocked offline unnecessarily. The key principle: DNS TTL changes must happen 48 hours before your cutover, not at cutover.

DNS cutover timeline showing minus 48 hours lower TTL to 300 seconds, minus 24 hours build on Hostinger, minus 6 hours test via hosts file, cutover switch DNS A record, plus 24 hours verify and raise TTL
The zero-downtime DNS cutover sequence. The critical rule: DNS TTL must be lowered 48 hours before the switch — not at the moment of switching. Resolvers cache your current TTL; the new short TTL only kicks in after the old cached value expires.

48–72 Hours Before Migration

  1. Log in to your domain registrar or DNS provider (wherever your A records live—Cloudflare, GoDaddy, Google Domains, etc.)
  2. Find your domain’s A record and lower the TTL to 300 seconds (5 minutes)
  3. Save. This tells DNS resolvers to re-check the record every 5 minutes once you change it—so propagation will be fast at cutover

Test the New Site Before Switching DNS

Before touching DNS, verify your new Hostinger site works correctly by temporarily pointing your local machine at it:

  1. Find your Hostinger server IP in hPanel (under your website’s hosting plan details)
  2. On Mac/Linux, edit /etc/hosts and add: YOUR.HOSTINGER.IP yourdomain.com www.yourdomain.com
  3. On Windows, edit C:\Windows\System32\drivers\etc\hosts with the same line
  4. Visit yourdomain.com in your browser—your machine will now load it from Hostinger. Test all pages, forms, logins, and media
  5. Remove the hosts file entry when done testing

DNS Cutover

  1. At your DNS provider, change the A record for your domain to your Hostinger server IP
  2. Update the www CNAME to point to your root domain
  3. Keep your old host active for 24–48 hours. Some visitors whose ISPs cached the old IP will still hit your previous host during propagation
  4. After 24 hours, verify your domain is loading from Hostinger across multiple locations using a tool like dnschecker.org

After Full Propagation

  1. Raise TTL back to 3600 (1 hour) or 86400 (24 hours)
  2. Verify Hostinger’s Let’s Encrypt SSL certificate has been issued (hPanel → SSL)
  3. Force HTTPS in hPanel settings
  4. Cancel or downgrade your old hosting plan

Post-Migration Setup Checklist

Fix Permalinks First

The most common post-migration issue is 404 errors on all pages except the homepage. In WordPress admin, go to Settings → Permalinks and click Save Changes without changing anything. This flushes the rewrite rules for your new server environment.

Activate LiteSpeed Cache

Hostinger’s shared hosting runs on LiteSpeed servers. The LiteSpeed Cache plugin (pre-installed on Hostinger’s WordPress setup) is the single most effective performance improvement for your site. Activate it and run a full cache purge from the plugin settings.

Verify SSL and HTTPS Redirects

  1. In hPanel, go to Hosting → SSL and confirm the Let’s Encrypt certificate shows as active
  2. Enable Force HTTPS in hPanel
  3. In WordPress admin, verify Settings → General shows https:// URLs
  4. If migrating from Cloudflare, re-add your domain and set SSL mode to Full (Strict)

Check PHP Version

In hPanel, go to Advanced → PHP Configuration and verify your PHP version. Hostinger supports PHP 8.1, 8.2, and 8.3. If your old host was running PHP 7.4 or 8.0, test your site on the newer version before locking it in—older plugins may have compatibility issues with PHP 8.3’s stricter type handling.

Email: Preserve MX Records

If your email runs through Google Workspace, Microsoft 365, or another provider, your MX records must not be overwritten when you switch to Hostinger’s nameservers. In hPanel’s DNS Zone Editor, verify your MX records match your email provider’s specifications exactly. Missing this step is the most common cause of lost email after migration.

Common Migration Errors and Fixes

ErrorCauseFix
404 on all pagesRewrite rules not setSettings → Permalinks → Save Changes
SSL not loading / mixed contentOld SSL rules or http:// URLs in databaseIssue new cert in hPanel; run Better Search Replace to update URLs
White screen of deathPHP version incompatibilityLower PHP version in hPanel → Advanced → PHP Configuration
Missing imagesFile permissions incorrectSet files to 644, folders to 755 in File Manager
Can’t log in after importImport replaced admin userUse your original WordPress credentials
Site loads slowlyLiteSpeed Cache not activatedInstall and activate LiteSpeed Cache plugin; run full purge

Is Hostinger Right for Your Site?

Hostinger is a strong choice for small-to-medium WordPress sites: fast LiteSpeed servers, free SSL and CDN, competitive renewal pricing, and responsive support. Their 48-month promotional pricing is compelling; renewal rates are significantly higher (Premium renews around $10.99/month vs. the promotional rate).

For the majority of small business sites, portfolios, and content sites under moderate traffic, Hostinger’s Business Shared plan offers the best feature set: daily backups, staging environment, LiteSpeed optimization, and free managed migration to get you started. If your site has significant traffic (over 50K monthly visitors on shared hosting) or you need dedicated server resources, Hostinger’s Cloud or VPS plans are worth comparing against Cloudways or WP Engine before you migrate.

Resources

Leave a Comment

Your email address will not be published. Required fields are marked *