Migrate WordPress site: Ultimate 2025 Guide

Why Moving Your WordPress Site Doesn’t Have to Be Stressful

Successfully planning to migrate WordPress site assets is more straightforward than many realize. It’s a strategic business decision, not just a technical task. Whether you’re switching hosts for better performance, rebranding with a new domain, or seeking enhanced security, moving your WordPress site is a common and necessary step for growth. A seamless migration protects your brand reputation, preserves your hard-earned SEO rankings, and ensures business continuity without disrupting your customer experience.

Quick Answer: How to Migrate WordPress Site

1. Backup your current site files and database.
2. Transfer the files and database to the new hosting environment.
3. Configure the database connection and update site settings.
4. Test the site thoroughly before updating your DNS to go live.

The most common reasons to migrate include:

• Performance issues: Slow loading times that hurt sales and SEO.
• Security concerns: Outdated hosting environments that increase vulnerability.
• Cost savings: Finding better hosting deals or features.
• Rebranding: Moving to a new domain name.
• Scalability: Outgrowing a host that can’t handle your traffic.

You have two main paths: manual migration offers complete control but requires technical skill, while plugin-assisted migration provides convenience but can struggle with larger sites. A typical migration takes 1 to 4 hours of active work, with DNS changes taking up to 72 hours to fully propagate worldwide.

I’m Kevin Gallagher, and with over 15 years of experience, I’ve managed hundreds of WordPress migrations. Through wpOncall, I’ve learned that proper preparation and a systematic, step-by-step approach are the keys to a smooth migrate WordPress site process. This guide demystifies the procedure, turning a potentially stressful task into a manageable and successful project that sets your site up for future success.

Preparing for Liftoff: Your Pre-Migration Checklist

Proper preparation is the key to a successful migration. Before you migrate WordPress site files, you need to have your new environment ready and your tools in order. This planning phase prevents most common migration headaches.

First, gather your prerequisites. You’ll need full administrative access to your new hosting account, including control panel (cPanel, Plesk, or a custom panel) credentials. It’s also wise to check the resources of your new plan—ensure it has sufficient storage, RAM, and PHP memory limits for your site’s needs. You will also need login access to your domain registrar (like GoDaddy, Namecheap, or Google Domains) to update your DNS settings later.

Your WordPress site consists of two main parts: site files and a database. The files include the WordPress core, but most importantly, your wp-content folder. This folder is the heart of your site’s unique identity, containing:

• Themes: The design and layout of your site.
• Plugins: The tools that add functionality, from contact forms to e-commerce.
• Uploads: All your uploaded media, such as images, videos, and documents, typically organized by year and month.

The database stores all your posts, pages, user data, comments, and configuration settings. Both the files and the database must be moved perfectly for the site to function.

To make the process smooth, have these tools ready:

• An FTP client like FileZilla: This is your digital moving truck for transferring files between servers. Use SFTP (Secure FTP) if available for an encrypted connection.
• A plain text editor like Notepad++: Essential for editing configuration files without adding formatting that can break your site.
• cPanel or Hosting Control Panel Access: This provides access to File Manager and database tools like phpMyAdmin.

How to Back Up Your WordPress Site for Migration

A complete backup is your non-negotiable insurance policy. Before you touch a single file, you must have a complete, restorable copy of your site. If anything goes wrong—a corrupted file, a database import error, or a server issue—you can restore your site to its original state and start over without any data loss. At wpOncall, we know that a reliable WordPress Backup Solution is the foundation of any safe migration.

Backing Up Your Site Files:
You have two main options:

1. cPanel File Manager: Log into your current host’s cPanel, navigate to File Manager, and find your public_html folder. Select all files (including hidden files like .htaccess) and use the “Compress” function to create a single ZIP archive. This is much faster to download than thousands of individual files.
2. FTP Client: Connect to your server with FileZilla. Navigate to your WordPress root directory and download the entire folder to your computer. Ensure your client is set to show hidden files.

Backing Up Your Database:
Databases require a special process:

1. Access phpMyAdmin from your current host’s cPanel.
2. Select your WordPress database from the list on the left.
3. Click the “Export” tab.
4. Choose the “Quick” export method and ensure the format is set to “SQL”.
5. Click “Go” to download a .sql file. This file contains all your site’s content and settings.

With these file and database backups, you’re ready for the next steps in your WordPress Backup and Migration.

The Manual Method: How to Migrate WordPress Site Step-by-Step

For complete control over the migrate WordPress site process, the manual method is the most reliable option. It’s ideal for large websites or complex setups where automated plugins might fail. While it requires more technical comfort, manual migration is transparent, ensuring you know exactly what’s happening at every stage.

This method takes more time, but the payoff is a deeper understanding of your site’s structure and the confidence that nothing was missed. You’ll never have to wonder if a plugin failed silently in the background.

