Alex Morgan
Alex Morgan
Senior Hosting Analyst
10+ years testing web hosting infrastructure. Benchmarks servers across 4 continents.

WordPress माइग्रेट कैसे करें 2026

Migrating a WordPress site to a new host is one of the most common maintenance tasks. and one of the most feared. Done correctly, you can move an entire WordPress installation (database, files, themes, plugins, and media) to a new host with zero downtime. Done carelessly, you risk data loss, broken links, or days of debugging. This guide walks through both the plugin method (fastest) and the manual method (most control).

हमने इन चरणों को कैसे सत्यापित किया

प्रकाशन से पहले अगर चरण होस्ट-विशिष्ट हैं तो कम से कम दो ब्रांड पर चलाते हैं. वरना एक ही स्टैक पर दो अलग दिन। कंसोल त्रुटियाँ, क्षेत्रीय UI अंतर और बटन खिसकने पर तुरंत कॉपी अपडेट करते हैं। पथ और स्क्रीनशॉट तिमाही में चेक। DNS/SSL/बिलिंग पर रिकवरी विकल्प सत्यापित करते हैं और आधिकारिक दस्तावेज़ लिंक करते हैं।

  1. 1

    Step 1: Choose your new host and set up the account

    Before migrating, ensure your new host is configured with PHP 8.2+ and MySQL/MariaDB. Create your hosting account, set up a database (note the name, username, and password), and confirm your new host's server address. SiteGround, Hostinger, and WP Engine all offer free migration services. Check if your new host will do it for you.

  2. 2

    Step 2: Back up your entire WordPress site

    Never migrate without a fresh backup. Use UpdraftPlus, Duplicator, or All-in-One WP Migration to create a complete backup of your files and database. Store the backup on your computer or cloud storage. not just on the same server you're moving away from. This backup also serves as your migration package.

  3. 3

    Step 3: Export your database

    If migrating manually: log in to your current host's phpMyAdmin, select your WordPress database, and click Export. Choose "Quick" export method and SQL format. Download the .sql file. If using a migration plugin (Duplicator or All-in-One WP Migration), this is handled automatically as part of the backup package.

  4. 4

    Step 4: Transfer WordPress files to the new host

    For manual migration: use FTP/SFTP (FileZilla is free and excellent) to upload all WordPress files to your new host's public_html directory. This includes the wp-content folder (themes, plugins, uploads) and all core WordPress files. For plugin migration: install the migration plugin on your new host and import the backup package from Step 2.

  5. 5

    Step 5: Import the database to the new host

    Log in to your new host's phpMyAdmin, select the empty database you created, and click Import. Upload the .sql file from Step 3. After import, update the wp_options table: change siteurl and home values to your domain (or temporary staging URL if testing first).

  6. 6

    Step 6: Update wp-config.php

    Edit the wp-config.php file on the new server to update the database connection details (DB_NAME, DB_USER, DB_PASSWORD, DB_HOST) to match your new database credentials. If testing on a temporary staging URL, also update the site URL constants if they were hardcoded.

  7. 7

    Step 7: Test on a staging URL before switching DNS

    Before pointing your live domain to the new host, test by temporarily editing your computer's hosts file to preview the new site. Alternatively, use a temporary staging URL if your new host provides one (SiteGround and WP Engine both do). Check all pages, forms, and checkout (if WooCommerce) work correctly.

  8. 8

    Step 8: Point your domain to the new host

    Update your domain's nameservers (at your domain registrar) to your new host's nameservers. DNS propagation takes 1–48 hours globally. During this time, some visitors may see the old site and some the new. Your old host's site remains live during propagation, so no data loss occurs if both are in sync.

1
SiteGround Fastest
Revenue-critical sites are where SiteGround earns the premium: Google Cloud, SuperCacher, and support that actually reads the ticket before replying.
★★★★½
✓ फ़ायदे
  • Staging, backups, and PHP version options on SiteGround match our screenshots.
  • High uptime, steady response times on their Google Cloud setup.
  • Staging and daily backups on every plan.
✕ नुकसान
  • SiteGround menu labels change. Look for the idea, not one fixed menu path.
  • No free domain included.
मूल्य/माह$3.99
स्टोरेज10 GB SSD
मुफ़्त डोमेन✕ नहीं
अपटाइम99.99%
2
Hostinger Top Pick
Hostinger has survived multiple yearly cycles on our bench: LiteSpeed, hPanel, and sub-$3 intro pricing still deliver the best overall value for most sites we migrate.
★★★★½
✓ फ़ायदे
  • Staging, backups, and PHP version options on Hostinger match our screenshots.
  • Fast LiteSpeed loading, consistent in our repeated tests.
  • Good storage, SSL, and backups on entry plans, no forced add-ons at login.
✕ नुकसान
  • Hostinger menu labels change. Look for the idea, not one fixed menu path.
  • No phone support on any plan.
मूल्य/माह$2.99
स्टोरेज100 GB SSD
मुफ़्त डोमेन✓ हाँ
अपटाइम99.9%

अक्सर पूछे जाने वाले प्रश्न

Will my WordPress site go down during migration?+
Not if you follow the staging approach. Set up the new host, test thoroughly, then switch DNS. Your old site remains live throughout, so visitors experience minimal to zero downtime. The only potential gap is during DNS propagation (0–48 hours).
How long does WordPress migration take?+
For a typical 5–10 GB site: 1–3 hours for the full manual process, or 30–60 minutes using a migration plugin. Large WooCommerce stores or sites with gigabytes of media uploads take longer.
Do I need a migration plugin or can I do it manually?+
Both methods work. Migration plugins (Duplicator, All-in-One WP Migration) are faster and less error-prone for most users. Manual migration gives more control and is better for complex configurations or when the plugin has size limitations.
Will my site's SEO be affected by migration?+
Not if you preserve your URL structure and set up 301 redirects for any changed URLs. Use a permalink structure check after migration. If your domain name is unchanged, Google will continue to index your site normally after it discovers the new server location.