Section 3: Host Configuration & Data Import

With your database export and site files securely saved on your computer, the next phase is setting up the destination server. When you migrate your wordpress website, configuring the receiving environment accurately ensures that your database connects without permission errors and your site files execute cleanly.

Step 1: Creating a New MySQL Database and User on the Destination Server

Before uploading your exported SQL data, you must provision a fresh, empty MySQL database and assign a database user with full privileges on the new web host.

1. Provisioning the Database via MySQL Database Wizard

1. Log into your new hosting account’s control panel (cPanel, Plesk, or custom dashboard).

2. Locate the Databases section and open MySQL Database Wizard (or MySQL Databases).

3. Enter a new database name (e.g., db_wpnew)and click Next Step.

4. Create a new database username (e.g., usr_wpnew).

5. Generate a strong, secure password using the built-in password generator.

   • Critical Note: Save the database name, database username, and database password in a temporary text file on your local machine. You will need these credentials in a later step.

-- Conceptual MySQL setup on destination host
CREATE DATABASE db_wpnew CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
CREATE USER 'usr_wpnew'@'localhost' IDENTIFIED BY 'Strong_Generated_Password';
GRANT ALL PRIVILEGES ON db_wpnew.* TO 'usr_wpnew'@'localhost';
FLUSH PRIVILEGES;

2. Assigning User Privileges

In the privilege assignment screen, check the box for ALL PRIVILEGES to grant your new user full access to read, write, and alter tables in the database. Complete the wizard to save the database structure. Assigning full database privileges ensures your connection strings work immediately after you migrate your wordpress website.

Step 2: Importing the Database File via phpMyAdmin

Now that your destination database is active and empty, you can populate it with your original site data. Importing your SQL dump restores all your published content, user profiles, and site settings when you migrate your wordpress website.

1. Uploading the SQL Export

1. Return to your hosting panel and open phpMyAdmin.

2. Select your newly created database (db_wpnew) from the left-hand menu.

3. Click on the Import tab in the top navigation bar.

4. Under File to Import, click Choose File and select your saved .sql or compressed .sql.gz file from your local computer.

5. Leave the format dropdown set to SQL and keep default settings intact.

6. Scroll down and click Import (or Go).

Depending on your database size, the upload process may take a few seconds to a few minutes. Once complete, phpMyAdmin will display a green success banner indicating that all tables were imported successfully. A successful SQL import completely restores your post hierarchy when you migrate your wordpress website.

Step 3: Uploading and Extracting Site Files to public_html

With the database populated, the next step is placing your physical site assets into the root folder of your new host. To migrate your wordpress website efficiently, uploading a single compressed .zip archive via File Manager is much faster than uploading loose files over FTP.

1. Uploading the Zip Archive via File Manager

1. Open File Manager in your new host’s panel and navigate to the domain root directory (usually public_html).

2. If any default host files exist (such as index.html or default.php), delete them to keep the directory clean.

3. Click Upload in the top bar, choose your site-backup.zip file, and wait for the upload progress bar to hit 100% and turn green.

2. Extracting Files on the Server

1. Select site-backup.zip inside public_html.

2. Click Extract in the top toolbar and confirm the target path as /public_html.

3. Once extraction finishes, verify that core folders (wp-content, wp-admin, wp-includes) are located directly inside public_html and not nested inside a subfolder.

4. Delete the remaining site-backup.zip file to save server disk space.

Verifying root directory alignment is critical after uploading files to migrate your wordpress website.

Step 4: Reconfiguring wp-config.php Credentials

At this point, your new server holds your database and site files, but they are not connected to each other yet. Your imported wp-config.php file still contains the old host’s database credentials. Updating this configuration is a vital step when you migrate your wordpress website manually.

1. Editing Database Credentials

1. In public_html, locate wp-config.php, right-click it, and select Edit.

2. Locate the MySQL settings section and replace the old values with your new destination server database details:

// ** Database settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
define( 'DB_NAME', 'db_wpnew' );

/** MySQL database username */
define( 'DB_USER', 'usr_wpnew' );

/** MySQL database password */
define( 'DB_PASSWORD', 'Strong_Generated_Password' );

/** MySQL hostname */
define( 'DB_HOST', 'localhost' );

Note: On most hosting providers (cPanel, SiteGround, Bluehost, Namecheap), DB_HOST remains 'localhost'. However, if you are using specialized hosts or third-party cloud databases (like AWS RDS), replace 'localhost' with the specific database server IP or hostname provided by your host.

