A website migration request to Hostinger may not be completed for several reasons. These usually require action on your side before the migration can be processed successfully.
Migration is only available when moving your website from another hosting provider to Hostinger. Websites already hosted at Hostinger are not eligible for this process. If this is the case, you don’t need to submit or edit a request. Instead, you can manually move your website to another hosting plan or Hostinger account.
Common issues
If your migration request was marked as Rejected, check the message left by the migration team. Below are the most common reasons why a request cannot be completed, and how to fix them:
|
Issue |
Solution |
|
Incorrect login details |
Double-check that the website login URL and credentials (admin username and password) are correct. |
|
Two-factor authentication is enabled on your previous provider |
Temporarily disable 2FA on your previous hosting provider until the migration is complete. |
|
Domain is already pointing to Hostinger |
Update your domain’s nameservers or IP address to match your previous hosting provider’s records, then wait for for DNS propagation. |
|
Insufficient disk space to create backups |
Remove unnecessary files from your previous hosting account, or upload your backup to a file-sharing service (Google Drive, Dropbox, etc.). |
|
Failed to install a plugin |
Check the error with your previous hosting provider and fix it before retrying the migration. |
|
An issue with the backup provided |
Make sure your backup includes all website files and the database. Re-upload the full backup in a supported format (.tar.gz, .zip, .rar, .tar for files, and .sql for the database). |
|
Unsupported CMS |
Websites built on unsupported platforms or technologies (e.g., sites created with proprietary builders from other providers, custom-built sites only supported on VPS) cannot be migrated automatically. You will need to migrate manually or rebuild your website. |
|
Account Suspended |
Restore access to your old hosting account or prepare a complete backup (files and database). |
|
The domain has already expired |
Renew your domain with your old provider, or use a complete backup (files and database). |
|
Multisite |
WordPress multisite migrations are not supported through our migration service. You can still host a multisite at Hostinger and migrate your content by setting up WordPress Multisite yourself and restoring your website from a backup. |
|
Custom URL for wp-admin |
If your WordPress login page uses a custom URL, ensure you provide it as the login link. Alternatively, use a complete backup (files and database). |
|
The database size is too big for the plan |
Reduce the size of your database by optimizing it. |
|
Old hosting only has an FTP feature |
FTP-only migrations are not supported. Prepare a complete backup (files and database) instead. |
|
Uncompressed files (SFTP/FTP) |
Compress your website files and database into a single archive (.tar.gz, .zip, .rar, .tar) to avoid missing data. |
|
Domain source not found |
Verify the source domain details are correct. |
|
Server connection closed |
Contact your previous provider to ensure the server is accessible and backups can be created. |
Once the issue is resolved:
- If the fix implied correcting details (such as login credentials, DNS, or server access), you can create a new migration request with the updated information.
- If you were submitting CMS credentials (e.g., WordPress login) and that method is not possible, you can instead provide your hosting control panel credentials (cPanel/other panel). Likewise, if hosting credentials are not available, try using CMS credentials.
- If neither method works, download a full backup of your website (files and database) and create a new migration request using the Upload backup files option.