Step 1: Create and Prepare the New Environment

Before moving anything, you must prepare the new server. The first task is creating a new, empty database for your WordPress content.

Log into your new host’s cPanel and find the “MySQL Databases” or “Database Wizard” tool. The wizard is often the easiest path as it guides you through all the necessary steps.

1. Create a New Database: Give it a descriptive name (e.g., wp_newsite). Your host will likely add a prefix based on your account username, like yourhost_wp_newsite. This prefix is a security measure to prevent database name collisions on shared servers.
2. Create a Database User: This user account is what WordPress will use to access the database. Create a strong, unique password for it using a password generator. Avoid reusing passwords.
3. Assign the User to the Database: This is a critical step that is often missed. You must grant the user you just created All Privileges on the new database. Without full privileges, WordPress cannot create or modify tables, leading to errors during operation.

Write down these four pieces of information:

• Database Name
• Database Username
• Database Password
• Database Host (usually localhost, but check with your host)

Step 2: Upload Files and Import the Database

With the new environment ready, it’s time to move your site.

Uploading Your Site Files:
Using your FTP client (preferably using the more secure SFTP protocol if your host supports it) or the new host’s File Manager, connect to your new server. Navigate to the public_html directory (or www, httpdocs, depending on your host).

If you created a ZIP archive of your files, upload that single file and use the File Manager’s “Extract” tool. This is significantly faster and more reliable than uploading thousands of individual files via FTP, which can lead to transfer failures or timeouts. The most important folder to transfer is wp-content, which contains your themes, plugins, and media. For a detailed walkthrough, see our guide on how to Upload WordPress Backup to New Host.

Importing Your Database:

1. In your new host’s cPanel, open phpMyAdmin.
2. Select the empty database you created in Step 1 from the left-hand menu.
3. Click the “Import” tab.
4. Click “Choose File” and select the .sql database backup file you downloaded from your old site.
5. Important Note for Large Databases: phpMyAdmin often has a file size limit (e.g., 50MB) and can time out during long imports. If your .sql file is larger than this, the import will fail. In this case, you have a few options:
   • Use a tool like BigDump: This is a PHP script that imports large database files in smaller chunks to avoid timeouts.
   • Use the command line: If you have SSH access, you can import the database directly using a command like mysql -u [username] -p [database_name] < [file.sql]. This is the most reliable method for very large databases.
   • Contact your host: Your new hosting provider’s support team can often import the database for you.
6. If your database is small enough, click “Go” to begin the import. This may take several minutes.

Step 3: Configure wp-config.php and Finalize

The wp-config.php file tells WordPress how to connect to its database. This final configuration step is crucial to making your site work on the new server.

Locate the wp-config.php file in your site’s root directory on the new server. Always make a backup of this file before editing. Open it with a plain text editor.

Find these lines of code:

define( 'DB_NAME', 'database_name_here' );
define( 'DB_USER', 'username_here' );
define( 'DB_PASSWORD', 'password_here' );
define( 'DB_HOST', 'localhost' );

Carefully replace the placeholder values with the new database credentials you recorded in Step 1. Be precise with spelling and punctuation. For more details, the official WordPress documentation offers guidance on editing wp-config.php.

Save the file and upload it back to the server, overwriting the old version. Once uploaded, it’s good practice to check its file permissions. For security, wp-config.php should be set to 644 or 600 to prevent other users on the server from reading it. At this point, your WordPress files are connected to the database, and your site should be functional on the new server.

Manual vs. Automated: Choosing Your Migration Path

When you decide to migrate WordPress site content, you face a key choice: a hands-on manual migration or an automated plugin-assisted one. Each path has distinct advantages depending on your site’s size, your technical skill, and your timeline.

Manual migration gives you complete control. It’s the most reliable method for large or complex sites, as you handle every file and database table directly, avoiding the timeouts that can plague automated tools. The downside is that it’s time-consuming and requires technical confidence. A small mistake, like a typo in wp-config.php, can cause errors.

Plugin-assisted migration offers speed and convenience. Tools like All-in-One WP Migration or Duplicator automate the process, packaging your site into a single file for easy transfer. This is an excellent choice for smaller sites (under 500MB) and users who aren’t comfortable with FTP or phpMyAdmin. However, these plugins can fail on larger sites due to server resource limits like PHP’s max_execution_time or memory_limit, which are often set low on shared hosting. Potential conflicts with other plugins or unusual server configurations can also create unexpected issues. The ‘pro’ versions of these plugins often include features specifically designed to circumvent these limits, such as chunked backups and direct server-to-server transfers, but they come at a cost.