2. Updating Security Salt Keys (Optional Best Practice)

To enhance site security after you migrate your wordpress website, you can update your security authentication keys inside wp-config.php. This automatically invalidates existing active sessions and forces all users (including potential unauthorized sessions) to log in freshly on the new host. Invaliding old login sessions protects your admin dashboard right after you migrate your wordpress website.

Step 5: Handling Domain or URL Changes (Database Search and Replace)

If you are transferring your site to a new hosting provider while keeping the exact same domain name, you do not need to alter database URL references. However, if you migrate your wordpress website to a new domain name or staging URL, you must update serialized URL strings across your database tables.

Why SQL Queries Break Serialized Data

Running a basic SQL UPDATE statement directly on serialized WordPress data (such as widget configurations or theme customizer values) will break serialized strings because character counts will no longer match the string length declarations.

Using WP-CLI or Search-Replace Scripts

To safely handle domain updates:

• Option A (WP-CLI): If SSH access is available on your new server, run:

  wp search-replace '[http://olddomain.com](http://olddomain.com)' '[https://newdomain.com](https://newdomain.com)' --skip-columns=guid

• Option B (Better Search Replace Plugin): If you prefer a visual interface, wait until DNS points to the new host, install the Better Search Replace plugin, and execute a safe database search and replace. Updating serialized database strings properly guarantees smooth navigation when you migrate your wordpress website to a new domain.

Step 6: Verifying File Permissions on the Destination Server

Incorrect file permissions after extraction can cause 500 Internal Server Errors or prevent image uploads. Ensure your server applies standard WordPress permissions:

• Directories / Folders: Set to 755 or 750.

• Files: Set to 644 or 640.

• wp-config.php: Set to 600 or 640 for elevated security protection.

Checking these permission flags completes your host setup phase. You now have a fully assembled duplicate of your site residing on the destination server, ready for testing before turning live traffic toward it. Setting standard 755 and 644 file permissions prevents 500 internal server errors when you migrate your wordpress website.

Section 4: Testing & Zero-Downtime Cutover

Before pointing your live traffic to the new server, comprehensive testing and a seamless cutover plan are essential. When you migrate your wordpress website, skipping the validation phase can lead to broken links, database mismatches, or unexpected downtime. Follow this structured approach to test your staging site thoroughly and execute a zero-downtime cutover.

1. Testing the Staging Environment via Hosts File or Temporary URL

Before updating your public DNS, you must inspect the migrated site on the new server without affecting live visitors.

• Option A: Edit Your Local Hosts File: Map your domain name directly to the new server’s IP address on your local computer (/etc/hosts on Linux/macOS or C:\Windows\System32\drivers\etc\hosts on Windows). This lets your browser load the new site while the rest of the world continues to see the old host.

• Option B: Temporary URL / Staging Link: Some hosting providers supply a temporary staging URL. If you choose this method to migrate your wordpress website, remember to update your database URLs back to the primary domain before public launch.

Key Elements to Verify During Testing:

• Navigation & Permalinks: Click through key pages, blog posts, and category archives to verify that internal linking works seamlessly without 404 errors.

• Forms & eCommerce Functionality: Test contact forms, user logins, and checkout processes to ensure mail servers and payment gateways connect properly.

• Media & Uploads: Confirm that all images, PDF attachments, and custom assets render correctly from the new server’s upload directory.

Verifying form connectivity on a local host mapping ensures total reliability before you migrate your wordpress website live.

2. Lowering TTL (Time To Live) Before DNS Cutover

To prepare for a smooth cutover when you migrate your wordpress website, lower the Time To Live (TTL) value of your domain’s A record (or CNAME) at your DNS provider (e.g., Cloudflare, Namecheap, or GoDaddy).

• Reduce TTL to 300 seconds (5 minutes) at least 24 to 48 hours prior to the migration.

• This ensures that when you update your IP address, internet service providers (ISPs) worldwide refresh their DNS cache almost instantly, drastically reducing propagation lag.

3. Executing the Zero-Downtime DNS Cutover

Achieving true zero-downtime requires keeping both the source and destination environments active during DNS propagation.

1. Put the Old Site in Read-Only Mode (Optional): If your site accepts user comments, orders, or data submissions, briefly enable maintenance mode or restrict database writes on the old server right before updating DNS.

