How To Migrate My Website From Hostinger
A Hostinger migration may start from WordPress admin, hPanel file and database access, FTP/SFTP, SSH on supported plans, or a hosted builder export. Identify the application and source folder first, then choose the route that can move the real website data without depending on the domain already pointing to the destination.
Inventory The Hostinger Account
- Record the site type, detected version, document root, database name, PHP or application runtime, and total file and database size.
- Check for additional domains, subdomains, staging sites, cron jobs, redirects, and files outside the public directory.
- List email accounts, forwarders, aliases, mailbox sizes, and current MX provider separately from the website.
- Confirm whether a CDN, WAF, object cache, or origin restriction must be adjusted during the move.
WordPress And PHP Applications
For WordPress, install the source agent through wp-admin or use file and database credentials. For Laravel, Joomla, PrestaShop, OpenCart, or another PHP application, include configuration files, writable storage, cron, queues, and the exact PHP extensions required. Do not upgrade the application or PHP version in the same step unless the upgrade has its own tested rollback plan.
Destination And Preview Testing
Create the destination document root and database, then test with a temporary hostname or hosts-file override. Check admin login, public routes, media, forms, ecommerce, redirects, scheduled tasks, and error logs. If the final domain changes, use application-aware URL and configuration updates rather than a blind database replacement.
Email Is A Separate Migration
When Hostinger mail is also moving, create destination mailboxes first, copy messages through the supported IMAP or provider route, reconcile folders and counts, and run a final delta. Change MX only after destination send and receive tests pass. Preserve SPF, DKIM, and DMARC values appropriate to the new sender.
Cutover
Run a final sync for changing data, update the web DNS records, verify TLS, purge destination and CDN caches, and watch logs after traffic arrives. Keep the source account available through the acceptance window. The server-to-server migration guide explains the direct transfer model, and the post-migration checklist covers production checks.