Setting up Hostinger is straightforward if you start a fresh site, but migrating a live site is where most guides skim the hard parts. This guide walks through every Hostinger setup decision in order, then breaks down the four migration paths so you can pick the one that actually fits your situation. It covers the prep work that protects your email and search rankings, the testing steps that prevent broken redirects, and the post-migration checks that catch problems before your visitors do.
What This Guide Covers
You will find an end-to-end Hostinger onboarding workflow, a comparison of all four migration methods (the Hostinger Automatic Migration tool, the free Hostinger expert migration, a cPanel-to-Hostinger transfer, and a manual SFTP move), a pre-migration insurance backup, DNS cut-over instructions that preserve email, a post-migration verification checklist, and a rollback plan if something goes wrong. The deeper plan-by-plan trade-offs sit in the broader Hostinger hosting guide, while the verdict on whether Hostinger is the right host at all lives in the Hostinger review.
Before You Start: Pick the Right Migration Method
The fastest way to avoid a botched migration is to spend five minutes on this decision. The right method depends on where your site lives today and how much downtime you can absorb.
- Live WordPress site, you have admin login: Hostinger Automatic Migration tool. Usually under two hours, zero downtime, no plugin install.
- Live non-WordPress site on cPanel: Hostinger cPanel/WHM transfer through the same migration form.
- Offline site or only have a backup: Free expert migration with file upload. Plan for a 24-hour SLA.
- You want full control or have a non-standard stack: Manual SFTP and phpMyAdmin export, with All-in-One WP Migration or Duplicator as the safer middle ground for WordPress.
- WordPress multisite, WordPress.com hosted, or a builder like Wix, Squarespace, or Shopify: Automatic tool will reject it. Plan a manual rebuild instead.
Step 1: Choose a Plan and Create Your Hostinger Account
Hostinger sells four shared tiers (Premium, Business, Cloud Startup, Cloud Professional) plus dedicated VPS and managed WordPress plans. For a single migrating WordPress site, Business is the practical floor because it includes the Auto Installer, daily backups, free CDN, and the staging environment you will need before you switch DNS. Premium works for hobby sites but skips daily backups and staging, which makes migration recovery harder. Cloud Startup makes sense once your traffic clears the low five figures per month.
Pay attention to the renewal price, not the intro price. Hostinger's intro pricing typically locks in only for the first term, and the renewal can be three to four times higher. Buying a longer term (24 or 48 months) keeps the cheaper rate locked in longer, but only if you are confident you will stay. If you have not made that call yet, start with a 12-month term and try the Hostinger plans at the published price.
During checkout, do not buy the recommended domain through Hostinger unless you want to consolidate registration. Keeping your domain at a separate registrar (Cloudflare, Porkbun, Namecheap) gives you faster DNS, easier portability if you change hosts later, and a cleaner separation between domain ownership and hosting.
Step 2: First-Time hPanel Setup
After signing up you land in hPanel, Hostinger's custom control panel that replaces cPanel. The onboarding wizard prompts you to either create a new site or set up an existing site. If you are migrating, choose "existing site" so hPanel does not try to provision a WordPress install on top of the one you are about to import.
Three settings matter before you do anything else. Add your domain under Domains so the migration can target a real host name. Enable the free SSL under SSL once the domain is added so HTTPS works automatically after cut-over. Confirm your server location under Hosting; pick the data center closest to most of your visitors because moving servers later is a paid operation. The main Hostinger guide goes deeper on hPanel's quirks if you are coming from a cPanel background.
Step 3: Pre-Migration Insurance Backup
Before you trigger any migration tool, make your own backup that does not depend on Hostinger or your old host. This is the step almost every Hostinger tutorial skips, and it is the one that saves you when a migration silently corrupts data. For WordPress, install UpdraftPlus on the live site, run a full backup including database, plugins, themes, and uploads, and download the archive to your local machine. For non-WordPress sites, pull a full SFTP copy of the document root plus a SQL dump from phpMyAdmin.
Store the archive somewhere outside both hosts (a cloud drive, an external disk). If anything goes wrong over the next 48 hours, this is your rollback artifact. It costs you 15 minutes and saves you days of recovery work.
Step 4: Run the Migration
Method 1: Hostinger Automatic Migration Tool
Open hPanel, go to Websites, and click Migrate Website. Choose the WordPress option, paste the source URL, and supply your WordPress admin username and password. Hostinger logs in, exports the site, transfers it, and imports it onto your new account.
Two preparation steps trip up most users. First, disable two-factor authentication on the source WordPress admin temporarily. Hostinger's tool cannot complete the second factor and will fail silently. Second, disable any anti-bot plugin (Wordfence's login challenge, Cloudflare Turnstile on /wp-admin) for the migration window. Re-enable both as soon as the migration completes.
Typical run time is 30 to 120 minutes for a site under 5 GB. Hostinger emails you when it finishes and gives you a preview URL on a hostinger.com subdomain so you can test before you point DNS. Skip ahead to Step 6 once the email arrives.
Method 2: Free Hostinger Expert Migration
If the automatic tool rejects your site, the migration form will offer the expert migration path. You upload your backup files directly (.zip, .tar, .tar.gz, .sql), and Hostinger's migration team handles the import within 24 hours. This is the only path that supports custom builds, exotic stacks, and offline sources. It also handles Joomla, OpenCart, and bare static sites that the WordPress tool will not touch. The trade-off is the SLA: 24 hours is a real wait, and there is no progress indicator beyond email updates.
One catch: the expert migration does not move email accounts, cron jobs, custom SSL certificates beyond the standard Let's Encrypt, or FTP user accounts. You will set these up by hand once the site files land. If you depend on professional email through your old host, plan email separately (Google Workspace, Zoho Mail, or hosted email through Hostinger Business).
Method 3: cPanel to Hostinger Transfer
If your old host runs cPanel or WHM, the migration form has a dedicated cPanel path. Provide your cPanel login URL and admin credentials, and Hostinger pulls a full account backup using the standard cPanel transfer format. This covers files, the MySQL database, the email accounts cPanel manages, and most cPanel-stored settings.
Email migration is the exception. The cPanel pipe does not include email delivery state (existing messages, IMAP folders), only the account definitions. If you want your historic email to land at Hostinger, export it from your old IMAP server to a desktop client first, then re-upload after Hostinger provisions the accounts.
Method 4: Manual Migration with a Plugin or SFTP
Manual migration suits you when the automated paths fail or when you need fine control over what moves. For WordPress, the safest middle ground is the All-in-One WP Migration plugin (free, 512 MB import limit; paid extension lifts that to 5 GB+) or Duplicator. Both export a single archive that bundles files and database, and they handle URL rewrites during import automatically.
For a raw SFTP move, copy /public_html (or your document root) from old to new with an SFTP client like FileZilla. Export the database via phpMyAdmin on the old host, import via phpMyAdmin on Hostinger, then update wp-config.php with the new database credentials. For WordPress, run the standard wp_options URL update or use the WP-CLI search-replace command before you flip DNS.
Step 5: Test Before You Switch DNS
Hostinger provisions a temporary preview URL (yourdomain.hostingersite.com style) the moment your account is live. Use it. The single biggest mistake new Hostinger users make is pointing DNS first and testing second, which means real visitors hit a broken site while you are still finding problems.
Test in this order on the preview URL: home page loads, the most-trafficked five landing pages load, your primary forms submit, your checkout completes (use a real card or a Stripe test mode if available), images render (not just placeholders), and HTTPS is forced everywhere. If any test fails, fix it on the Hostinger preview before DNS cut-over.
One subtle issue: if your site has hard-coded references to your old hostname (CDN URLs, embedded scripts, theme customizer values), they will silently keep loading from the old host. Run a Better Search Replace pass against the database to catch these, then retest. The companion step-by-step WordPress migration walkthrough covers the specific search patterns to run.
Step 6: Point Your Domain to Hostinger
DNS cut-over is the moment your live visitors start hitting Hostinger. Plan it for low-traffic hours, lower your DNS TTL to 300 seconds 24 hours in advance (so the propagation finishes faster), and have both hosts running in parallel until propagation completes.
You have two cut-over paths: change nameservers (Hostinger handles all DNS, simpler, but moves everything including MX records) or change A records only (keep DNS where it is, surgical). Most migrations should use nameservers because Hostinger pre-populates the records correctly, but A records make sense if you have a complex Cloudflare or third-party email setup you do not want to rebuild. The dedicated how to point a domain to Hostinger guide covers both paths with registrar-specific screenshots.
Email continuity is the part most guides bury. If you are using third-party email (Google Workspace, Microsoft 365, Zoho), copy your MX records, SPF, DKIM, and DMARC TXT records from the old host to Hostinger's DNS zone before you flip nameservers. Miss this and email goes dark for 24 to 48 hours.
Step 7: Post-Migration Verification
Once DNS resolves to Hostinger (use dnschecker.org to confirm globally), walk through this checklist in order. Catch problems in the first hour while you still remember what changed.
- Home page and top 10 pages return HTTP 200, not 301 chains or 5xx errors.
- SSL padlock shows on every page, no mixed-content warnings in the browser console.
- Forms submit and the resulting emails arrive (check spam too).
- Checkout completes end-to-end if you run ecommerce.
- WordPress admin login works, plugins are active, scheduled posts are queued.
- Search Console and Analytics still receive data within 48 hours.
- Email arrives at and sends from your domain (MX, SPF, DKIM all valid via mxtoolbox).
- The old host is still running for at least 7 days as a fallback.
Migrating WooCommerce to Hostinger
WooCommerce migrations need three extra steps that a plain WordPress migration does not. First, freeze new orders during the cut-over window by enabling maintenance mode or putting the store in catalog-only mode for an hour. WooCommerce sessions and pending orders live in the database, and a migration mid-checkout corrupts orders. Second, re-authenticate your payment gateways after the site lands. Stripe, PayPal, and Authorize.net all key webhooks to the domain, but some gateways tie their API connections to the previous server's IP and need a manual reconnect from the WooCommerce settings panel. Third, run a transient cache flush (wp-cli transient delete --all or a plugin like WP-Optimize) because cached price calculations and shipping rates can hold stale data from the old host.
Allow an extra 24 hours of overlap before you cancel the old WooCommerce hosting. Order webhooks from Stripe and PayPal sometimes retry against the old domain for up to 24 hours after DNS flips.
Performance Quick-Wins After Migration
Hostinger runs LiteSpeed Web Server, which means you get full-page caching that beats most WordPress cache plugins. Three tweaks deliver most of the speed win without paid extensions.
- Install the LiteSpeed Cache plugin. Activate the default preset and turn on Object Cache via Memcached or Redis in the LiteSpeed settings. This alone usually cuts TTFB by 60 to 80%.
- Enable hPanel's PHP OPcache. Go to Advanced > PHP Configuration and confirm OPcache is on for PHP 8.2 or 8.3. It is off on some legacy accounts.
- Turn on the Hostinger CDN. Available on Business and Cloud plans, accessed from Websites > Performance > CDN. This serves static assets from a Cloudflare-backed edge so visitors do not hit your origin for every page load.
Measure before and after with GTmetrix or Lighthouse so you have a real baseline. If TTFB stays above 500 ms after these three changes, the issue is usually a database query in a slow plugin, not the host.
Rolling Back If Something Breaks
You did the insurance backup in Step 3 for exactly this scenario. If you discover a broken migration after DNS has flipped (corrupt data, missing posts, broken checkout), the rollback path is: change DNS A record back to your old host's IP (TTL is already low because you set it to 300 in Step 6), restore the UpdraftPlus archive to the old host to undo any changes that happened during the migration window, and let propagation reverse. Most rollbacks complete inside 30 minutes if your old host is still active.
If the old host is already cancelled, restore the UpdraftPlus archive directly onto Hostinger and treat Hostinger as the new primary. The decision to roll back or fix forward depends on how many real visitors and orders happened during the bad window; under 50 orders or zero forms submitted usually means roll back, more than that usually means fix forward.
Hostinger Plan Tiers: What to Budget
Intro pricing is one number, real ongoing pricing is another. Plan for the renewal:
- Premium: Single site, 100 GB SSD, weekly backups. Renews around $8 to $11 per month after intro. Skip if you need staging or daily backups.
- Business: 100 sites, 200 GB NVMe, daily backups, staging, free CDN, free email. This is the floor for serious migrations. Renews around $11 to $14 per month after intro.
- Cloud Startup: Dedicated resources (3 CPU, 3 GB RAM), 200 GB NVMe, priority support. Renews around $20 to $30 per month after intro. Worth it once you cross ~20k monthly visits.
- Cloud Professional: 6 CPU, 6 GB RAM. Renews around $40 to $50 per month after intro. Compete-with-VPS territory.
If you outgrow Cloud Professional, the next jump is a Hostinger VPS or a managed cloud platform. The Cloudways setup and migration guide covers what migrating up to a managed cloud host looks like if shared hosting starts to feel cramped.
Common Migration Errors and Fixes
These are the failures real migrations hit. Skim before you start so the symptoms ring a bell when they show up.
- Migration stuck at "Importing database" for over two hours. Usually a large WooCommerce or membership database with bloated wp_options or wp_postmeta. Cancel the run, delete transients and expired sessions on the source, retry.
- White screen after migration. A plugin incompatibility with the new PHP version. Rename the /wp-content/plugins folder via SFTP to disable everything, log in, and re-enable plugins one at a time.
- Login redirect loop. Mixed-content rewrite issue. Check that wp-config.php has the right WP_HOME and WP_SITEURL, and run a search-replace from http:// to https:// across the database.
- Mixed content warnings. Old absolute HTTP URLs hard-coded in posts or theme files. Run Better Search Replace to convert http:// references to https://.
- Email stopped after DNS flip. MX or SPF records not copied to the Hostinger DNS zone. Re-add them under hPanel > DNS > Manage and wait one propagation cycle.
- Search rankings dropped. Usually a broken redirect map or missing /sitemap.xml. Re-submit your sitemap in Search Console, run a 404 check with Screaming Frog, and verify your canonical tags.
Most of these are five-minute fixes once you know what to look for. The deeper symptom-by-symptom troubleshooting lives in the dedicated WordPress migration how-to, and account-level fixes belong in the how to set up Hostinger walkthrough.
