How to Migrate a Website to Hostinger in 2026

Thinking about moving your website from your current hosting provider to Hostinger? Whether you run a WordPress blog, a business website, or a custom PHP application, you can transfer your website to a new hosting account without rebuilding everything from scratch.

Website migration involves moving your website files and databases, configuring the new hosting environment, and pointing your domain to the new server. The process needs to be handled carefully because changing your domain too early can cause downtime or interrupt access to your website.

Hostinger offers an assisted website migration service for eligible websites, as well as options for manually transferring website files and databases. This guide explains both approaches and shows you how to prepare, migrate, and test your website before switching your domain.

1. What Does It Mean to Migrate a Website to Hostinger?

Website migration means transferring an existing website from one hosting provider or platform to another. For example, if your website currently runs on Bluehost, GoDaddy, SiteGround, or another hosting service, you can move its supported files and database to Hostinger.

A typical migration involves transferring several components:

• Website files: HTML, CSS, JavaScript, PHP, images, themes, plugins, and other website files.
• Database: Posts, pages, user accounts, product information, settings, and other stored data.
• Website configuration: Database connection details, application settings, and other environment-specific information.
• Domain settings: DNS records that direct visitors to the new hosting server.
• Email services: Mailboxes and email data associated with your domain, which usually need a separate migration.

The exact process depends on your website platform. A WordPress website has different migration requirements from a simple HTML website or a custom PHP application.

2. What to Do Before Migrating Your Website

Preparation is one of the most important parts of website migration. Before requesting a transfer or moving files manually, check the following requirements.

1. Purchase an appropriate Hostinger hosting plan

You need an active hosting plan that supports your website's technology and has enough storage and resources for your website.

Hostinger's assisted migration eligibility currently covers eligible Web, Cloud, and Agency hosting plans. VPS hosting is not included in the free assisted migration offer described in its migration documentation.

2. Check your current hosting access

Make sure you can access your existing hosting account, website administration dashboard, and website files. Depending on the migration method, Hostinger may request WordPress administrator or cPanel credentials.

3. Create a complete backup

Before making changes, download a copy of your website files and export its database. Store the backup on your computer or another secure location.

A backup gives you a recovery option if the migration fails or some content is missing.

4. Check available hosting resources

Review the size of your website, database, and expected resource usage. Your new hosting plan must have sufficient resources to run the website properly.

5. Review security settings

Hostinger recommends disabling two-factor authentication and anti-bot verification on the current hosting account or website administration page when these protections prevent its migration process from accessing the website. Only do this when necessary, and restore the protections after migration.

3. Choose the Right Website Migration Method

Hostinger provides different migration options depending on whether your website is online, whether you have a backup, and which platform you use.

Which websites qualify for free assisted migration?

Hostinger's current migration documentation lists eligibility requirements for its free assisted migration service. These include:

• The website must currently be hosted with a provider other than Hostinger.
• The website must use an eligible open-source CMS, such as WordPress.org or Joomla, for the relevant assisted migration offer.
• The destination hosting plan must have enough resources.
• The website must comply with Hostinger's terms and hosting agreement.
• The destination plan must be an eligible Web, Cloud, or Agency plan.

Websites created with proprietary website builders such as Shopify, Squarespace, Canva, Google Sites, Blogger, or GoDaddy Website Builder cannot be transferred through the same assisted migration method. They may need to be recreated on a supported platform or migrated using a different approach where possible.

4. How to Migrate a Website Using Hostinger's Migration Service

Hostinger's assisted migration service is a convenient option for eligible websites because its migration team handles the transfer after you submit the required information.

5. How to Migrate a WordPress Website to Hostinger

WordPress is one of the common platforms supported by Hostinger's assisted migration service. If your website is a self-hosted, single-site WordPress installation and is currently online, you may be able to migrate it using your WordPress administrator credentials.

Method A: Migrate WordPress using administrator login

1. Log in to your Hostinger dashboard.
2. Open Websites → Import site.
3. Select Migrate from another host.
4. Enter the current WordPress website's domain.
5. Select WordPress as the migration platform.
6. Enter the requested WordPress administrator login details.
7. Review the migration summary.
8. Submit the migration request.
9. Track the progress from the Migrations section.

