How to migrate website to Hostinger on Hostinger
Manually migrate by backing up files and database from source hPanel, adding the website to destination plan, uploading/extracting files to public_html, creating/importing new database, and updating config files. Plan for downtime and test on a temporary domain. Allow time for DNS propagation if changing domains.
Prerequisites
- Backup of source website files in .tar.gz format via File Manager
- Exported source database .sql file via phpMyAdmin
- Source database name, username, and password details
- Access to hPanel on both source and destination accounts
- Temporary domain for testing post-migration
Step-by-Step Instructions
Backup Source Website Files
.tar.gz backup, and download it. Use FTP as alternative for large sites.Backup Source Database
.sql file. Record database name, username, and password.Access Destination Hosting Plan
Add Website to Destination Plan
Upload and Extract Files
.tar.gz backup. Right-click uploaded file → Extract to folder like backup, then move contents from backup/domains/[domain]/public_html to root /public_html. Delete temporary files.Create New Database
name (e.g., u123456789_dbname), username, generate strong password, and store securely.Import Database
.sql file, and execute with default UTF-8 charset.Update Configuration File
public_html, edit site config file (e.g., wp-config.php) to replace old database name, username, and password with new ones. Save changes.Test and Point Domain
Common Issues & Troubleshooting
Incorrect nameserver pointing causing migration access failure
Revert domain nameservers to previous provider, wait 24 hours for DNS propagation, then resubmit.
Login or 404/503 errors in WordPress admin
Verify admin URL loads on old host, confirm credentials, temporarily disable 2FA.
Upload or extraction fails in File Manager
Use .tar.gz or .zip format, check file size limits, try FTP for large backups.
Database import errors
Confirm UTF-8 charset, create database/user with ALL privileges, check size limits.
Site not loading after migration
Clear browser/Hostinger cache, verify config file DB details, check file permissions.