2. Update DNS Records: Point your domain’s A Record to your new server’s IP address (or update the Nameservers if you are using your new host’s DNS infrastructure).

3. Dual-Server Monitoring: As DNS propagates globally, traffic will gradually shift from the old server to the new one. Because both servers host identical files and database structures, visitors will experience zero interruption regardless of which server their ISP routes them to.

4. Final Post-Cutover Auditing & Cleanup

Once DNS propagation is complete across major global resolvers, perform a final round of checks to finalize the process.

• Clear All Caching Layers: Flush server-side caches (Redis/Memcached), CDN caches (Cloudflare), and WordPress caching plugins (e.g., WP Rocket, LiteSpeed) so updated files serve properly.

• Re-verify SSL/TLS Certificates: Ensure your HTTPS certificate is active on the new server and that force-HTTPS redirects are active without mixed-content warnings.

• Decommission the Old Hosting Account: Keep the old server running for 48–72 hours as a backup. Once you are 100% confident that traffic has shifted completely, cancel the old subscription to finalize the decision to migrate your wordpress website.

By following these steps carefully whenever you plan to migrate your wordpress website, you guarantee a reliable transition that preserves user experience, SEO standings, and backend integrity. Knowing how to migrate your wordpress website without dropping a single visitor is the ultimate benchmark of a successful migration strategy.

Section 5: Post-Migration Audit & FAQs

Completing the technical transfer and DNS cutover is a major milestone, but a thorough post-migration audit guarantees that your site maintains peak performance and search visibility. Taking time to verify indexability, clean up temporary configurations, and monitor error logs after you migrate your wordpress website protects your search engine rankings and ensures a smooth user experience.

Post-Migration Optimization and Maintenance Audit

After DNS propagation settles and traffic flows to the new host, complete these essential maintenance tasks to optimize your environment:

• Flush and Re-arm Caching Systems: Re-enable your preferred caching plugins (e.g., LiteSpeed Cache, WP Rocket, or W3 Total Cache). Purge all server-level object caches (Redis or Memcached) and clear your CDN edge cache to ensure visitors receive fresh assets.

• Resave Permalink Structures: In your WordPress dashboard, navigate to Settings > Permalinks and click Save Changes without making any edits. This action flushes and rewrites your .htaccess rules, resolving potential 404 errors on internal pages.

• Audit Broken Links and Media Paths: Run a crawl using tools like Screaming Frog or a link-checker plugin to verify that internal images, canonical tags, and hyperlinked resources load correctly over HTTPS.

• Inspect Google Search Console (GSC): Monitor your Google Search Console coverage report over the first 48 to 72 hours. Check for spikes in 5xx server errors or 404 response codes to verify that search engine bots crawl your new host without friction.

Performing these post-transfer checks ensures that when you migrate your wordpress website, your site remains fully indexable and structurally sound. Executing a post-transfer Search Console crawl confirms search engine indexability immediately after you migrate your wordpress website.

Frequently Asked Questions (FAQs)

Q. How long does a manual WordPress site migration take?

A manual migration typically takes between 30 to 60 minutes for small to medium-sized sites. The exact duration depends on your media library size, internet connection speed, and database file size. Allowance for full global DNS propagation (which can take 1 to 24 hours depending on your TTL settings) should also be factored in.

Q. Will executing a manual migration affect my SEO rankings or traffic?

If performed using a zero-downtime strategy with proper 301 redirects, identical URL structures, and valid SSL setup, manual migration will not negatively impact your SEO rankings or organic traffic. Maintaining server response speeds and resolving any post-migration crawl errors quickly protects your existing search engine index.

Q. What should I do if I see an “Error Establishing a Database Connection”?

This error indicates that WordPress cannot connect to MySQL using the parameters stored in wp-config.php. To fix it:

1. Open wp-config.php and verify that DB_NAME, DB_USER, DB_PASSWORD, and DB_HOST match your destination server credentials.

2. Ensure your database user is assigned to the database with ALL PRIVILEGES.

3. Verify that the MySQL database service is running on your destination web host.

Q. Why is a manual migration better than using a migration plugin?

While plugins work well for small, simple sites, manual migration gives you complete control over raw files and database exports. It eliminates server execution timeouts, memory limit crashes, and incomplete file transfers making it the safest method to migrate your wordpress website when dealing with large databases or high-traffic blogs.