Transparency: This article contains affiliate links. If you buy through them, we may earn a commission at no extra cost to you. Our recommendations are based on real experience and value for Portuguese businesses.
How to migrate your WordPress site to Hostinger: free professional migration (24-48h), mannual plugin or FTP. Pbooks SEO, 301 redirects.
Table of Contents(20 sections)
- Method 1: Free Hostinger Migration
- Method 2: Mannual with All-in-One WP Migration
- Pbook SEO After Migration
- Advanced Tips
- Common Mistakes to Avoid
- FAQ
- Related Hostinger Guides
- Technical Deep-Dive: Metrics That Really Matter
- Real-World Use Cases
- Common Mistakes That Sink Sites in SEO
- Advanced Technical Questions Answered
- Legal and Compliance Aspects
- Zero-SEO-Loss Migration Checklist
- Free Tools You Should Use on Any Site
- How to Optimize Performance on Any Site
- Advanced Hosting Metrics
- Advanced Technical Decisions
- Common Technical Mistakes Degrading Performance
- Advanced Migration Scenarios and Edge Cases
- FAQ: Advanced Migration Scenarios
Migrating your WordPress site to Hostinger is simpler than it seems. Hostinger does free professional migration in 24-48h. Alternatively, you can migrate mannually with plugins. This guide covers both methods with SEO preservation.
Hostinger
Fast WordPress hosting with LiteSpeed, free SSL, free domain and 24/7 support — plans from €2.49/mo.
- LiteSpeed Enterprise cache
- Free SSL & CDN
- Free domain for 1 year
- Daily automatic backups
- 24/7 support in English
- 30-day money-back guarantee
Instant activation · 30-day money-back
4,6/5 · 73k+ reviews
Method 1: Free Hostinger Migration
- In hPanel → Websites → Request Migration
- Fill form: current site URL, old hosting credentials, destination domain
- Submit — migration team confirms in 1-2h
- Complete in 24-48h
Advantages
- Zero technical risk — experienced team
- Free
- Pbooks URLs and structure
- Support during entire process
Method 2: Mannual with All-in-One WP Migration
On Old Site
- Install “All-in-One WP Migration” plugin
- Menu → Export → Export To File
- Download .wpress file
On New Hostinger Site
- Install WordPress on Hostinger
- Install same plugin
- Menu → Import → File → select .wpress
- Wait 5-15 minutes
Free limit: 500MB. For larger sites use Google Drive extension or FTP method.
Hostinger
Fast WordPress hosting with LiteSpeed, free SSL, free domain and 24/7 support — plans from €2.49/mo.
- LiteSpeed Enterprise cache
- Free SSL & CDN
- Free domain for 1 year
- Daily automatic backups
- 24/7 support in English
- 30-day money-back guarantee
Instant activation · 30-day money-back
4,6/5 · 73k+ reviews
Pbook SEO After Migration
1. 301 Redirects
If URLs changed, configure 301 redirects in .htaccess.
2. Update DNS
Point domain to Hostinger nameservers: ns1.dns-parking.com, ns2.dns-parking.com. Propagation: 1-48h.
3. Google Search Console
- Submit updated sitemap
- Request indexing of main URLs
- Monitor crawl errors for 2-4 weeks
4. Complete Test
- All main pages open?
- Forms submit?
- Images appear?
- Internal links work?
- Core Web Vitals maintained?
Advanced Tips
Cache Optimization
Hostinger includes LiteSpeed Enterprise on all Business+ plans and the free LiteSpeed Cache plugin for WordPress. After install, enable in WordPress admin → LiteSpeed Cache → “Enable Cache” with recommended settings.
Free CDN
On Business+ plans, Hostinger includes accelerated CDN. Enable in hPanel → Websites → CDN → Enable. Typical impact: 20-40% faster loading for international visitors.
Performance Monitoring
After setup, regularly measure with PageSpeed Insights, GTmetrix and Google Search Console. Core Web Vitals should all be green (LCP < 2.5s, INP < 200ms, CLS < 0.1).
Security
Hostinger includes Imunify360 (web application firewall) on Business+ plans. Additionally install a WordPress plugin like Wordfence or Solid Security.
Common Mistakes to Avoid
- Forgetting personal backups — Hostinger does automatic backups but also have offsite backup
- Not enabling LiteSpeed Cache — plugin must be mannually installed
- Installing too many plugins — maximum 15 active plugins
- Ignoring updates — WordPress core + themes + plugins should be updated weekly
- Using obscure themes — prefer Astra, Kadence, GeneratePress
Need to migrate your site to Hostinger without losing SEO? See our Zero-Downtime Migration service starting from €450+VAT.
FAQ
Can I cancel if I don’t like it?
Yes. Hostinger has 30-day no-questions money-back. Request via chat, refund processed in 5-10 days.
Do I need technical knowledge?
For shared plans: no. hPanel interface is visual, 1-click. For VPS: yes, requires Linux commands.
Does support work in multiple languages?
Yes, 24/7 chat support including Portuguese. Response in 2-5 minutes for common questions.
Can I migrate my current site?
Yes, free. Hostinger does professional migration in 24-48h. Alternative: “All-in-One WP Migration” plugin.
Grow Your Business with SEO
+12 years of SEO in Portugal. Free proposal in 24h. Guaranteed results in 90 days.
Related Hostinger Guides
Deepen your knowledge with our other Hostinger guides:
Install WordPress on Hostinger
Complete setup in 5 minutes.
hPanel Guide
All control panel features.
Hostinger Backup
Automatic + mannual + offsite.
Migrate WordPress to Hostinger
Free, zero downtime, SEO pbookd.
Online Store with WooCommerce
Payments + performance.
Hostinger Plans
Which to choose for your project.
Technical Deep-Dive: Metrics That Really Matter
TTFB (Time to First Byte)
TTFB measures how long the server takes to respond with the first byte. It’s one of the most critical SEO indicators because it directly affects LCP (Largest Contentful Paint), one of Google’s Core Web Vitals. TTFB below 200ms is excellent; above 600ms is problematic.
Hostinger, with LiteSpeed Enterprise + NVMe SSD, consistently delivers TTFB between 120ms and 180ms in real client tests. Traditional shared hosting without LiteSpeed typically runs 400-700ms — the difference is visible to both users and Google’s algorithm.
Core Web Vitals
Google’s Core Web Vitals evaluate three metrics: LCP (visual loading speed), INP (interactivity) and CLS (layout stability). Sites that pass all three gain significant ranking advantage, especially on mobile. Good hosting is the foundation — no amount of code optimization can save you without it.
Real vs Promised Uptime
99.9% uptime sounds impressive but translates to 8.76 hours of downtime per year. 99.99% (four nines) means only 52 minutes/year. Serious providers like Hostinger document average uptime above 99.95% with 99.9% guaranteed SLA.
I/O Latency and Disk Speed
NVMe SSDs deliver 50-100 microsecond latencies vs 200-500 microseconds for traditional SATA SSDs. For WooCommerce with many database queries, this translates to pages 2-3x faster in real-world scenarios.
Real-World Use Cases
Personal Blog or Portfolio
For a personal blog or professional portfolio with 1,000-10,000 monthly visits, Hostinger Premium (€2.49/mo) is more than enough. 100 GB SSD, LiteSpeed cache, free domain in year 1, automatic SSL. Setup: 1-click WordPress install, lightweight theme (Astra, Kadence, GeneratePress), LiteSpeed Cache plugin, Yoast SEO. Result: fast site, solid SEO, total annual cost under €60.
SME Corporate Site
A small-to-medium business with institutional site, 5-10 pages, contact form and occasional blog. Volume: 5,000-30,000 monthly visits, mostly from local Google searches. Recommended: Hostinger Business (€3.99/mo). Advantages: automatic daily backups (critical for commercial sites), professional email included, more resources for image-heavy pages. Typical setup time: 4-8 hours including migration.
Small Online Store (up to 100 products)
WooCommerce with 50-100 products, 10k-50k visits/month, seasonal peaks. Hostinger Business handles this with proper optimization: LiteSpeed Cache configured for e-commerce, WebP images, lazy loading, CDN active. For peaks above 50k visits/month, upgrade to Cloud Startup.
Medium Online Store (500+ products)
Extensive catalog, active marketing campaigns, peaks of 100k+ visits/month. Hostinger Cloud Startup (€7.99/mo) or Cloud Professional delivers dedicated resources (CPU, RAM, IP) unaffected by other clients. Critical advantage: resource isolation during Black Friday peaks or aggressive Meta Ads campaigns.
Common Mistakes That Sink Sites in SEO
- Hosting without cache: Serving pages without cache means every visitor forces the server to generate HTML from scratch. With cache (LiteSpeed, Varnish, Redis), pages are served in milliseconds from memory.
- Outdated PHP: Sites running PHP 7.4 or lower are 30-50% slower than PHP 8.1+. Additionally, old versions stop receiving security updates, making the site vulnerable.
- Bad shared-hosting neighbors: On cheap shared hosting, you may share servers with spam, phishing or abnormally high-traffic sites. The shared IP can affect email delivery and ranking.
- Wrong geographic location: Hosting on Asian or American servers for a Portuguese or European audience adds 100-300ms latency. European servers (Portugal, Spain, Germany, Netherlands) are the minimum standard.
- Ignoring backups: Automatic daily backups are the minimum essential. Weekly is insufficient for e-commerce or regularly updated sites.
Advanced Technical Questions Answered
What is LiteSpeed and why does it matter?
LiteSpeed is an alternative web server to Apache/NGINX, specifically optimized for performance. Serves static pages 3-10x faster than Apache. Combined with the free LiteSpeed Cache plugin for WordPress, it delivers full-page caching, automatic CSS/JS/image optimization and QUIC/HTTP3 support. It’s the “secret” behind the best performance in shared hosting.
SSD vs NVMe vs HDD: What’s the difference?
HDDs are obsolete for web (10-20ms latencies). Traditional SATA SSDs deliver 100-200 microseconds. NVMe SSDs (like Hostinger’s) drop to 50-100 microseconds — 3-4x faster. For WooCommerce with heavy SQL queries, the difference is enormous.
CDN: Do I need one?
For visitors exclusively in Portugal or a single European country, a good European server doesn’t need a CDN. For international audiences (EN, DE, FR, US), CDN is mandatory. Options: Cloudflare (excellent free plan), BunnyCDN (from $1/mo), Hostinger CDN (included in Business+ plans).
HTTP/3 and QUIC: Why are they important?
HTTP/3 (over QUIC) is the latest web protocol. Reduces handshake latency, handles packet loss better (critical on mobile) and improves performance on mobile networks. LiteSpeed supports it natively — another technical advantage.
Backups: daily, weekly or real-time?
For most sites, automatic daily backups are the essential minimum. For e-commerce or critical applications, real-time (or hourly incremental) is preferable. Always check that the provider stores backups in a different physical location (offsite) for hardware failure protection.
Legal and Compliance Aspects
GDPR and Data Location
For sites targeting Portugal or Europe, GDPR requires transparency about where user data is stored. Hosting with EU datacenters (Portugal, Spain, Germany, Netherlands, Lithuania for Hostinger) is within the GDPR space without additional complications. US-only providers may require Standard Contractual Clauses (SCC) and additional documentation.
Cookies and Tracking
Regardless of hosting, your site must have a GDPR + ePrivacy-compliant cookie policy. For WordPress, plugins like Complianz or CookieYes handle the essentials in 15-30 minutes of configuration.
Professional Email and DMARC/SPF/DKIM
Hosting with email requires correct configuration of SPF (identifies authorized sending servers), DKIM (cryptographic signature) and DMARC (recipient protection policy). Without this, emails land in spam. Hostinger configures these automatically but it’s worth validating via MXToolbox.
Zero-SEO-Loss Migration Checklist
- Full backup of current site (files + database)
- Snapshot current rankings in Google Search Console
- Export current URL structure
- Staging migration (not direct to production)
- Test all main pages and forms
- Verify 301 redirects for any URLs that change
- Update DNS (lower TTL 24h before)
- Monitor GSC for 2-4 weeks post-migration
- Submit updated sitemap to Google
- Reindex critical URLs via GSC
For SEO-critical migrations where rankings are at stake, consider our professional SEO migration service — we guarantee zero ranking loss.
Free Tools You Should Use on Any Site
Beyond hosting, there are free tools every professional site should have configured from day 1. These make the difference between a stagnant site and one that grows consistently.
Performance Monitoring
- Google PageSpeed Insights — measures Core Web Vitals in real conditions. Monthly benchmark.
- GTmetrix — detailed waterfall, TTFB per resource. 5 free tests/day.
- WebPageTest — tests from multiple locations.
- UptimeRobot — 24/7 monitoring with email/SMS alerts. 50 free monitors.
- Lighthouse (Chrome DevTools) — complete audit of performance, accessibility, SEO, PWA.
SEO
- Google Search Console — most important tool. Submit sitemap, see queries, impressions, CTR, crawl errors, Core Web Vitals.
- Google Analytics 4 — traffic, origin, behavior, conversions.
- Bing Webmaster Tools — equivalent to GSC for Bing + IndexNow sync.
- Yoast SEO or Rank Math — meta tags, schema, automatic sitemaps.
Security
- Wordfence Security — firewall + malware scanning for WordPress.
- Sucuri SiteCheck — external scan to verify blacklist status.
- Mozilla Observatory — security headers audit (HSTS, CSP).
How to Optimize Performance on Any Site
These 10 optimizations improve Core Web Vitals on any site, regardless of hosting:
- Convert images to WebP — up to 70% lighter than JPG
- Image lazy loading — HTML5 native (
loading="lazy") or plugin - Minify CSS/JS — remove whitespace, comments
- Combine CSS/JS — fewer HTTP requests. Careful: may break HTTP/2
- Preload critical resources — fonts, hero image, above-the-fold CSS
- CDN for static assets — free Cloudflare suffices for most
- WOFF2 subset fonts — load only used glyphs
- Database cleanup — WP-Optimize for revisions, spam, transients
- Reduce plugins — max 15 active
- HTTP/3 (QUIC) — automatic on modern LiteSpeed/Cloudflare servers
Advanced Hosting Metrics
- OPcache hit rate — must be >95%
- Object cache hit rate (Redis/Memcached) — target >90% for WooCommerce
- Database query count per page — <50 on homepage, <100 on listing
- Memory peak per page — <64MB for typical WordPress, <256MB for complex WooCommerce
- CPU per request — <100ms on cached pages
Advanced Technical Decisions
PHP-FPM vs mod_php
PHP-FPM is 20-40% more memory-efficient. Standard in modern professional hosting. Hostinger uses PHP-FPM on all plans.
HTTP/2 vs HTTP/3
HTTP/2 suffices for 95% of cases. HTTP/3 (QUIC) wins on mobile networks and with packet loss.
Redis vs Memcached
Redis is more versatile (persistent, data structures). Memcached simpler and faster for pure caching. For WordPress/WooCommerce, Redis is the modern choice.
Common Technical Mistakes Degrading Performance
- Poorly optimized plugins (Elementor + WPBakery)
- Unoptimized images (20MB images don’t scale)
- External scripts without async (Google Fonts, Analytics, Facebook Pixel block render)
- Database with thousands of post revisions
- Shared hosting with thousands of sites per server
- Slow DNS (above 100ms response adds 300-500ms per new visit)
Advanced Migration Scenarios and Edge Cases
Beyond standard WordPress migrations, specific scenarios require specialized approaches. Here are the complete playbooks for complex migration cases.
Scenario 1: Multisite Network Migration
WordPress Multisite migrations are substantially more complex than single-site:
Pre-Migration Checklist
- Document all sites in network with URLs and purposes
- Note which sites use subdomains vs subdirectories
- Backup database (contains metadata for all sites)
- Document plugins activated network-wide vs per-site
- Identify shared uploads vs per-site uploads
Migration Steps
- Full backup of entire network via UpdraftPlus with multisite add-on
- Transfer all files to new Hostinger hosting
- Transfer complete database
- Update wp-config.php with new DB credentials AND multisite constants:
define('MULTISITE', true); define('SUBDOMAIN_INSTALL', false); // true if subdomains define('DOMAIN_CURRENT_SITE', 'newdomain.com'); define('PATH_CURRENT_SITE', '/'); define('SITE_ID_CURRENT_SITE', 1); define('BLOG_ID_CURRENT_SITE', 1); - Update .htaccess for multisite routing
- If domain changed: WP-CLI mass search-replace on all tables:
wp search-replace 'olddomain.com' 'newdomain.com' --network --skip-columns=guid - Test each site individually
- Verify network admin accessible
- Verify user accounts across all sites
Common Multisite Migration Issues
- Table prefix mismatches between sites
- Media not loading on some sites
- User roles different across sites
- Theme not activated on specific sites
- Mapped domains need reconfiguration
Scenario 2: WooCommerce Store Migration
E-commerce migrations have highest stakes — downtime equals lost revenue:
Timing Strategy
- Choose lowest-traffic window (typically Tuesday 2-6 AM for most Portuguese stores)
- Place maintenance mode banner 48 hours before
- Freeze new order processing 2 hours before migration
- Communicate with customers via email about expected downtime
- Have social media ready to update if issues arise
WooCommerce-Specific Steps
- Complete order freeze: process all pending orders first
- Export orders CSV from Analytics as backup
- Note current stock levels (reconcile post-migration)
- Document payment gateway settings (API keys, webhooks)
- Full backup including WooCommerce tables (wp_wc_orders, wp_wc_customer_lookup, etc.)
- Transfer all files and database
- Update payment gateway webhook URLs
- Reconnect Stripe, PayPal with new domain if applicable
- Test complete purchase flow (small amount through all gateways)
- Verify emails send (order confirmations, shipping notifications)
- Test refund flow
- Verify analytics tracking (purchases register correctly)
- Update Google Shopping, Facebook Catalog feeds if applicable
Post-Migration Verification
- Place test order (actual purchase, small value)
- Verify payment captured correctly
- Verify order email sent
- Verify stock decremented
- Verify analytics tracked
- Refund test order
- Verify refund processed
- Lift maintenance mode
Scenario 3: Membership/LMS Site Migration
Member-based sites require extra care:
- User passwords are hashed — survive migration if database transferred correctly
- Membership expiry dates in meta tables
- Course progress data (LMS)
- Download logs
- Subscription payment integrations (Stripe recurring, PayPal subscriptions)
Critical Steps
- Export user list with all metadata before migration
- Document all active subscriptions and renewal dates
- Note integrations with payment processors
- Transfer all member-related tables
- Verify login works for sample users post-migration
- Verify subscription processors can webhook new URL
- Test content access rights (members see members-only content)
- Test course progression (LMS)
- Email users about migration confirmation
Scenario 4: High-Traffic Site Migration (100k+ monthly visits)
Standard migration approaches don’t scale well. Consider:
Blue-Green Deployment
- Set up complete new environment on Hostinger (blue)
- Keep old environment running (green)
- Replicate database changes with real-time sync
- DNS cutover with low TTL (300 seconds)
- Monitor new environment for 24 hours
- Keep old environment as rollback option
Database Streaming Replication
For databases over 10GB:
- mysqldump may timeout; use pt-dump instead
- Consider logical replication
- Transfer in chunks: structure first, data by table
- Verify row counts match post-transfer
CDN Pre-warming
- Set up CDN on new host before cutover
- Pre-cache critical pages
- Prime CDN with crawler
- Verify cache hit rate before cutover
Scenario 5: Legacy Site Migration
Sites running old WordPress (3.x, 4.x) or deprecated themes:
Pre-Migration Preparation
- Upgrade WordPress to latest 4.x version first (avoid skipping major versions)
- Update theme to latest version if available
- Update plugins
- Fix any PHP deprecation warnings
- Test site functionality after each update
- Only after stable, migrate to Hostinger with modern PHP (8.1+)
Common Legacy Issues
- PHP 5.6 code fails on PHP 7+ (deprecated functions)
- Short tags <? instead of <?php
- Mysql_* functions (deprecated in favor of mysqli_)
- Create_function (removed in PHP 7.2+)
- Each: iterate on PHP 7+ requires foreach
Scenario 6: Database Charset Mismatch
Common cause of broken characters (is, ç, á appearing as question marks):
Diagnosis
- Original DB may be latin1 or utf8
- New hosting may expect utf8mb4
- Mismatch causes character corruption
Fix
- Dump original DB maintaining charset
- Convert dump file:
iconv -f latin1 -t utf8 old.sql > new.sql - Import to new DB
- Update wp-config.php with correct charset
- If broken characters remain: wp-cli find/replace with specific patterns
Scenario 7: Migration from Non-WordPress Platform
Moving from Wix, Squarespace, the leading international e-commerce SaaS platform, Joomla, Drupal:
Content Migration Options
- Mannual copy-paste (for small sites, < 20 pages)
- Export from source (if provided — Wix doesn’t export cleanly)
- Automated tools: cms2cms, FG WordPress Import
- Custom scripts for complex sites
What Doesn’t Transfer Automatically
- Theme and design (must rebuild in WordPress)
- Custom functionality (needs plugins or custom code)
- Form submissions and user data
- E-commerce catalog (specific per-platform)
- Blog comments (may need mannual export/import)
Essential: URL Mapping
Different platforms have different URL structures. Create comprehensive mapping:
- /products/widget.html → /loja/widget/
- /blog/2024/01/post-slug.html → /blog/post-slug/
- Implement 301 redirects for every URL
- Monitor Google Search Console for 404s
Scenario 8: Partial Migration (Keep Some Features on Old Site)
Sometimes you want to migrate only parts:
Hybrid Approaches
- Blog on WordPress, store on the leading international e-commerce SaaS platform: subdomain approach (blog.yoursite.com)
- Main site on WordPress, legacy app on old server: subdirectory routing (yoursite.com/app/)
- Content on WordPress, docs on separate platform: domain routing
Technical Considerations
- Shared headers/footers via includes (iframes avoided)
- Consistent branding across platforms
- Single Sign-On if membership shared
- Unified analytics tracking
- Linked content strategy
Scenario 9: International Multi-Region Migration
Sites serving multiple regions with hreflang:
- Pbook all language versions during migration
- Verify hreflang tags still correct post-migration
- Google Search Console: separate properties per language version
- Consider CDN with regional caching
- Verify currency displays correctly
- Test checkout from different geographic IPs
Rollback Strategy
Always prepare for migration failure:
24-48 Hours Pre-Migration
- Reduce DNS TTL to 300 seconds (easier rollback)
- Full backup of current site
- Document current state (screenshots, metrics)
- Maintain old hosting for 30 days after migration (safety net)
Rollback Trigger Points
- Site completely broken 2+ hours into migration
- Critical functionality (checkout) non-functional
- Data loss discovered
- Performance 50%+ worse than baseline
- Major SEO drop (if visible immediately)
Rollback Execution
- Revert DNS to old hosting
- DNS propagation 15 min to 2 hours
- Communicate with users via status page
- Investigate issues in staging
- Re-attempt migration when issues resolved
Zero-Downtime Migration Technique
For truly critical sites:
- Set up new environment on Hostinger (identical configuration)
- Set up database replication from old to new
- Keep both environments in sync for days/weeks
- Switch DNS when confident
- Decommission old environment weeks later
Complexity high but risk negligible. Appropriate for mission-critical e-commerce.
Post-Migration SEO Recovery
Even perfectly executed migrations may dip 10-20% traffic for 2-4 weeks:
Acceleration Techniques
- Submit new sitemap to Search Console immediately
- Request indexing of key pages mannually
- Monitor for crawl errors daily
- Fix broken redirects immediately
- Update backlinks if possible (reach out to referring sites)
- Internal linking: ensure all pages have good internal links
- Fresh content: publish new content signaling site is active
- Technical: Core Web Vitals must be excellent (not just good)
FAQ: Advanced Migration Scenarios
What’s the biggest migration risk?
Data loss. Always have multiple backup verifications before touching anything. Even then, assume something will go wrong and plan accordingly.
Should I hire a professional for migration?
For simple sites under 50 pages: DIY feasible if technical. For e-commerce, multisite, or sites generating >€1000/month revenue: professional migration is cheap insurance (€500-2000 for peace of mind).
How to prove migration was clean?
Compare pre and post metrics: traffic (Analytics), rankings (Search Console), performance (PageSpeed), functionality (mannual testing), content integrity (random spot checks).
Can Hostinger support help with migration?
Yes, Hostinger offers 1 free migration per account. Technically competent for simple sites. For complex projects, their service may need coordination with your shouldloper.