Recommended Free Tools
The safest way to move WordPress is to build and test the new server before changing public DNS. Back up the complete site, copy the files and database, preview the destination while visitors still reach the old host, then switch DNS and keep the old server available until the new copy is confirmed. This can reduce interruption substantially, but neither WordPress nor the sources below promise literally zero downtime or a universal DNS propagation time.
What a WordPress migration includes
A proper move includes the WordPress files and database. The files contain your uploads, themes, plugins and configuration; the database contains posts, pages, users, settings and other site data. Moving those does not automatically move separately hosted mailboxes, messages, DNS mail records or unrelated server services.
Keeping the same domain and URL structure makes the move simpler. WordPress documentation states: “If database and URL remain the same, you can move by just copying your files and database.” See WordPress’s migration documentation.
Before you copy anything: inventory and rollback
Record the details you will need to reproduce the site:
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match#1 Best Overall
- Current domain, document-root path and DNS provider.
- Database name, user, host and the PHP and database versions shown by the hosting panel.
- SSL configuration, caching or CDN settings, scheduled jobs and web-server rewrite rules.
- Where email is hosted and which non-WordPress services depend on the old server.
- Forms, shops, memberships, bookings or other features that receive new data.
Make a fresh copy of the WordPress directory and export the database before touching the destination. Keep one copy outside the old server, such as on a computer or external SSD, in addition to the host copy. WordPress recommends maintaining backups in both places (site-maintenance guidance).
Do not mistake Tools → Export for a full server backup. The WXR export covers content such as posts, pages, comments, custom fields, taxonomies and users, but not plugin or theme files, uploads or server configuration. It can help with content transfer, but it is not a replacement for a files-plus-database backup (Export screen documentation).
Prepare the new host without sending visitors there
Create the destination account, map the domain, create its database and establish a way to view the new copy while the public domain still resolves to the old server. Common options are a host-provided staging or temporary URL, a hosts-file override on your computer, or another preview method supplied by the provider. WordPress support guidance recommends verifying the new site before changing DNS (support discussion).
A migration service that connects from its own infrastructure may not be able to reach a destination visible only through your local hosts file. Check that limitation before choosing an automated service.
Rank #3
Confirm that the destination supports your site’s PHP, database and resource requirements. WordPress’s hosting guide points to current technical requirements and notes that some WordPress-focused hosts include backups, updates or developer tools.
Copy the files and database
- Upload the files. Put the complete WordPress directory, including
wp-content/uploads, themes, plugins andwp-config.php, in the destination document root. - Create and import the database. Create the destination database and import the SQL export. Preserve the original database and files as your rollback copy.
- Update connection settings. If the database name, user, password or host changed, edit those values in the destination
wp-config.php. A “database connection error” usually means checking both the credentials and the database hostname or access grant required by the new provider. - Keep URLs unchanged where possible. For a same-domain move, do not perform a search-and-replace merely because the server changed.
If the domain, protocol or installation path changes, stored URLs may need replacement. Use a WordPress-aware search-and-replace tool that handles serialized data and keep a database backup first. WordPress says such tools should generally be used instead of manual database edits and warns that multisite migrations require additional attention. Its guidance is available at Migrating WordPress.
Preview and test the destination
Open the new copy through the temporary URL, staging address or hosts-file method while the old site remains public. Work through the paths that matter to your visitors:
- Homepage, representative posts and pages, images, downloads and navigation.
/wp-admin, administrator login, user registration and password reset.- Search, contact forms, comments and email notifications.
- Checkout, memberships, bookings or other transaction flows.
- External APIs, webhooks, cron jobs and analytics integrations.
- HTTPS, redirects, canonical URLs and robots directives.
Check permalinks and rewrite rules. WordPress notes that, depending on the server configuration, .htaccess may need attention and permalinks may need to be re-saved when the site goes live. Apache, nginx and managed hosts use different rules, so follow the destination provider’s instructions rather than copying server directives blindly.
Plan for new writes
A database export is a snapshot. Comments, orders, bookings, form submissions and user registrations created afterward will not appear in that copy automatically. For a busy or transactional site, ask the host or migration specialist how they perform a final database sync, pause writes, or reconcile new records immediately before cutover. The exact method depends on your host and application.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choose a migration method deliberately
| Approach | What it can simplify | Questions to verify |
|---|---|---|
| Manual files and database move | Direct control over exports, configuration, preview and rollback. | Can you access the database, preserve permissions and test the destination before DNS? |
| Migration plugin | May package copying, backup and URL-handling steps. | Does it include the complete database and files, handle serialized data, support your site size and multisite, and provide a rollback? |
| Host-assisted migration | The provider may perform transfer and server configuration. | What is included, how is the destination previewed, and how are final writes, DNS and email handled? |
Learn WordPress lists Duplicator, Backup Migration and All-in-One WordPress Migration as examples to investigate (lesson). That list does not establish a best option, current limits, pricing or support for your particular site. Before relying on any tool, verify its size, runtime and access limits, URL-change behavior, multisite support, complete-backup coverage and recovery path.
Switch DNS only after validation
- Confirm the previewed destination passes your functional checks.
- Change the relevant DNS records or nameservers using your DNS provider’s and new host’s documented procedure.
- Keep the old host running and retain the original backup while visitors move between resolvers.
- Check the site from more than one network or DNS resolver, and monitor errors, SSL, redirects, email routing and important transactions.
DNS changes do not reach every visitor at one guaranteed instant. The available WordPress guidance does not establish a universal TTL or propagation duration, so do not promise a fixed number of minutes or hours.
Close out the migration safely
After the new server reliably serves the domain and key features work, create a new backup there and retain the pre-move copy according to your recovery policy. Keep the old account long enough to recover quickly if a missed integration or delayed DNS answer appears.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Handle email as a separate project
WordPress files and database do not automatically transfer mailboxes or messages. Determine whether mail is hosted by the old web host, a dedicated mail provider or another service, then handle its DNS records and mailbox migration separately. The WordPress support discussion explicitly distinguishes WordPress data from email accounts and email data.
Quick Recap
Common failure points
- Database connection error: recheck the destination database name, username, password, hostname and access permissions in
wp-config.php. - Images or downloads return 404: verify that uploads were copied and that the document root and permissions are correct.
- Permalinks fail: confirm the destination rewrite configuration and re-save the permalink settings after the site is live.
- Redirect loops or insecure assets: check HTTPS certificates, site URL values, proxy settings and forced-HTTPS rules.
- Recent orders or comments are missing: identify the time of the database snapshot and arrange a final sync or reconciliation.
- Mail stops working: inspect MX and related DNS records; web hosting migration and mailbox migration are separate tasks.
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.
