Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
You can move a live WordPress site with no planned outage by building a complete copy at the new host, testing it privately, synchronizing new database changes immediately before cutover, and then changing DNS while the old host remains available. “No downtime” is an operational goal: DNS caches and individual resolvers do not switch at exactly the same moment, so keep the original site online until the new destination is verified.
The migration includes two inseparable parts—your WordPress files and your database. Treat the first copy as a staging version, decide which site is authoritative during the switch, and retain a tested rollback path.
What a no-downtime WordPress migration actually involves
A host migration changes where the existing domain is served; it does not normally require reinstalling WordPress. The official WordPress Advanced Administration Handbook states: “Whether you are moving WordPress to a new server or to a different location on your server, you don’t need to reinstall.” For a move where the domain and URLs stay the same, its guidance is that “If database and URL remain the same, you can move by just copying your files and database.”
During the project, the old host continues serving visitors while you prepare the destination. You privately inspect the new copy, complete a final database synchronization for any new comments, orders, form entries, or edits, and only then point web DNS at the destination. Some users may still reach the old server while their resolver cache expires; that is propagation, not an intentional outage.
#1 Best Overall
- Slim durable design to help take your important files with you
- Vast capacities up to 6TB[1] to store your photos, videos, music, important documents and more
- Back up smarter with included device management software[2] with defense against ransomware
- Help secure your important files with password protection and hardware encryption
- 3-year limited warranty
- Files: the WordPress core, themes, plugins, uploads, custom code, and other files in the site directory.
- Database: posts, pages, settings, users, orders, comments, plugin data, and other dynamic content.
- Configuration: database credentials in
wp-config.php, PHP/runtime settings, scheduled tasks, SSL, redirects, and any host-specific rules. - DNS: the records that direct the domain to the web server. Mail records may be hosted separately and must not be overwritten accidentally.
A static brochure site may have no meaningful writes between copies. A store, membership site, newsroom, or form-heavy site does; those sites need an explicit write-freeze or final-sync procedure.
Before copying anything: inventory access and risk
Make a migration checklist and identify the people who can approve the DNS change. Confirm that you can sign in to all of the following:
- WordPress administration and the current hosting account.
- The new hosting account, its site root, database, and file-transfer method.
- The authoritative DNS provider, including permission to edit the web records.
- Your domain registrar if DNS delegation might need changing.
- External services such as transactional email, payment gateways, CDN, analytics, object storage, or security tools.
Record the current PHP/runtime version, database engine and version, enabled extensions, web-server rules, storage usage, cron or scheduled-task definitions, SSL certificate arrangement, redirects, and any custom configuration outside the WordPress directory. Check the new host against that inventory before importing. A plugin that depends on a missing PHP extension or a different database setting can fail even when the files and database copied correctly.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Classify the site’s write activity. List every feature that can change data after the first copy: checkout and orders, subscriptions, registrations, comments, contact forms, bookings, uploads, and editorial changes. Decide who may edit the old site and when those edits stop. If you cannot briefly freeze writes, plan a final export or database synchronization close to DNS cutover.
Make and protect a restorable backup
Take a complete backup before altering either server. WordPress’s migration guidance explicitly calls for backing up the WordPress directory, images, plugins, other files, and the database. Keep an untouched copy separate from the working files you will import.
Back up the files
- Archive the entire WordPress installation, not just
wp-content. Includewp-config.php, uploads, custom themes, plugins, and server rules such as.htaccesswhere applicable. - Preserve file names, directory structure, and permissions as far as the destination permits.
- Store a second copy outside the current host; an external drive is an optional location, not a requirement.
Back up the database
- Export every table belonging to the site, including tables created by plugins.
- Keep the export in its original form and note its date, database name, character set, and table prefix.
- Open or validate the archive so a failed download is not discovered during an emergency restore.
Do not delete the old site or its backup after the first successful page load. A rollback is only practical while the original files, database, and hosting account remain intact.
Rank #2
- 【Plug-and-Play Expandability】 With no software to install, just plug it in and the drive is ready to use in Windows（For Mac，first format the drive and select the ExFat format.
- 【Fast Data Transfers 】The external hard drives with the USB 3.0 cable to provide super fast transfer speed. The theoretical read speed is as high as 110MB/s-133MB/s, and the write speed is as high as 103MB/s.
- 【High capacity in a small enclosure 】The small, lightweight design offers up to 500GB capacity, offering ample space for storing large files, multimedia content, and backups with ease. Weighing only 0.35 Lbs, it's easy to carry "
- 【Wide Compatibility】Supports PS4 5/xbox one/Windows/Linux/Mac and other operating systems, ensuring seamless integration with game consoles,various laptops and desktops .
- Important Notes for PS/Xbox Gaming Devices: You can play last-gen games (PS4 / Xbox One) directly from an external hard drive. However, to play current-gen games (PS5 / Xbox Series X|S), you must copy them to the console's internal SSD first. The external drive is great for keeping your library on hand, but it can't run the new games.
Prepare the destination host
Create the destination site root and an empty database before transferring content. Confirm storage, PHP/runtime compatibility, database limits, SSL support, and the ability to create scheduled tasks. If the host supplies a migration service or plugin, treat it as a transfer mechanism rather than proof that custom configuration has been handled.
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 reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteImport the files and database
- Transfer the complete WordPress directory to the destination site root using the host’s supported file-transfer method.
- Import the database backup into the destination database.
- Open the destination copy of
wp-config.php. If the database name, user, password, host, or table prefix differs, update those values for the new database. Do not change credentials on the old host. - Check that the web server’s document root points to the directory containing
wp-admin,wp-content, andwp-includes. - Install or activate the destination SSL certificate and reproduce required redirects and rewrite rules.
For a pure host move, leave the existing home and siteurl values unchanged. Changing URLs merely to preview a copy creates extra replacement work and can make the eventual cutover harder.
Host-assisted and plugin migrations
A migration plugin or host-assisted service can package files and database data, which may be useful when you do not have shell or database expertise. Verify what it transfers: custom cron jobs, server rules, email configuration, large media libraries, and external integrations may still require manual work. Do not assume a service is free or that it handles every custom setup.
WordPress.com’s documented importer is a platform-specific example. Its instructions require a fresh paid-plan destination and warn that importing replaces the destination’s contents. Those conditions do not automatically apply to other hosts, but they illustrate why you should read the destination’s import rules before starting.
Preview the new server before changing public DNS
Use the destination’s staging feature when available. Otherwise, preview the new server from your own computer with a hosts-file override. The override maps your real domain to the destination IP only on that computer; public visitors continue reaching the old host.
Hosts-file procedure
- Obtain the destination server’s public IP address from the new host.
- Back up your current hosts file.
- Add one line containing the destination IP, a space, and the real hostname, for example
203.0.113.10 www.example.com example.com. Replace the example IP and domain with your actual values. - Save the file with administrator privileges. On Windows it is commonly at
C:WindowsSystem32driversetchosts; on macOS and Linux it is commonly/etc/hosts. - Flush the local DNS cache if your operating system or browser continues using the old address.
- Open the site in a private browser window and test it as a visitor and as an administrator.
Remove the override after testing. Leaving it in place can make you believe the public DNS switch has happened when only your computer is using the destination.
Rank #3
- Slim durable design to help take your important files with you
- Vast capacities up to 6TB[1] to store your photos, videos, music, important documents and more
- Back up smarter with included device management software[2] with defense against ransomware
- Help secure your important files with password protection and hardware encryption
- 3-year limited warranty
Functional test checklist
- Home page, representative posts and pages, category or search pages, menus, and pagination.
- WordPress login, administrator screens, media uploads, and the editor.
- Images, downloads, embedded media, and any protected content.
- Contact, registration, booking, and other forms, including confirmation messages and email delivery.
- Cart, checkout, account pages, payment callbacks, and order creation if the site sells anything.
- HTTPS, canonical URLs, redirects, robots directives, XML sitemaps, and mixed-content warnings.
- Scheduled tasks, background queues, webhooks, and third-party API connections.
- Destination access and error logs while you exercise the site.
Test from a fresh browser session so cached assets and cookies from the old host do not hide errors. Compare key records, such as the newest order or form submission, with the source site before approving the switch.
Handle new comments, orders, and edits before cutover
The first database export becomes stale as soon as the live site accepts another comment, order, registration, form submission, upload, or editorial change. Running the DNS change without addressing those writes can make the newest data disappear from the destination.
Choose an authority window
- Short write freeze: announce a brief period when editors stop publishing and users cannot submit forms or orders. This is the simplest approach.
- Final export and import: keep the old site serving, stop or pause writes, export the database again, and import that fresh export into the destination.
- Incremental synchronization: use a host-supported or administrator-managed method to synchronize changes. Confirm exactly which tables and files are included.
HostPanel’s 4 August 2026 migration guidance recommends a fresh export immediately before a DNS switch for sites with ongoing writes. It also advises avoiding edits on both copies during the transition. Coordinate the freeze, final sync, and DNS change as one timed operation, and record the timestamp of the last accepted write.
Keep the copies consistent
After the final synchronization starts, do not publish on the old copy and then continue editing the new copy independently. If an emergency change is unavoidable, record it and apply it to the authoritative copy only after confirming which server is receiving the request. Keep the old host online as a read-only fallback where your application allows it.
Lower DNS TTL and switch records carefully
A lower time-to-live (TTL) can reduce how long some resolvers retain the old web address, but it cannot force every resolver to refresh simultaneously. HostPanel suggests lowering the relevant web-record TTL 24–48 hours before the move and uses 300 seconds as an example target. Those are that publisher’s recommendations, not a universal propagation schedule.
Prepare the DNS change
- Identify the authoritative DNS provider and list the records currently used for the website.
- Lower the TTL on the web records you will change, such as the apex and
wwwaddress records, if the provider permits it. - Do not remove mail records. Preserve MX, SPF, DKIM, DMARC, and other service records when DNS is separate from web hosting.
- Confirm the destination IP or target hostname and the exact records that must change.
Perform the cutover
- Complete the final write freeze or database synchronization.
- Change only the records needed to send web traffic to the destination.
- Record the change time, previous values, new values, and the person who made the edit.
- Keep the old host and its database available while caches expire and verification continues.
Do not cancel the old hosting account immediately. Some users and monitoring systems may still resolve the old address for a while, and the old server is your fastest rollback if the destination has a serious defect.
Rank #4
- Slim durable design to help take your important files with you
- Back up smarter with included device management software[2] with defense against ransomware
- Help secure your important files with password protection and hardware encryption
- 3-year limited warranty
Verify the live destination and retain rollback
Check the site from more than one network or DNS resolver after changing records. Test a mobile connection or another independent network in addition to your normal office or home connection. Confirm that the expected pages, forms, transactions, SSL certificate, redirects, and background jobs work on the destination.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →- Review web-server, PHP, database, and application logs for new errors.
- Check that the newest record created during the final synchronization is present.
- Watch payment, email, webhook, and monitoring dashboards for failed callbacks.
- Compare the resolved address from several resolvers with the destination address.
- Keep backups and the original host until the site has remained stable for a period appropriate to its traffic and your hosting agreement.
If the destination fails, restore the previous DNS values while the old site is still intact, then diagnose the destination privately. A rollback does not repair data written to the wrong copy, so preserve the cutover log and reconcile any transactions before reopening writes.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.When the domain or URL changes too
A host-only move keeps the domain and URLs unchanged. If the domain name or URL path changes as well, add a separate URL-migration plan. Old URLs can remain in post content, serialized plugin settings, menus, widgets, theme options, and media references.
WordPress warns that a naïve database-wide text replacement can damage serialized data because the stored string length is part of the value. Use a serialization-aware search-and-replace tool, test on a copy, and verify pages, media, menus, redirects, feeds, and canonical links.
The WordPress migration handbook gives this WP-CLI example:
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemswp search-replace 'example.dev' 'example.com' --skip-columns=guidReplace both domains with your actual old and new values, confirm the correct database is selected, and run a dry run or equivalent preview when available. The --skip-columns=guid option is shown in the handbook’s example; it is not a reason to paste the command unchanged into every migration.
Best Value
- High-capacity external hard drive with up to 2TB of storage The ModusTech Facet portable external hard drive gives you dependable HDD storage in a slim 2.5-inch design. Multiple capacities available up to 2TB — back up photos, videos, music, documents, and game libraries with room to grow. A trusted external storage solution for everyday backup, media archives, and creative work.
- USB-C and USB 3.1 connectivity with included 2-in-1 cable The Facet ships with a USB-C to USB-C cable and tethered USB-A adapter, so this external hard drive connects to modern laptops, USB-C iPhones, tablets, and older USB-A computers without buying an extra cable. USB 3.1 Gen 1 (5Gbps) interface delivers real-world transfer speeds up to 100MB/s — fast enough to back up 50GB of files in about 8 minutes.
- Plug-and-play external hard drive for PC, Mac, and laptops Preformatted in exFAT and ready to use the moment you plug it in. The Facet works out of the box with Windows PCs, macOS Macs, MacBooks, Chromebooks, and laptops — no drivers, no software, no setup required. A true plug-and-play external hard drive built for everyday use across every major operating system.
- External hard drive for PS4, Xbox One, and Smart TV gaming The Facet is compatible with PlayStation 4, Xbox One, and Smart TVs with USB support. PS4 and Xbox One games run directly from the drive — plug it in, format through the console, and add to your storage. Also works with Smart TVs that support USB recording or external media playback.
- Slim, shock-resistant portable external hard drive — 160g At 2.5 inches and just 160g, this portable external hard drive is bus-powered through a single USB-C cable — no separate power adapter, no extra cables. Slim enough for a laptop bag, jacket pocket, or camera bag, with a shockresistant casing and faceted diamond-texture top panel that resists fingerprints and everyday wear. Backed by a 1-year limited warranty from ModusTech, a consumer electronics brand specializing in external storage.
Multisite needs a different plan
Do not apply a single-site checklist blindly to WordPress Multisite. WordPress describes network moves as more complex because references can appear throughout the database, and domain changes may require manual edits to the database, .htaccess, and wp-config.php.
- Map every site in the network and identify its domain or path.
- Back up the complete network database and files before changing anything.
- Review network-specific constants, rewrite rules, and upload paths.
- Test the network dashboard and several subsites through a private destination preview.
- Use an administrator experienced with Multisite for domain or structural changes.
A network migration can also have different write activity and caching behavior per site, so define one authority window for the entire network rather than switching subsites independently without a plan.
Choose a migration method that matches your site
| Approach | Best fit | Control and requirements | Main risks to check |
|---|---|---|---|
| Manual file and database transfer | Administrators with hosting and database access | Highest visibility into files, credentials, imports, and final synchronization | Missed custom configuration, incorrect database credentials, incomplete imports, or permission errors |
| Migration plugin | Single sites where the plugin supports the site size and configuration | Less command-line work; still requires destination testing and DNS control | Large archives, proprietary plugin data, server rules, and serialized URL changes may need separate handling |
| Host-assisted migration | Readers who want the destination host to perform the transfer | Convenience; confirm what access, backup, and rollback the service provides | Unclear scope, incompatible runtime settings, or assumptions that custom services were transferred |
| Platform importer | Moves into a platform with its own documented importer | Follow that platform’s prerequisites and content-replacement rules | Destination content may be replaced; for WordPress.com, the documented process requires a fresh paid-plan destination |
The safest choice is the method that gives you a restorable backup, a private preview, a reliable final synchronization, and control of the DNS switch. Convenience is secondary to those four capabilities.
Recommended Free Tools
Troubleshoot common migration failures
Database connection error
Recheck the destination database name, user, password, host, and table prefix in wp-config.php. Confirm that the database user has permission to access the imported database and that the import completed without truncation.
Home page works but internal pages return 404
Verify the destination document root and rewrite rules. In WordPress, visiting the Permalinks screen and saving once can regenerate rewrite settings, but do this on the destination only and verify that custom rules were preserved.
Images or downloads are missing
Compare the destination uploads directory with the source, including files added after the initial copy. Check permissions, case-sensitive file names, CDN or object-storage credentials, and any URL replacement that changed media paths.
Forms, orders, or comments are absent
Determine which server accepted the submission and whether the final database export included it. Do not merge two independently edited databases casually; identify the authoritative copy and perform a controlled synchronization or re-enter the missing record through the application.
HTTPS loops or mixed-content warnings appear
Confirm the destination certificate covers the apex and required subdomains, verify proxy settings, and inspect redirects for conflicting HTTP-to-HTTPS rules. Test both the bare domain and www hostname if both are advertised.
Users still see the old site
Check the authoritative DNS response and several independent resolvers before assuming failure. Existing resolver caches may still hold the old record. Keep the old host serving during this period and avoid making divergent edits there.
Quick Recap
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.