Keep the original WordPress website online while the transfer is in progress. Do not change its domain's DNS settings before migration is complete.

Method B: Migrate WordPress using a backup

If the automatic login-based method is unsuitable, you can use a website backup. A WordPress migration backup normally includes:

• WordPress core files.
• The wp-content directory containing themes, plugins, and uploads.
• The WordPress configuration file.
• A SQL export of the WordPress database.

Choose the backup upload option in Hostinger's migration flow, upload the website archive and SQL database file, and review the migration summary before submitting.

6. How to Migrate a Website to Hostinger Manually

If your website is not eligible for assisted migration or you prefer to handle the transfer yourself, you can manually move its files and database.

This method is suitable for many custom PHP websites, static HTML websites, and supported applications that use standard files and databases.

Step 1: Download your website files from the old host

Log in to your current hosting provider and open its File Manager or FTP account. Locate your website's document root and download a complete backup of its files.

Make sure the backup includes all important directories, configuration files, images, uploads, and application files. If your website uses an .htaccess file, include that as well.

Step 2: Export your database

If your website uses a database, open phpMyAdmin or the database management tool provided by your old host.

1. Select the database used by your website.
2. Open the Export option.
3. Choose the appropriate SQL export format.
4. Download the database backup to your computer.

Step 3: Prepare your Hostinger website

Log in to Hostinger and add a custom PHP/HTML website to your destination hosting plan if you are migrating a custom website.

Open the website's management dashboard and launch File Manager.

Step 4: Upload your website files

Navigate to the correct website document root, commonly public_html for a primary shared hosting website. Upload your backup archive or transfer the individual files using File Manager or FTP.

If you uploaded a compressed archive, extract it and verify that the website files are in the correct directory.

Step 5: Create a database on Hostinger

Open the Databases section of your Hostinger dashboard. Create a new database and database user if your application needs one.

Save the new database name, username, password, and hostname. You will need these details when updating the website configuration.

Step 6: Import your database backup

Open phpMyAdmin for the new database, select the database, and use the Import tab to upload your SQL backup.

Wait for the import to finish and check that the database tables have been created successfully.

Step 7: Update the website configuration

Your website may still contain database credentials from the previous hosting provider. Update its configuration file with the new Hostinger database details.

For example, a PHP application might use settings similar to these:

DB_HOST=your_hostinger_database_host
DB_NAME=your_new_database_name
DB_USER=your_new_database_user
DB_PASSWORD=your_new_database_password

The actual configuration format depends on your application. WordPress uses wp-config.php, while other PHP applications may use a separate configuration file or environment variables.

Step 8: Test the website before switching DNS

Check that the website works on the new hosting account. Test its homepage, internal pages, images, forms, login, and database-backed features before pointing the live domain to Hostinger.

Hostinger's manual website transfer guide provides additional instructions for transferring files and databases.

7. How to Transfer a Website Database to Hostinger

A database is an essential part of many dynamic websites. If you move only the website files but forget the database, your site may show an error or lose important content.

What should you transfer?

Depending on your website, the database may contain:

• WordPress posts and pages.
• User accounts and profile information.
• Website settings and plugin data.
• Products and order information.
• Comments and other user-generated content.

Database migration checklist

8. How to Migrate Email Services Separately

One important detail many website owners overlook is email migration. Moving your website does not automatically move your email accounts and mailbox data.

For example, if you use [email protected] or [email protected] through your current hosting provider, those mailboxes may continue to exist on the old service after your website has moved.

What should you do?

1. Identify where your domain's email service is currently hosted.
2. List your existing email addresses and mailboxes.
3. Back up important email messages and attachments.
4. Choose the email service you want to use after migration.
5. Create the required mailboxes on the new email service.
6. Transfer existing mailbox data using the provider's supported migration process.
7. Update MX and other required email DNS records when appropriate.
8. Test sending and receiving messages.

Hostinger documents email migration separately from website migration. Follow its official Help Center for the current email transfer instructions.

9. How to Point Your Domain to Hostinger After Migration

Once your website has been migrated and tested, you can direct your domain to the new Hostinger hosting account.

This is the final step that allows visitors to reach the new version of your website using your existing domain.

Option 1: Change your domain nameservers

