Learning how to migrate WordPress to a new host safely comes down to five stages: back up everything, move your files and database, rebuild the site on the new server, point your domain, and test before you go live. WordPress powers 43.5% of all websites as of early 2026, according to W3Techs, which means millions of owners face this exact task each year. This guide walks through every stage in order, including the pre-migration checklist most tutorials skip and the post-migration tests that catch broken images, lost email, and SEO damage. Read on for the complete process, plus the mistakes that cause downtime and how to avoid them.
What Does It Mean to Migrate a WordPress Site to a New Host?
Quick Answer: Migrating a WordPress site means copying your site files and database from your current hosting server to a new one, then pointing your domain to the new server. The process moves your entire website, including themes, plugins, media, and content, without rebuilding it from scratch. The details determine whether the switch is seamless or causes downtime.
Migrating a WordPress site to a new host is the process of transferring two core components, your website files and your MySQL database, from your existing server to a different hosting environment. Your files include WordPress core, themes, plugins, and the wp-content folder that holds your media uploads. Your database holds posts, pages, settings, users, and (for stores) orders and customers.
A migration does not usually change how your site looks or works. Done correctly, visitors see the same website at the same domain, just served from faster or more reliable infrastructure. The domain name stays yours because it is registered separately from your hosting.
People often confuse three related tasks. Moving hosts keeps the same domain and moves the server. Moving domains changes the web address. Moving both at once happens during a rebrand. This guide focuses on moving hosts while keeping your existing domain, which is the most common scenario.
Why Do People Migrate Their WordPress Site to a New Host?
Quick Answer: People migrate WordPress to a new host to fix slow load times, reduce downtime, cut costs, improve support, or gain features like staging and managed updates. Slow performance and frequent outages are the top triggers, because both directly reduce revenue and search rankings. The hidden risk is that a botched move can cause the very downtime owners are trying to escape.
Site owners move hosts for measurable business reasons, not preference alone. The data makes the stakes clear.
Speed is the most common driver. A one-second delay in page load time reduces conversions by roughly 7%, according to Akamai research widely cited through 2025, and 53% of mobile users abandon a site that takes longer than three seconds to load, per Think with Google. Poor hosting accounts for a significant share of slow-loading sites, so a faster server often produces an immediate performance gain.
Downtime is the second driver. A 2025 Liquid Web survey of 500 business owners and IT decision-makers found that businesses lose an average of five hours per month to downtime, with one in five losing more than $2,500 per month as a result. The same survey found that 43% of respondents cited high costs and 26% cited frequent downtime as reasons they would switch hosts.
Here is what typically pushes owners to migrate:
- Slow page loads that hurt conversions and Core Web Vitals scores
- Recurring downtime during traffic spikes
- Rising renewal prices with no added value
- Weak or slow support when problems appear
- Missing features like free SSL, daily backups, staging sites, and a CDN
- Outgrowing shared hosting as traffic and sales climb
There is a catch worth naming early. The same Liquid Web survey found that nearly seven in ten businesses had delayed switching hosts because of fears around downtime, migration costs, and technical complexity, and that these fears were most common among WordPress and managed WordPress users. That fear is rational, because a careless migration can cause downtime. The rest of this guide exists to remove that risk.
If you would rather skip the technical work entirely, our managed WordPress hosting includes a free, hands-off migration handled by our engineers, so you get the speed upgrade without touching a database.
What Should You Do Before You Migrate a WordPress Site?
Quick Answer: Before migrating a WordPress site, run a full backup, record your site size and PHP and MySQL versions, document active plugins and themes, choose a low-traffic migration window, and confirm your new host is ready. This preparation prevents most migration failures. Skipping it is the single biggest cause of broken migrations.
Preparation determines whether your migration is boring or painful. Complete this pre-migration checklist before you move a single file. This is the WordPress migration checklist that competitors either rush or omit.
Create a Complete Backup of Files and Database
Creating a complete backup means saving a copy of both your WordPress files and your database before any changes begin. A backup is your undo button. If anything goes wrong on the new server, you restore from the backup and try again with zero permanent loss.
Back up two things: the full site directory (usually public_html) and a full export of your MySQL database. Store both copies somewhere off the server, such as your local computer or cloud storage, so a server failure cannot take your backup with it.
Record Your Site Size, PHP Version, and Database Version
Recording your site size and software versions tells you which migration method will work and prevents version mismatches on the new host. Note the total size of your files, because sites larger than roughly 1 GB often exceed the upload limits that migration plugins impose.
Check three versions in your current hosting control panel and confirm the new host matches or exceeds them:
| Component | Where to Check | Why It Matters |
| PHP version | Control panel or Site Health | A lower PHP version on the new host can break plugins and themes |
| MySQL or MariaDB version | Control panel database tools | Version gaps can cause import errors |
| WordPress version | Dashboard footer or Updates screen | The new install should match to avoid conflicts |
Document Active Plugins, Themes, and Custom Settings
Documenting your active plugins and themes gives you a reference list to verify against after the move. Take a screenshot of your Plugins screen and note your active theme, any license keys, and custom code added to functions.php or wp-config.php. Store license keys somewhere safe, because premium plugins and themes may need reactivation on the new domain path.
Choose a Low-Traffic Migration Window
Choosing a low-traffic window minimizes the impact if something goes wrong during the move. Review your analytics and pick the hours when the fewest visitors are on your site, often late night or early morning in your primary time zone. Avoid migrating during sales events, campaigns, or product launches.
Keep Your Old Hosting Active During the Transition
Keeping your old host active means not cancelling your current plan until the new site is fully verified and live. Your old server must stay online while DNS changes propagate worldwide, which can take up to 48 hours. Cancelling early is a common and avoidable cause of downtime.
How to Migrate WordPress to New Host: Two Proven Methods
Quick Answer: The two methods to migrate WordPress to a new host are the plugin method, which automates the transfer and suits most sites, and the manual method, which uses FTP and phpMyAdmin for full control over large or complex sites. Managed hosts offer a third option: they perform the entire migration for you. Your site size and comfort level decide which fits.
There are three practical paths, and the right one depends on your site size, technical confidence, and how much risk you want to carry.
| Method | Best For | Skill Level | Typical Time | Main Risk |
| Migration plugin | Most sites under 1 GB | Beginner | 30 to 60 minutes | Upload limits on large sites |
| Manual (FTP and phpMyAdmin) | Large or complex sites | Advanced | 1 to 3 hours | Human error in database and config edits |
| Managed migration by host | Owners who want zero effort | None required | Handled for you | Choosing a host that does it well |
The plugin method handles complex data restructuring automatically, which is why it works for the majority of sites. The manual method gives complete control when a site is exceptionally large or when plugins fail or time out. The managed option removes the work entirely. The next sections cover the two do-it-yourself methods in full.
How to Migrate WordPress to New Host With a Migration Plugin
Migrating WordPress with a plugin means installing a migration tool that exports your entire site into a single package, then importing that package on the new server. This is the easiest method and the one most beginners should choose. Popular free options include All-in-One WP Migration, Duplicator, and Migrate Guru, all available in the official WordPress plugin directory.
Follow these steps in order:
- Install a migration plugin on your current site. Log into your existing WordPress dashboard, then install and activate a well-rated migration plugin.
- Export your website to a file. Open the plugin, choose the Export option, and select File. Download the generated package to your computer. This single file contains your files and database together.
- Install a fresh copy of WordPress on the new host. Log into your new hosting control panel and use the one-click installer to set up a blank WordPress site.
- Install the same plugin on the new site and import. Activate the identical migration plugin on the blank site, open the Import screen, upload your package, and confirm the overwrite.
- Save your permalinks twice. Log into the new dashboard with your old credentials, go to Settings then Permalinks, and click Save Changes twice to rebuild your URL structure.
If your export file is larger than your new host’s upload limit, the import may fail. That size ceiling is the main reason large sites move to the manual method below.
How to Manually Migrate a WordPress Site With FTP and phpMyAdmin
Manually migrating a WordPress site means transferring your files with an FTP client and your database with phpMyAdmin, giving you full control when plugins fail or time out. This method suits large sites, complex stores, and any migration where an automated tool stalls. It has more steps, but nothing here is difficult once you understand what each file does.
Phase 1: Download everything from your old host
- Download your site files. Connect to your old server with an FTP client such as FileZilla, or use your control panel’s File Manager. Download the entire root directory, usually public_html, to your computer. The wp-content folder and your wp-config.php file are the two most important pieces.
- Export your database. Open phpMyAdmin in your old control panel, select your WordPress database, click the Export tab, choose the Quick method, and download the .sql file.
Phase 2: Upload everything to your new host
- Create a new database and user. In your new hosting panel, open the MySQL Databases tool. Create a new empty database, create a new user with a strong password, and assign that user to the database with all privileges. Save these credentials.
- Edit your wp-config.php file. Open the downloaded wp-config.php in a plain text editor. Update DB_NAME, DB_USER, DB_PASSWORD, and DB_HOST to match the new credentials you just created.
- Upload your files. Connect to the new server by FTP and upload all your WordPress files, including the edited wp-config.php, into the new root directory.
- Import your database. Open phpMyAdmin on the new host, select your new empty database, click the Import tab, choose your .sql file, and run the import.
- Update site URLs if needed. If your temporary URL differs from your live domain during testing, update the siteurl and home values, then run a safe search-and-replace so serialized data is not corrupted.
The manual method is reliable precisely because it does not depend on a plugin completing a large upload in one pass. That control is why agencies keep it in their toolkit.
Manual migrations demand comfort with databases and server files. If that is not your world, Prestige Technologies web development and hosting teams handle manual and complex migrations, including large WooCommerce hosting stores where order data cannot be lost.
How Do You Configure DNS After Migrating WordPress?
Quick Answer: After migrating WordPress, you point your domain to the new host by updating either your nameservers or your DNS records at your domain registrar. Propagation can take 2 to 48 hours to complete worldwide. Keeping your old host live during this window is what makes a zero-downtime switch possible.
Configuring DNS after a migration is how you route real visitors from the old server to the new one. Until you change DNS, your domain still points at the old host, which is useful, because it lets you test the new site privately first.
You have two ways to point your domain:
- Update nameservers. Log into your domain registrar, find the Nameservers section, and replace the old nameservers with the ones in your new host’s welcome email. This moves everything, including email, to the new host.
- Update DNS records only. Change the A record to the new server’s IP address to move only the website while keeping email where it is. This is the safer choice when your email lives elsewhere.
How to Migrate WordPress to New Host With Zero Downtime
Migrating with zero downtime means testing the new site fully before you change DNS, then keeping the old host online until propagation finishes. Follow this sequence to keep your site reachable the entire time.
- Preview the new site before DNS changes using a temporary URL or a local hosts file entry that maps your domain to the new server’s IP only on your computer.
- Confirm every page, image, form, and (for stores) checkout works on the new server.
- Only then update DNS at your registrar.
- Leave the old host active for at least 48 hours so visitors hitting either server see a working site during propagation.
Because both servers serve the same content during propagation, no visitor ever lands on a broken page. This is the core of a professional, downtime-free move.
What Should You Test After Migrating a WordPress Site?
Quick Answer: After migrating a WordPress site, test your homepage and key pages, all images and internal links, contact and checkout forms, SSL and mixed content, email delivery, and search functionality. Post-migration testing catches the silent failures that a quick glance misses. Skipping it is how broken images and lost leads slip live unnoticed.
Testing after a migration is not optional, because some failures are invisible on the homepage. Work through this post-migration checklist on the new server before and after you switch DNS.
Verify Core Pages, Links, and Images
Verifying pages, links, and images confirms your content and media transferred with correct paths. Click through your homepage, top landing pages, and a sample of posts. Look specifically for broken images, which usually mean the media path still points to the old domain and needs a database search-and-replace.
Test Forms, Checkout, and Interactive Features
Testing forms and checkout confirms that lead capture and revenue functions still work. Submit a test contact form, complete a test order in a store, and confirm confirmation emails arrive. For WooCommerce stores, verify payment gateways, tax settings, and order emails, because these depend on domain-specific configuration.
Check SSL and Fix Mixed Content Warnings
Checking SSL confirms your certificate is active on the new host and your site loads over HTTPS. Mixed content warnings appear when a secure page still loads images or scripts over insecure HTTP, often after a migration. Fix them with a database search-and-replace from http:// to https:// so browsers show the padlock and trust signals stay intact.
Confirm Email Still Works
Confirming email works is the step most tutorials forget, and it causes real damage when skipped. If you changed nameservers, your MX records moved too, which can break email. Send and receive a test message on every affected address, and mirror your MX records on the new host if email did not follow.
Review Search Console and Rankings
Reviewing Search Console confirms search engines can still crawl and index your migrated site. Check that your site is not accidentally blocking crawlers under Settings then Reading, submit your sitemap, and monitor coverage for a week. A brief, small ranking fluctuation is normal; a sustained drop signals a problem to investigate.
What Are the Most Common WordPress Migration Mistakes to Avoid?
Quick Answer: The most common WordPress migration mistakes are skipping backups, changing DNS before testing, ignoring SSL and mixed content, corrupting serialized data during URL replacement, forgetting email and MX records, and cancelling the old host too soon. Each mistake causes downtime, data loss, or broken functionality. All are avoidable with the steps in this guide.
Most migration disasters trace back to a short list of errors. Avoiding these keeps your move clean.
- Skipping the backup. Without a backup, a failed import can mean permanent loss. Always back up files and database first.
- Changing DNS before testing. Pointing your domain at an untested server sends live visitors to a broken site. Test first, switch DNS last.
- Cancelling the old host too early. Propagation takes up to 48 hours. Keep the old server live until the new one is confirmed everywhere.
- Ignoring mixed content. Leftover http:// links break the padlock and erode trust. Run a secure search-and-replace after moving.
- Corrupting serialized data. WordPress stores some settings as serialized arrays. A raw find-and-replace can break them, so use a tool built to handle serialized data safely.
- Forgetting email. Changing nameservers can silently break email. Plan MX records before switching.
- Overlooking file permissions. Wrong permissions on wp-content after extraction can break uploads and search-and-replace tools. Reset them if media or plugins misbehave.
- Timeouts on large sites. Plugin exports on large sites often stall. Switch to the manual method rather than retrying a failing upload.
How to Migrate WordPress to New Host Without Losing Data
Migrating without losing data means backing up before you start, verifying the database import finished completely, and keeping the old copy until the new site is confirmed. Never delete anything on the old server until every page, order, and email on the new server checks out. Your old host is your safety net, so keep it until the net is no longer needed.
How Do You Preserve SEO Rankings During a WordPress Migration?
Quick Answer: You preserve SEO during a WordPress migration by keeping the same domain and URL structure, transferring all content and metadata intact, maintaining SSL, and submitting your sitemap after the move. When the domain and URLs stay the same, search engines see no change worth penalizing. Downtime and broken URLs are the real ranking risks, not the migration itself.
Preserving SEO during a migration is mostly about avoiding disruption, because a same-domain host move should be invisible to search engines. A complete migration carries your posts, pages, metadata, and permalink structure across unchanged, so rankings hold.
Three factors protect your rankings:
- No downtime. A site that returns errors during the switch can lose crawl access and, as one 2025 analysis noted, sites with even 0.1% downtime risk losing organic traffic. The zero-downtime method above prevents this.
- Identical URLs. Keep your permalink structure the same so every ranked URL still resolves. If any URL must change, add a 301 redirect from old to new.
- Working SSL. A secure site is a ranking signal, so confirm HTTPS loads cleanly with no mixed content.
After the move, submit your sitemap in Google Search Console and watch coverage for a week. This is also a good moment to read the Prestige Technologies blog for related guides on WordPress speed and Core Web Vitals, since a faster new host can lift rankings beyond simply preserving them.
Migrate Your WordPress Site the Easy Way
Knowing how to migrate WordPress to new host gives you full control over your site’s future, and the process above works whether you choose the plugin method, the manual method, or a managed move. Back up first, transfer files and database, rebuild on the new server, point your domain, and test thoroughly before you go live. Follow the checklist, keep your old host active through propagation, and downtime never enters the picture.
If you would rather skip every technical step, we migrate your WordPress site for free, with minimal disruption, handling backups, transfer, DNS, and testing end to end. Our managed WordPress hosting pairs that hands-off migration with faster load times, automated backups, and expert support, so your move upgrades your site instead of just changing servers. Request a free migration today and let our team do the heavy lifting while you focus on your business.
Frequently Asked Questions
1. How do I migrate my WordPress site to a new host without downtime? Migrate without downtime by testing the new site fully before changing DNS, then keeping your old host active during propagation. Preview the new server using a temporary URL or a local hosts file entry, confirm every page and form works, and only then update your domain. Because both servers serve the same content during propagation, visitors never see a broken page.
2. What is the easiest way to move a WordPress site to a new host? The easiest way to move a WordPress site is a migration plugin that exports your whole site into one file, which you then import on a fresh WordPress install on the new host. This automated method suits most sites under 1 GB and takes 30 to 60 minutes. Larger sites that exceed upload limits usually need a manual transfer instead.
3. Can I migrate WordPress to a new host without a plugin? Yes, you can migrate WordPress without a plugin by transferring files with an FTP client and moving your database through phpMyAdmin. Download your site directory and export your database, then upload the files, import the database, and update your configuration file on the new host. This manual method gives full control and works well for large sites where plugins time out.
4. How long does a WordPress migration take? A WordPress migration typically takes 30 minutes to 3 hours of hands-on work, depending on site size and method. Plugin migrations of small sites finish fastest. Manual migrations of large sites take longer. Separately, DNS propagation after you point your domain can take 2 to 48 hours to complete worldwide, which is why you keep the old host active during that window.
5. Will migrating WordPress to a new host affect my SEO? Migrating to a new host while keeping the same domain should not hurt SEO, because your URLs, content, and metadata transfer unchanged. Search engines see no change worth penalizing. The real risks are downtime and broken URLs during the switch, so use a zero-downtime method, keep your permalink structure identical, and submit your sitemap afterward to confirm crawling continues.
6. What files do I need to migrate a WordPress site? You need two things to migrate a WordPress site: your website files and your database. The files include WordPress core, your themes, plugins, and the wp-content folder holding media uploads. The database holds posts, pages, settings, users, and store data. The wp-config.php file connects the two and must be updated with your new database credentials on the destination server.
7. How do I move my WordPress database to a new host? Move your WordPress database by exporting it from phpMyAdmin on your old host as a .sql file, then importing that file into a new empty database on the destination host. Create the new database and user first, assign full privileges, and update your wp-config.php file with the new credentials. Then run the import through phpMyAdmin on the new server.
8. Do I have to keep my old hosting active during migration? Yes, keep your old hosting active until the new site is fully verified and DNS has propagated, which can take up to 48 hours. Your old server continues serving visitors while the domain change spreads worldwide, preventing downtime. Cancelling too early is a common cause of outages. Delete old files and close the account only after the new site checks out everywhere.
9. How do I update DNS after moving WordPress hosting? Update DNS by logging into your domain registrar and either replacing your nameservers with the new host’s nameservers or changing your A record to the new server’s IP address. Nameservers move everything including email, while changing only the A record moves just the website. Save the changes and allow 2 to 48 hours for global propagation before expecting the switch to complete.
10. What is the best free WordPress migration plugin? The best free WordPress migration plugins include All-in-One WP Migration, Duplicator, and Migrate Guru, all available in the official WordPress plugin directory. Each exports your site into a package you import on the new host. Choose based on your site size, since free versions impose upload limits that can block large sites. For those, a manual migration is more reliable.
11. How do I migrate a large WordPress site that keeps timing out? Migrate a large site that times out by switching from a plugin to the manual method using FTP and phpMyAdmin. Plugin exports often stall when a site exceeds upload limits or server timeouts. Downloading files directly and importing the database separately avoids the single large upload that causes failures. Splitting a very large database export into smaller pieces also helps the import complete.
12. Can I migrate WordPress and keep the same domain name? Yes, you can migrate WordPress to a new host and keep the same domain, which is the most common scenario. Your domain is registered separately from your hosting, so you simply repoint it to the new server after moving your files and database. Visitors see the same web address served from new infrastructure, and keeping the domain unchanged also protects your search rankings.
13. How do I fix broken images after migrating WordPress? Fix broken images after migration by running a database search-and-replace that updates old image paths to the new site URL. Broken images usually mean media links still point to the old domain or a temporary URL. Use a tool that handles serialized data safely rather than a raw find-and-replace, then clear your cache and confirm the images load across several pages.
14. How much does it cost to migrate a WordPress site? Migrating a WordPress site yourself costs nothing beyond your time if you use free tools and methods. Some hosts charge for migration support, with fees reported around $100 per site at certain providers. Many quality hosts include free migration with a new plan. Weigh the cost against the risk, because a failed do-it-yourself move can be more expensive than a professional one.
15. How do I test my WordPress site after migration? Test your migrated WordPress site by checking core pages, all images and internal links, contact and checkout forms, SSL and mixed content, email delivery, and search functionality. Do this on the new server before changing DNS whenever possible. Broken images signal a path issue, mixed content warnings signal an SSL fix is needed, and missing email signals your MX records require attention.
16. How should I move WordPress between two hosting companies? Move WordPress between two hosting companies by exporting your site and database from the first host, installing a fresh WordPress on the second, and importing your content there. Use a migration plugin for most sites or the manual FTP and phpMyAdmin method for large ones. Test the new site using a temporary URL, then repoint your domain and keep the old host live during propagation.
17. What is the difference between migrating hosts and migrating domains? Migrating hosts moves your website to a new server while the domain name stays the same, whereas migrating domains changes the actual web address. Host migration is usually invisible to visitors and search engines. Domain migration changes every URL and requires 301 redirects to preserve rankings. This guide covers host migration with the same domain, the most common and lowest-risk move.
18. Why is my site redirecting to the old host after migration? A site that redirects to the old host after migration usually has old URLs still stored in the database or cached DNS pointing to the previous server. Check the siteurl and home values in your database, run a search-and-replace to update any old domain references, and clear your browser and site caches. If it persists, confirm there are no forwarding rules on the domain.
19. Do I need to update file permissions after migrating WordPress? You may need to reset file permissions after migrating WordPress if uploads, plugins, or search-and-replace tools stop working on the new server. Extracting a compressed wp-content folder can leave incorrect permissions. Standard settings are 755 for folders and 644 for files, with wp-config.php often set more restrictively. If media fails to load or upload after a move, wrong permissions are a likely cause.
20. Should I migrate WordPress myself or use a professional service? Migrate WordPress yourself if you are comfortable with backups, databases, and DNS and your site is straightforward. Use a professional or managed service if your site is large, runs a store, or you cannot risk downtime. Many hosts perform the entire migration for free with a new plan, removing the technical work and the risk of data loss or extended outages during the switch.