To move WordPress to a new host safely, copy both the site files and database, test the copy on the new server, and switch DNS only after it works. If you keep the same domain, you usually do not need to replace site URLs, but you still need to point the domain to the new host. If you change the domain or URL path, plan a serialization-safe URL update and redirects.
Choose a migration method
The right route depends on how much control you want and what your new host supports. Whichever method you choose, retain a separate backup before starting.
| Route | Best fit | Important limits |
|---|---|---|
| Host migration tool or assisted service | You want the new provider to handle some or all of the transfer. | Check the host’s current eligibility, plan, and compatibility requirements. WordPress.com, for example, documents a full-site migration workflow and an assisted service that usually takes 2–3 business days; that estimate applies to its service, not migrations generally. WordPress.com migration guide |
| Migration plugin | You want an export/import workflow without manually moving files and database tables. | Follow the plugin’s current instructions and check restrictions such as file size and compatibility. Learn WordPress names Duplicator, Backup Migration, and All-in-One WordPress Migration as examples to explore, not as a comparative endorsement. Learn WordPress migration lesson |
| Manual files-and-database move | You need direct control or the host’s tools require a manual transfer. | You will need to transfer files, export and import the database, and configure the destination’s database settings. The cPanel example uses phpMyAdmin and FTP; other hosts may use different interfaces. WordPress handbook: Moving WordPress · cPanel: Move a WordPress installation |
A WordPress content XML export/import is not a full-site migration: by itself it does not reproduce the complete installation, database configuration, theme, or plugin setup.
1. Inventory the site and make a complete backup
Before changing anything, record the current site URL and identify the accounts and settings you may need: the old and new hosting accounts, the domain registrar or DNS provider, database name and user, email setup, plugins, themes, and any unusual configuration.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minute#1 Best Overall
- Back up the full WordPress directory and the database. The WordPress handbook recommends preserving both before moving servers.
- Keep a copy somewhere separate from the old server. Learn WordPress recommends storing a plugin export on an external drive.
- If the site gets orders, registrations, comments, or frequent edits, plan a content freeze or final synchronization. An export is a snapshot; changes made after it is created are not automatically included in the imported copy.
See the WordPress moving guide and Learn WordPress migration lesson for the backup context.
2. Prepare the new host
Create the destination hosting account and site. Confirm that the host supports the site’s PHP and database requirements, then locate its file manager, database tool, and DNS controls. If you are using a host migration service or plugin, check its current instructions and any plan, file-size, or compatibility restrictions before you begin.
For a manual cPanel-style move, create a database at the destination and import the source SQL export. Then update the database values in the destination wp-config.php file: DB_NAME, DB_USER, and DB_PASSWORD. The exact interface varies by host. The cPanel instructions illustrate one approach.
Provider workflows can have specific requirements. WordPress.com’s documented migration, for example, requires a fresh destination site on a paid plan and notes that some source configuration edits do not transfer. Check the current WordPress.com migration guide if that is your destination.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →3. Copy the files and database
Using a migration plugin
Install and run the chosen plugin on the source site, export the site as directed, and download the export. Use the plugin’s destination-side process to import it into the prepared site. Keep the separate backup copy you made in step 1; an export file on its own should not be your only recovery copy.
Moving files and database manually
- Export the source WordPress database as an SQL file using the database tool available on the old host.
- Copy the WordPress files to the new host, preserving the directory structure. FTP and a host file manager are examples of transfer methods.
- Import the SQL file into the destination database.
- Set the destination database name, username, and password in
wp-config.php.
The WordPress handbook and cPanel guide describe these file-and-database steps.
4. Decide whether WordPress URLs need to change
If the domain and URL paths stay the same
When the public URLs remain unchanged, the WordPress handbook says the move may be made by copying the files and database. Update wp-config.php if the destination database name or user differs. You will still need to direct the domain to the new host after testing the copy.
If the domain or URL path changes
Old URLs can remain in database content and settings. Do not run a naive database-wide search-and-replace: themes and widgets may store serialized values whose length information can be damaged by a plain replacement. WordPress recommends a serialization-aware method, such as WP-CLI’s search-replace command or a suitable plugin, and making a backup first. See WordPress’s URL-change guidance.
Recommended Free Tools
Map old public addresses to their new destinations and configure permanent redirects where appropriate. A 301 redirect tells browsers and search engines that a page has permanently moved and can send visitors from an old URL to the replacement. The Learn WordPress migration lesson explains the redirect role.
5. Test the new site before changing DNS
Preview the destination using the host’s temporary address, staging feature, or another safe preview method. Check the site before directing public traffic to it:
- Open the home page and representative posts or pages.
- Check images and other media, internal links, and any forms.
- Test the login and WordPress administrator access.
- Confirm permalinks and theme/plugin behavior.
- Test site-specific features such as checkout, memberships, or registrations if applicable.
Old media links and permalink rewrite settings may need attention after a move. If the source used a temporary URL, complete the appropriate final URL replacement before cutover. WordPress’s moving guide and WordPress.com’s migration checklist cover these kinds of checks.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.6. Point the domain to the new host and protect email
After the destination passes your checks, update the domain’s nameservers or the DNS records specified by the new host. Make the change at the account that controls the domain. Nameservers tell DNS where the site is hosted; if you keep the same domain, this DNS change is still needed to send visitors to the new server.
Free tools Windows power users keep installed
One-click scans. No signup required.
Best Value
DNS changes do not take effect everywhere at once. Learn WordPress gives a typical propagation estimate of 24–48 hours and says it can sometimes take up to 72 hours; the timing varies and is not a guaranteed deadline. See its migration lesson.
Before cancelling the old hosting account, confirm how domain email is handled. Email may be tied to the old host, and the new email service may require its own DNS records. Some hosts may migrate email accounts, but confirm what your specific provider includes. Learn WordPress identifies email as a separate migration consideration in its migration lesson.
7. Verify the live site and close out carefully
Once traffic is reaching the new host, repeat the important checks on the live domain. Verify forms, media, redirects, and SSL, then review administrator access, plugins, premium theme or plugin licenses, and the site’s canonical content URLs. WordPress.com’s post-migration checklist calls out these closeout tasks.
Keep the old hosting account and your backup until the new site and email have been verified. The safe retention period depends on your site and host; no single duration applies to every migration.
Quick Recap
Common migration mistakes to avoid
- Copying only the database or only the files: a full move needs both.
- Switching DNS before testing: validate the destination first so visitors are not sent to an unfinished copy.
- Replacing URLs with a plain database-wide operation: serialized values can break; use a serialization-aware method.
- Forgetting changes made after export: freeze updates or synchronize the final content before cutover.
- Closing the old host without checking email: mail service and DNS records may be separate from the website transfer.
- Leaving the
RELOCATEconstant enabled: WordPress warns this can be insecure because, in some configurations, it allows an attacker to change the site URL. Remove it when it is no longer needed. WordPress handbook
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