If you want Hostinger to manage your domain's DNS records, you can change the nameservers at your domain registrar.

1. Open the domain management page at your current registrar.
2. Find the nameserver settings.
3. Copy the exact nameservers displayed in your Hostinger dashboard.
4. Replace the old nameservers with the Hostinger values.
5. Save the changes.
6. Wait for DNS propagation.

Option 2: Update the A record

If you want to keep DNS management with your current provider, you can point the domain to Hostinger by updating the required A record using the IP address displayed in your hosting dashboard.

This method can be useful when you want to keep email and other DNS services managed by a separate provider.

How long does DNS propagation take?

DNS changes can take up to 24 hours to propagate globally, although they may become visible sooner. During this period, different visitors may temporarily reach different versions of the website.

For the latest instructions, see Hostinger's domain pointing guide.

10. How to Test Your Website After Migration

Before cancelling your old hosting account, thoroughly check the migrated website. A successful file transfer does not necessarily mean every feature is working correctly.

Check the following areas

• Homepage: Confirm that the correct website loads on the new hosting service.
• Internal pages: Open important pages and check navigation links.
• Images and media: Verify that images, videos, and downloadable files work.
• Database: Check that posts, products, accounts, and other stored content are present.
• Forms: Test contact forms, registration forms, and other submissions.
• Login: Verify that administrator and customer login functions work.
• Mobile layout: Check the website on smartphones and tablets.
• SSL certificate: Confirm that the HTTPS version works.
• Email: Send and receive test messages if you migrated email services.
• Performance: Check that pages load correctly and that there are no major errors.

Keep your old hosting account active temporarily

Do not cancel the previous hosting service immediately after migration. Keep it active until the new website has been verified and you are confident that no important files, database records, or email data are missing.

If your website receives frequent updates or customer orders, plan the final switch carefully. You may need a final content or database synchronization to avoid losing changes made during the migration period.

11. Common Website Migration Problems and How to Fix Them

Problem 1: Migration request is rejected

Check whether your website meets Hostinger's migration requirements. The selected plan, website platform, hosting resources, and login accessibility can all affect eligibility. If assisted migration is unavailable, review the manual transfer option.

Problem 2: Website files are missing

Check that the backup includes all website directories and files. Upload the complete archive again if necessary, and verify that files are in the correct document root.

Problem 3: Database connection error

Check the new database hostname, database name, username, and password. Confirm that the database was imported and update the website's configuration file with the new credentials.

Problem 4: Website displays an old version

This may happen because of browser caching, DNS propagation, or an incomplete migration. Clear your browser cache, check the domain's DNS records, and verify the website on the new hosting account.

Problem 5: Website images or CSS are missing

Check that all asset directories were transferred and that the website's file paths are correct. Also check uppercase and lowercase differences in filenames.

Problem 6: Website works but email stops working

Website migration does not automatically transfer email services. Check the domain's MX, SPF, DKIM, and DMARC records and verify that your mailboxes have been moved to the intended email provider.

Problem 7: SSL certificate is not working

Check that the domain points to Hostinger and that the SSL certificate has been issued for the correct domain. Review the SSL settings in the hosting dashboard and test HTTPS after activation.

Problem 8: WordPress pages show 404 errors

Check the WordPress permalink settings and rewrite configuration. You may need to save the permalink settings again from the WordPress dashboard after migration. Also verify that the relevant rewrite rules were transferred correctly.

Problem 9: Some recent content is missing

If the original website received new posts, comments, orders, or customer submissions during migration, the destination may not include those changes. Compare the source and destination databases and perform a final synchronization if necessary.

12. Final Website Migration Checklist

Use this checklist before considering your migration complete:

• Destination Hostinger plan is active.
• Website backup is saved securely.
• Website files transferred successfully.
• Database imported and connected, if required.
• Configuration files updated.
• Homepage and internal pages tested.
• Forms, login, and dynamic features tested.
• Email migration handled separately.
• Domain DNS points to Hostinger.
• SSL certificate and HTTPS verified.
• Old hosting retained until final verification.
• New backup created after migration.

Frequently Asked Questions

Editorial note: Hostinger's migration eligibility, dashboard labels, supported platforms, and transfer options can change. Check the current migration instructions and terms in your account before submitting a request.