Moving a WordPress website to another hosting provider is safe when you preserve the files, database, domain settings, and testing process. The safest method is to create a full backup, copy the site to the new server, test it before changing DNS, then keep the old hosting active until visitors reach the new site.
If you’re moving to Hostinger, first review the hosting basics and check whether your new plan suits one site or several. A migration is much easier when the destination has enough storage and server resources for your current WordPress installation.
What to prepare before moving WordPress
Preparation prevents most migration failures. Gather access to your current hosting account, new hosting account, domain registrar, WordPress dashboard, and email settings before changing anything.
- Confirm the new hosting plan. Check storage, database support, PHP support, backups, email handling, and the number of websites allowed.
- Record your current settings. Write down nameservers, DNS records, email records, redirects, cron jobs, and any special server settings.
- Check your WordPress version. Update WordPress, plugins, and themes only after creating a backup.
- Remove items you no longer need. Old backups, unused plugins, draft media, and cache files make the transfer larger.
- Lower DNS TTL if available. A lower time to live can reduce the wait when the domain points to the new server, though DNS changes still take time to spread.
Do not cancel the old hosting account yet. Keep it active while you test the new copy and wait for DNS traffic to move.
Hostinger’s multi-site hosting limits matter if you plan to move more than one WordPress installation. A plan that handles a small blog may not suit several stores with large media libraries.
Which parts of a WordPress site must move
A WordPress site has more than visible pages. A complete transfer includes the files, database, domain connection, and supporting services.
WordPress files
The files include the WordPress core, themes, plugins, uploads, and configuration file. The uploads folder contains images and other media, so it often makes up most of the transfer size.
The WordPress database
The database stores posts, pages, settings, users, comments, menus, widget settings, and plugin data. Copying the files without copying the database creates an incomplete site.
Domain and DNS records
DNS tells browsers where to find your domain. You may need to update nameservers or edit the domain’s A record. Email records matter too. If your domain handles email, copying only the website can interrupt mail delivery.
SSL and redirects
HTTPS settings and redirects need testing on the new server. An SSL certificate may be issued again for the new hosting account. Existing redirects in .htaccess or a redirect plugin should be checked after the move.
Choose a migration method that matches your site
The right method depends on your access, site size, and tolerance for technical work. Small sites often move well with a migration plugin. Large sites need more control and a careful file and database transfer.
Use the new host’s migration service
Some hosts provide a migration process through their support team or account tools. This is often the least technical route, but the exact eligibility and process depend on the plan and host.
Ask what the service includes before starting. Confirm whether it copies the database, media, email settings, SSL setup, redirects, and multisite configuration. A migration service may move the website but not your mailboxes or third-party DNS records.
Use a WordPress migration plugin
A migration plugin can package the site and restore it on the new host. This suits many small and medium WordPress sites, especially when you can log in to the dashboard on both sides.
Plugin limits can matter. Large media libraries, limited server storage, blocked archive files, or PHP memory limits can stop a package from completing. Check the plugin’s documentation and keep a separate manual backup.
Move the files and database manually
A manual transfer gives you the most control. You download the WordPress files, export the database, upload the files to the new server, create a new database, import the SQL file, and update the database connection in wp-config.php.
This method suits developers and larger sites. It also creates more places for mistakes, especially with database names, usernames, passwords, file paths, and serialized data.
How to transfer a WordPress website to another hosting safely
Follow these steps in order. Keep the old site online until the new copy passes your tests.
- Create a complete backup. Export the WordPress database and download all site files, including
wp-content,wp-config.php, and any custom server files. Store the backup outside your hosting account, then check that the archive opens and the database export is present. - Set up the new hosting account. Add the domain or temporary site address through the new host’s matching account section. Do not change the domain’s DNS yet. The new server needs a place to receive the website first.
- Copy the WordPress files. Upload the backup to the new server and place the files in the document root assigned to the domain. If you use a migration plugin, follow its restore process instead of combining it with a manual upload.
- Create and import the database. Create a new MySQL or compatible WordPress database on the new host. Import the SQL backup, then update
wp-config.phpwith the new database name, username, password, and host value. - Search and replace the old site address. If the domain stays the same, you may not need a broad URL replacement. If the domain changes, update old URLs with a WordPress-safe tool that understands serialized data. A basic text replacement can damage plugin settings.
- Test the site on the new server. Use a temporary URL, hosts-file test, or host-provided preview method when available. Check the homepage, posts, pages, images, menus, forms, login, search, redirects, and checkout if the site sells anything.
- Point the domain to the new host. Change the nameservers or the relevant DNS records at your registrar. Use the records supplied by the new host. Do not guess them from another account.
- Wait for DNS changes to spread. Some visitors may reach the old server while others reach the new one. Avoid editing content during this period because new comments, orders, or form submissions can land on different copies.
- Issue or enable SSL on the new host. Visit the site with HTTPS after the certificate is ready. Fix mixed content, redirects, or certificate warnings before declaring the transfer complete.
- Monitor both sites. Check traffic, orders, email, uptime, error logs, and WordPress admin access. Keep the old hosting account for several days, or longer if the site receives important transactions.
Hostinger’s own migration process can vary by product and account. If you choose that destination, compare this process with the instructions in its account area and its migration walkthrough.
How to test the new WordPress copy before DNS changes
Testing before the domain switch gives you a safe fallback. The goal is to find problems while the old site still serves visitors.
- Open several content types. Test a post, page, category, tag, image, PDF, and any custom post type.
- Test WordPress admin. Log in, edit a draft, upload an image, save a setting, and confirm the changes remain after refreshing.
- Test forms and email. Send a test message and confirm it reaches the correct inbox. Contact forms often depend on separate mail settings.
- Test user actions. Check registration, password reset, comments, memberships, bookings, and customer accounts if they apply.
- Test payments carefully. For a store, use the payment provider’s test mode or a small controlled test. Check order creation, confirmation emails, inventory, and webhooks.
- Check links and redirects. Look for links that still point to a temporary address or the old domain.
- Check mobile layouts. A server move should not change the design, but missing uploads or blocked scripts can appear only on certain pages.
Use the official WordPress project site for software documentation and support references. Host-specific settings still belong to the new provider’s documentation.
What can go wrong during a hosting transfer
Most migration problems come from an incomplete backup, an incorrect database connection, or a DNS change made too early.
| Problem | Likely cause | What to check |
|---|---|---|
| White screen or server error | Plugin conflict, PHP mismatch, memory limit, or damaged file | Disable recently changed plugins, review the host’s error area, and compare the PHP version with your old server |
| Missing images | Uploads were not copied or file paths changed | Compare the wp-content/uploads folders and check image URLs |
| Database connection error | Wrong database name, user, password, or host value | Match every database value in wp-config.php with the new database account |
| Old site appears for some visitors | DNS caching or incomplete propagation | Check the domain records and wait while different DNS resolvers update |
| HTTPS warning | SSL is missing, still issuing, or attached to the wrong domain | Confirm the certificate covers the domain and test both HTTP and HTTPS |
| Forms stop working | Mail settings, blocked sending, or changed domain verification | Test delivery and review the form provider’s domain or SMTP requirements |
Back up before changing files, plugins, themes, or database values. A rushed fix can remove the only working copy. DNS and SSL changes also need time. A correct setting may not appear everywhere at once.
When should you change nameservers?
Change nameservers only after the new website is uploaded and tested. Nameservers direct the domain’s DNS management to a hosting or DNS provider. An A record points the domain to a particular server address.
Use nameservers when you want the new host to manage the domain’s DNS records. Use an A record when DNS remains with your registrar or another DNS provider. The correct choice depends on where your email, verification records, and other services are managed.
Before changing anything, copy your existing DNS records. Include MX records for email, TXT records for verification and security, and any subdomain records. Missing an MX record can affect email even when the website works.
If the domain is registered with GoDaddy, this guide on connecting a registered domain covers the related setup. For Hostinger DNS work, you can also review nameserver changes and record management.
How long should you keep the old host?
Keep the old account active until the new site receives normal traffic and important functions work. A short move may settle quickly, but DNS caches vary between networks and devices.
During the overlap, watch for new comments, orders, registrations, and form messages on the old copy. If the site is active, put it into maintenance mode briefly or freeze content during the final database transfer. A busy store may need a final database sync after the first copy.
Cancel the old account only after you have a fresh backup from the new host. Download invoices and records you may need, and confirm that domain registration is separate from hosting cancellation.
Who should handle the migration themselves?
Manual migration suits a small site owner who can manage backups, databases, DNS, and basic WordPress settings. A plugin or host-assisted move is safer for someone without database experience.
Use professional help for a large store, membership site, multisite network, or website with custom server code. The cost of a short service is often lower than losing orders or customer data.
Hostinger may fit a site owner who wants a lower first-term hosting cost and a guided account setup. The limitation is that the final migration process, included services, and available support depend on the chosen plan and current provider terms.
If Hostinger is your destination, the code hHostCouponHub gives 85% off. The final discount depends on the plan and billing term chosen at checkout.
Questions people ask before changing hosts
Will my WordPress site go offline during the transfer?
It should not if the old host stays active until the new copy works and DNS has updated. Some visitors may briefly reach different servers during DNS propagation, so avoid changing content during that window.
Can I move WordPress without changing the domain name?
Yes. You can keep the same domain and change only the hosting destination. The main work is copying the files and database, then updating DNS after testing.
Do I need to transfer the domain registration too?
No. Domain registration and web hosting are separate services. You can leave the domain with its current registrar and point DNS to the new host.
How do I move email with the website?
Email needs its own check. Preserve MX, TXT, and related records, then confirm that mailboxes and sending settings exist at the new provider before changing DNS.
Is a migration plugin safer than a manual move?
Neither method is automatically safer. A plugin reduces database work for many smaller sites, while a manual move gives more control over large or unusual installations. Keep a separate backup whichever method you choose.
Can I use the code hHostCouponHub for a WordPress migration?
The code applies to eligible Hostinger purchases, not to the migration itself. It provides 85% off, and the final discount depends on the plan and billing term selected at checkout.
Make the DNS switch after the new site passes its checks
Start with a verified backup, build the new copy, test it privately, then change DNS and monitor both servers. If you’re moving to Hostinger, confirm the current plan details and apply hHostCouponHub before payment. The final discount depends on the plan and billing term chosen at checkout.
This page contains affiliate links. If you purchase through the links on this page, we may earn a commission, at no extra cost to you.