Your choice depends on your priorities. For small, simple sites, a plugin is often the fastest and easiest route. For large, mission-critical, or highly customized sites, the reliability of the manual method is often worth the extra time and effort.

Final Approach and Landing: Post-Migration Essentials

Your files and database are on the new server, but the job isn’t done. These final steps are what make a migrate WordPress site project a true success, ensuring everything works perfectly and your SEO is protected. This is a core part of our WordPress Site Optimization process.

How to Migrate WordPress Site URLs and Fix Broken Links

If you changed your domain name or moved from a temporary URL, your database will still contain old links. Simply changing the site address in WordPress settings is not enough, as URLs are embedded throughout your content and settings.

WordPress stores some of this data in a serialized format, which is a way of storing complex data (like arrays or objects) as a string. This format includes the length of the string. A simple find-and-replace in a text editor will change the URL but not update the stored string length, which corrupts the data and breaks your site. The best solution is a database-aware tool. The Better Search Replace plugin is designed for this task. It correctly unserializes the data, performs the replacement, and then re-serializes it with the correct string lengths, preventing corruption.

Before making changes, always use the plugin’s “dry run” feature. This shows you what will be changed without actually doing it. Once you’re confident, run the replacement, changing your old URL (e.g., http://olddomain.com) to your new one (e.g., https://newdomain.com).

Updating DNS and Mitigating SEO Impact

Now, you’ll tell the internet where to find your site’s new home. This is done by changing your domain’s DNS (Domain Name System) records. Log into your domain registrar and update your domain’s nameservers to the ones provided by your new host (e.g., ns1.newhost.com and ns2.newhost.com). Nameservers are like the internet’s address book; you’re telling your domain to look for its address at the new host. Alternatively, if you only want to point your website and not your email, you can change the A Record to point to your new server’s IP address, but changing nameservers is usually simpler and recommended by hosts.

This change initiates DNS propagation, which can take up to 48-72 hours to complete globally. During this time, some visitors may see the old site and some the new. This is normal.

To protect your SEO:

• Implement 301 redirects if your URL structure has changed. This tells search engines the move is permanent and passes along link equity.
• For domain changes, use Google Search Console’s Change of Address tool to officially notify Google.
• Monitor Google Search Console for any new 404 (Not Found) errors and redirect them accordingly.

Migrating to a faster host can often improve your SEO, as page speed is a known ranking factor. This aligns with our goal to Fix Slow WordPress Website issues for our clients.

Thorough Post-Migration Testing

Once DNS has propagated, conduct a full audit of your site.

Frontend Testing (Visitor Experience):

• Navigation: Click through every link in your main menu, footer menu, and any sidebar navigation.
• Core Pages: Check your homepage, about page, contact page, and any other key pages.
• Content: Verify that all images, videos, and downloadable files (like PDFs) load correctly on various posts and pages.
• Links: Test a sample of internal links (linking to other pages on your site) and all critical external links.
• Forms: Submit every form on your site—contact forms, newsletter signups, search bars, and comment forms. Check that the submissions are received correctly.
• Responsiveness: Use your browser’s developer tools or a real device to check that the site looks and functions correctly on mobile phones and tablets.
• SSL/HTTPS: Ensure the padlock icon is present in the address bar on all pages, indicating a secure connection.

Backend Testing (Admin Functionality):

• Login: Log into the WordPress dashboard at /wp-admin.
• Content Creation: Create, edit, and save a new post and a new page. Test the block editor (Gutenberg) or classic editor functionality.
• Media Library: Upload a new image or file to the Media Library.
• Plugins & Themes: Check that all plugin and theme settings pages load correctly and that settings can be saved.
• Permalinks: Go to Settings > Permalinks and click “Save Changes” to regenerate your .htaccess file and ensure clean URLs are working.

E-commerce Testing (if applicable):

• Product Pages: View several product pages to ensure images, descriptions, and prices are correct.
• Add to Cart: Test adding products (including variable products) to the shopping cart.
• Checkout Process: Run a complete test transaction. Go through the entire checkout process, from entering customer details to processing a payment with a test gateway or a small live purchase.
• Order Confirmation: Verify that order confirmation emails are sent and received correctly.

This detailed testing, a key part of our WordPress Page Speed Optimization service, ensures your site is flawless after the move.

Frequently Asked Questions about WordPress Migration

Having managed hundreds of migrations at wpOncall, I’ve found that the same questions arise. Here are clear, practical answers to the most common concerns when you migrate WordPress site projects.

How long does a typical WordPress migration take?

The timeline depends on several factors. For most small-to-medium sites, the active migration work takes 1 to 4 hours. However, the total time is influenced by:

• Site Size: A large site with gigabytes of media will take much longer to upload than a small blog.
• Migration Method: Manual migrations are generally more time-consuming than using a plugin.
• Internet Speed: Your connection speed affects how quickly you can upload and download large backup files.

After the technical work is done, you must account for DNS propagation, which can take up to 48-72 hours for the change to be visible everywhere.

Will my website experience downtime during the migration?

One of the biggest fears is that your site will be offline for hours. With the right strategy, you can achieve a zero-downtime migration. The professional method involves these steps:

1. Keep the Old Site Live: Your current site remains fully operational and accessible to visitors throughout the process.
2. Work on a Temporary URL: The entire migration process (transferring files, importing the database, configuring, and testing) is done on the new server using a temporary address or by editing your local computer’s hosts file to preview the site on the new server before it’s live.
3. Thorough Testing: The migrated site is tested extensively in this private, “staging” environment.
4. Final DNS Switch: Only after the new site is confirmed to be working perfectly do you update the DNS records. During the DNS propagation period (up to 48 hours), traffic will be directed to either the old or new server, both of which are fully functional. This ensures no visitor ever sees a broken site. This approach guarantees a seamless transition with no service interruption.

What are common issues during a manual migration and how are they resolved?

Even with careful planning, you might encounter these common problems:

• Error Establishing a Database Connection: This almost always points to a typo in your wp-config.php file. Double-check the database name, user, password, and host. Also, confirm the user has full privileges on the database.
• 500 Internal Server Error: This is a generic error, meaning something went wrong on the server, but it can’t be more specific. Common causes after a migration include:
  • A misconfigured .htaccess file: This is a frequent culprit. Try renaming it to .htaccess_old via FTP to see if the site loads. If it does, go to Settings > Permalinks in your WordPress dashboard and click “Save Changes” to generate a fresh, correct .htaccess file.
  • PHP Memory Limit: The new server may have a lower PHP memory limit than the old one. You can try increasing it by editing your wp-config.php file or contacting your host.
  • PHP Version Mismatch: If your old server was running PHP 7.4 and the new one is on PHP 8.1, a plugin or theme might be incompatible. You can try switching the PHP version in your hosting control panel to match the old environment to see if that resolves the issue.
  • Corrupted Files: An incomplete or corrupted file transfer can also cause this error. Re-uploading the WordPress core files or the folder of a suspected plugin can help.
• Mixed Content Errors: This happens after moving to HTTPS if some resources (like images) still load over HTTP. Use a plugin like Better Search Replace to update all http:// URLs to https:// in your database.
• Broken Images or Missing Media: This usually means the wp-content/uploads folder didn’t transfer completely or has incorrect file permissions on the new server. Verify the transfer and check permission settings.
• Critical Error / White Screen of Death: This typically indicates a fatal PHP error, often from an incompatible plugin or theme. Enable WordPress debugging to see the specific error message. You can disable all plugins by renaming the plugins folder via FTP to isolate the cause.

For more complex issues, our WordPress Site Recovery Complete Guide offers in-depth solutions.

Do email accounts need to be migrated separately from the website?

Yes, absolutely. Website migration and email migration are two separate processes. Moving your WordPress files and database does not move your email accounts or messages.

To migrate your email, you must:

1. Create Email Accounts: Manually set up the same email addresses on your new hosting provider.
2. Migrate Existing Emails: Use an email client like Outlook or Thunderbird. Configure it to connect to both your old and new accounts via IMAP, then drag and drop messages and folders from the old server to the new one. Some hosts also offer email migration tools.
3. Update MX Records: In your domain registrar’s DNS settings, update the MX (Mail Exchanger) records to point to your new host’s mail servers. This ensures new emails are delivered to the correct place.

Conclusion

Moving your WordPress site is a systematic process that, when handled correctly, doesn’t have to be a source of stress. By breaking down the migrate WordPress site project into clear steps—backup, transfer, configuration, and testing—you can ensure a smooth transition to your new hosting environment.

We’ve covered the two primary paths: manual migration, which offers complete control and is ideal for complex sites, and plugin-assisted migration, which provides speed and convenience for smaller sites. Your choice depends on your site’s complexity and your technical comfort level.

Post-migration testing is non-negotiable. A site that looks fine on the surface can hide broken forms, a malfunctioning checkout process, or other critical errors that hurt your business. Following a comprehensive testing checklist, as outlined above, is the final, critical step to success. While DNS propagation can take up to 72 hours, this is a normal and temporary part of the zero-downtime migration process.

A successful migration should be invisible to your visitors. They should experience the same great site, only now delivered with the improved performance, security, and reliability of your new host.

For business owners who prefer to focus on their company instead of technical details, a professional service offers peace of mind. At wpOncall, we provide expert WordPress Site Migration services, guaranteeing a seamless, zero-downtime move. Our team handles every detail, from backup to comprehensive post-migration testing, allowing you to concentrate on what you do best: growing your business.