Moving a WordPress website to a new hosting provider is usually straightforward if you follow a structured process and verify each step before switching traffic. A careful migration helps preserve content, SEO value, email continuity, and uptime. Whether you are moving from shared hosting to managed hosting, from one control panel to another, or into a Plesk-based environment, the key is to transfer files, databases, and configuration in the right order and test everything before updating DNS.
This guide explains how to move a WordPress website to a new hosting provider with minimal risk. It is designed for site owners, developers, and support teams working in a hosting platform or control panel environment.
What you need before you start
Before moving a WordPress site, make sure you have access to both the current and the new hosting accounts. If the destination uses a control panel such as Plesk, confirm that you can create a domain or subscription, manage databases, and upload files. It also helps to schedule the migration during a low-traffic period, especially for stores, membership sites, or sites with frequent form submissions.
Checklist before migration
- Full access to the old hosting account, including file manager or SFTP and database credentials.
- Access to the new hosting platform or Plesk panel.
- A backup of the website files and database.
- Current DNS provider access.
- Any email accounts connected to the domain documented in advance.
- Plugin, theme, and WordPress version details.
- SSL certificate status and renewal method.
If your website uses caching, security, or performance plugins, note their settings before transfer. Some plugins store server-specific paths or need to be reconfigured after migration.
Choose the migration method
There are several ways to move a WordPress website to a new hosting provider. The right method depends on the size of the site, your technical comfort, and the tools available in the hosting platform.
Manual migration
This method involves copying the WordPress files and exporting/importing the database manually. It gives the most control and works well when moving between different hosting environments, including managed hosting and Plesk.
Migration plugin
Plugins can automate the transfer of content, themes, plugins, and the database. This is often the easiest option for smaller sites. Popular migration plugins can create an archive and restore it on the new server, but they may have limits on large websites or complex configurations.
Host-assisted migration
Some hosting providers offer migration support as part of their service. This is a good option if you want less hands-on work and your new host can import the site into their control panel or managed hosting stack.
For SEO-sensitive sites, the best approach is the one that allows you to fully test the new environment before DNS changes go live.
Step 1: Create a complete backup
The first step is to create a complete backup of the WordPress website. A migration backup should include all site files and the database. In hosting platforms with a control panel, you can often use the file manager, backup tool, or an SFTP client together with phpMyAdmin or a similar database tool.
What to back up
- WordPress core files
- wp-content folder, including themes, plugins, and uploads
- Database containing posts, pages, users, settings, and plugin data
- Custom configuration files such as wp-config.php
- .htaccess or server rewrite rules if applicable
Do not rely on a single backup copy. Keep one copy on your local machine and one in secure cloud or external storage. If the migration fails, a clean backup lets you restore the site quickly.
Step 2: Prepare the new hosting environment
Before transferring content, set up the destination account correctly. In a managed hosting or Plesk environment, this often means creating a domain, subscription, or hosting space, then preparing the web root and database.
Set up the domain or subscription
If the domain is already pointed to the new provider, you can use a temporary URL or hosts file entry for testing. If not, create the site structure in the control panel so the files have a proper location when uploaded.
Create a new database
Create a new MySQL or MariaDB database, a database user, and a strong password. Record the database name, username, host, and password. In many hosting platforms, the database host is localhost, but some managed environments use separate database servers.
Match the required environment
Check the WordPress version, PHP version, and extensions supported by the new host. If the old site used a specific PHP version or required modules, try to match them first. This reduces the chance of plugin errors or theme conflicts after migration.
Step 3: Transfer WordPress files
Once the destination is ready, copy the website files to the new server. You can do this with SFTP, the control panel file manager, or a migration plugin archive.
Using SFTP or file manager
Download the current WordPress files from the old hosting account and upload them to the document root of the new hosting account. Make sure the wp-content folder, uploads directory, and any custom files are included. If the site is large, compressing the files into an archive before transfer can save time.
Important file permissions
After upload, verify file and folder permissions. Incorrect permissions can cause broken media uploads, plugin update failures, or security issues. Typical WordPress permissions are 755 for directories and 644 for files, though your hosting provider may recommend specific settings.
Step 4: Move the database
The WordPress database stores posts, pages, menus, user accounts, settings, and plugin data. If the database is not transferred correctly, the site may load with missing content or errors.
Export the database from the old host
Use phpMyAdmin or an equivalent database tool to export the WordPress database as a SQL file. For best compatibility, use a standard export format and include all tables.
Import the database on the new host
Import the SQL file into the new database you created earlier. If the database is large, the hosting provider may offer command-line tools or optimized import methods. In a Plesk-based environment, database import tools are often available directly from the panel.
Update wp-config.php
After import, update wp-config.php with the new database name, database user, and password. Also confirm the table prefix if your site uses a non-default prefix. A mismatch here is one of the most common causes of post-migration errors.
Step 5: Update site URLs if needed
If the domain name remains the same, WordPress usually does not need a full URL change. However, if you are testing on a temporary domain, moving from HTTP to HTTPS, or changing the site path, you may need to update the WordPress address and site address.
When to run a search and replace
Run a careful search and replace when the old site URL differs from the new one. This is especially important for links stored inside the database, such as image paths, serialized data, or page builder content. Use a reliable tool to avoid breaking serialized strings.
Examples of situations that require URL updates:
- Moving from http:// to https://
- Testing the site on a temporary domain
- Changing the folder location of WordPress
- Moving from a subdomain to the root domain
Step 6: Test the migrated site before DNS changes
Testing before changing DNS is essential. It lets you confirm that the site works on the new hosting platform without affecting live visitors. This is especially useful in hosting and control panel environments where you can preview the site using a temporary URL or local hosts file entry.
What to test
- Homepage loading and navigation
- Posts, pages, and media files
- Login to wp-admin
- Forms and contact submissions
- Shopping cart and checkout, if applicable
- Search function
- Permalinks and clean URLs
- SSL certificate and HTTPS redirects
- Plugin and theme functionality
Check browser console errors and server logs if something appears broken. In many cases, a plugin conflict, missing PHP extension, or incorrect file path is the cause.
Step 7: Handle email and DNS carefully
Website migration and email migration are not always the same thing. If your domain email is hosted with the same provider, confirm whether email accounts must be recreated on the new server before changing DNS. Failing to do this can cause mailbox downtime.
DNS update strategy
Once the new site has been tested, update the DNS records to point the domain to the new host. The main record is usually the A record, although some setups use CNAME or managed DNS service. DNS propagation can take time, so lower the TTL in advance if possible to speed up the switch.
How to avoid downtime
- Keep the old hosting account active during propagation.
- Do not cancel the old service until the new site is verified.
- Check both www and non-www versions of the domain.
- Confirm email MX records are still correct.
If your provider supports it, you can use staged migration or temporary domain testing to reduce the risk of any visible interruption.
Step 8: Verify SEO elements after migration
A WordPress migration can affect SEO if redirects, canonical URLs, structured data, or internal links break. Search engines should see the same content and the same URL structure unless you intentionally changed it.
SEO checks after a move
- Confirm that page titles and meta descriptions are intact.
- Check canonical tags on key pages.
- Verify 301 redirects if URLs changed.
- Make sure robots.txt is not blocking important pages.
- Resubmit the XML sitemap in Google Search Console if necessary.
- Test schema markup and Open Graph tags.
If the site uses a caching plugin or CDN, clear the cache after the migration. Stale cached content can make it look as if the move failed even when the new server is working correctly.
Step 9: Optimize the new hosting setup
After the migration is complete, take the opportunity to improve the WordPress hosting setup. A move to a better hosting platform often brings performance, stability, and management benefits, but only if the environment is configured correctly.
Recommended post-migration tasks
- Enable SSL and force HTTPS.
- Set up server-side caching if available.
- Update PHP to a supported version.
- Remove unused plugins and themes.
- Check image optimization and lazy loading settings.
- Review cron jobs and scheduled tasks.
- Enable automatic backups on the new host.
In Plesk or managed hosting environments, you may also be able to enable security tools, set PHP limits, configure redirect rules, and manage backups from the panel. These features can improve reliability after the move.
Common migration problems and how to fix them
Even well-planned migrations can run into issues. Most problems are related to database access, URL mismatches, caching, or server configuration.
White screen or 500 error
This often points to a plugin conflict, a PHP compatibility problem, or missing file permissions. Rename the plugins folder temporarily to isolate the issue, then reactivate plugins one by one.
Missing images or broken links
This usually means the uploads folder was not copied fully, or the site URLs were not updated correctly. Check the wp-content/uploads directory and run a proper search and replace if the domain changed.
Can’t log in to wp-admin
Confirm that the database import completed successfully and that cookies are not being blocked by an SSL or domain mismatch. Also check whether the site address in the database points to the wrong URL.
Forms or checkout not working
These issues often occur when JavaScript, caching, or CAPTCHA settings are different on the new host. Disable aggressive caching, confirm SMTP settings, and test with a clean browser session.
Best practices for a safe WordPress migration
A successful move is not only about transferring data. It also requires planning, verification, and rollback readiness. Following a few best practices can save time and prevent damage to rankings or user experience.
- Always keep a full backup before making changes.
- Test the site on the new host before changing DNS.
- Document all credentials, records, and settings.
- Keep the old hosting account active until the new one is stable.
- Use 301 redirects if URLs change.
- Check email separately from the website.
- Monitor logs and uptime after the move.
If you are migrating multiple sites or a large WordPress installation, consider performing the move in phases. For example, move staging first, then production, and validate each environment before proceeding.
FAQ
How long does it take to move a WordPress website to a new hosting provider?
A small WordPress site can often be moved in less than an hour, excluding DNS propagation. Larger sites, eCommerce stores, and sites with custom configurations may take several hours or longer, especially if testing and URL replacement are needed.
Will my website go offline during migration?
It should not if you prepare correctly. The safest process is to copy and test the site on the new host first, then update DNS. Keeping the old hosting active during propagation helps avoid downtime.
Do I need to migrate email too?
Only if your email is hosted with the same provider and you want it to continue working there after the move. Website hosting and email hosting can be separate, but they often share the same DNS records, so you should verify MX settings carefully.
Can I move a WordPress site without a plugin?
Yes. Manual migration is fully possible and often preferred for greater control. It involves copying files, exporting and importing the database, and updating configuration details.
What should I do if the new host uses Plesk?
Create the domain or subscription in Plesk, set up a database, upload the WordPress files to the correct document root, import the database, and update wp-config.php. Then test the site using the panel’s tools or a temporary URL before switching DNS.
Will changing hosts affect SEO?
Not if the migration is handled correctly. Keep URLs consistent, preserve redirects, maintain metadata, and avoid long downtime. Search engines are more likely to react negatively to broken pages or inconsistent content than to the hosting change itself.
Conclusion
Moving a WordPress website to a new hosting provider is a process of preparation, transfer, testing, and validation. If you back up the site, set up the new hosting environment correctly, move files and databases carefully, and verify the site before updating DNS, the migration can be completed with minimal risk. For hosting platforms, managed hosting, and Plesk-based environments, the same principles apply: preserve data, protect SEO, and confirm service continuity before going live.
After the move, monitor performance, fix any broken links or configuration issues, and keep backups enabled on the new host. A well-executed migration not only changes where the site is hosted, but can also improve speed, stability, and long-term maintainability.