A straightforward WordPress move can take about one to four hours of hands-on work, while a larger or more complicated site may take several hours or a day or two. Changing the domain, rebuilding on another platform, auditing content, recreating forms, and mapping redirects can extend the project to one to 16 weeks or more. DNS changes can require up to 72 hours to reach users worldwide. WordPress itself publishes procedures, not an official duration, so your site’s content, database, integrations, and redirect requirements determine the real schedule.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
What WordPress officially says about migration time
The official WordPress documentation does not promise a number of hours or days. It explains how to move files, databases, URLs, and rewrite rules, but leaves scheduling to the site owner. That is important: any exact duration should be treated as a planning estimate rather than a WordPress service-level guarantee.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →For the technical sequence, use WordPress.org’s Migrating WordPress guide and the WordPress Developer Documentation migration guide. The steps differ substantially depending on whether the address stays the same, the domain changes, or WordPress is replaced by another content-management system.
Typical timelines by migration type
The ranges below combine the official procedure with rough figures reported by vendor blogs and agencies whose names and publication dates were not identified. They are useful for setting expectations, not verified benchmarks.
| Migration scenario | Rough planning range | What usually consumes the time |
|---|---|---|
| Same host, same URL | About 1–4 hours for a straightforward site; several hours to a day or two for a larger or complex site | Copying files and the database, checking configuration, testing, and restoring permalinks |
| New host, same URL | Often the same hands-on range as a basic move, plus DNS waiting time of up to 72 hours | Database import, server configuration, DNS changes, and verification on the new host |
| New host and new domain or URL | No fixed official estimate; commonly longer than a host-only move because every stored URL must be reviewed | URL replacement, redirect mapping, media and internal-link checks, and SEO validation |
| WordPress to another platform | About 1–2 weeks for a simple site, 2–4 weeks for a mid-size business site with a blog, and 4–8 weeks for a large site or store | Template rebuilding, content transformation, integrations, forms, redirects, and acceptance testing |
| WordPress to Webflow, by page count | 3–4 weeks for 20–50 pages; 4–8 weeks for 50–200 pages; 8–16 weeks or more for 200+ pages with integrations | Page-by-page recreation, CMS collections, responsive layouts, redirects, and connected services |
The 1–4-hour, 72-hour, and multi-week figures are reported ranges from unidentified publishers, with no visible dates. They should not be presented as official WordPress statistics.
Why two sites with the same page count take different times
Content quality matters more than raw page count
Page count is an imperfect predictor. One agency example says 300 pages of inconsistent, poorly structured content can take longer to migrate than 3,000 clean pages. During a migration, someone may need to normalize headings, remove obsolete entries, repair media references, and decide which URLs remain public. A smaller but messy site therefore needs a larger review window.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Database and media size affect transfer and checking
Copying files and exporting a database is only one part of the job. Large uploads directories, substantial databases, and serialized settings increase transfer, import, and verification time. A successful import still requires checking that images load, menus point to the intended destinations, and dynamic content has not been truncated.
Plugins, forms, and integrations add discovery work
Every plugin that stores settings, custom post types, user data, or external connections can introduce a migration task. Reported anecdotes include a redirect list growing from 200 to 1,800 rows and a site containing 47 undocumented forms with conditional logic. Those examples are not universal measurements, but they show why an apparently small site can require a long audit.
Redirects protect search visibility
When URLs change, the old addresses need deliberate destinations. One source describes skipped redirects as a common cause of permanent ranking loss. Building, reviewing, and testing a redirect map can take longer than copying the WordPress files themselves, particularly when the old and new information architectures differ.
DNS is elapsed time, not hands-on labor
After nameservers or DNS records are changed, different networks can continue using cached answers. An unnamed guide gives up to 72 hours as an upper bound for worldwide propagation. Your team may finish the server work in an afternoon while some visitors still reach the old host during that window.
Same host and same URL: the shortest path
If the hosting account and public URL remain unchanged, the official guidance says you can often copy the WordPress files and database. You only need to edit wp-config.php if the database name or database user changes.
- Make complete backups. Keep a copy of the files and a database export before replacing anything.
- Copy the files and database. Preserve the WordPress directory structure and import the database into the intended database.
- Check configuration. Update the database name or user in
wp-config.phponly when those credentials differ. - Test before the final switch. WordPress allows a temporary test by changing the
siteurlandhomevalues in thewp_optionstable. Record the original values so they can be restored. - Handle rewrites carefully. If the site uses custom permalinks or rewrite rules, disable
.htaccesstemporarily and reconfigure permalinks after the site is live. - Verify the live site. Test the homepage, representative posts, login, media, forms, menus, and any ecommerce or membership functions before declaring the move complete.
For a simple installation, these actions explain why hands-on work is often measured in hours. A heavily customized site can still take a day or two because testing and troubleshooting, rather than file copying, become the limiting steps.
New host with the same domain
Moving hosts while keeping the exact domain usually follows the same file-and-database process, but DNS introduces an additional elapsed-time phase. Plan for a period in which some visitors may reach the old server and others the new one.
Practical sequence
- Back up the old site and confirm that the backup can be opened or restored.
- Prepare the new hosting account, database, PHP environment, and file location.
- Upload the files and import the database on the new server.
- Point the new server’s configuration at the imported database and check that the domain resolves correctly there.
- Change the DNS records or nameservers when the new copy has passed testing.
- Monitor both servers during propagation, then recheck forms, logins, media, and scheduled functions after the new host receives traffic.
The DNS upper bound of 72 hours comes from an undated, unidentified guide, not from WordPress.org. Actual propagation varies by resolver and cache, so treat it as contingency time rather than a promise that every user will wait exactly three days.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesNew host and new domain or URL: the URL work is the project
A domain change is more than a server transfer because the old address is embedded in content, settings, media references, and links. WordPress’s documented workflow is deliberate:
- Back up and export. Back up the files and export the database from the old site.
- Change the site address. In Settings > General, change the WordPress Address and Site Address to the new URL. The guide warns that a 404 afterward is expected at this stage.
- Download and export again. Download the files and export the database after the address change so the new values are captured.
- Configure the destination. Point
wp-config.phpat the new server’s database, upload the files, and import the database. - Replace remaining URLs. Use Better Search Replace in the dashboard or WP-CLI’s
search-replacecommand to find old URLs and write the new ones. Skip theguidcolumn; the official guidance says never to change GUID values. - Preserve redirects and rewrites. Save custom
.htaccessrules or redirects before replacing the file, then restore the required rules on the new server. - Refresh permalinks. Re-save the permalink settings and confirm that both address fields under Settings > General show the new URL.
Build a redirect for every changed public URL, not just the homepage. Test old links, internal links, canonical tags, XML sitemaps, images, feeds, and campaign URLs. Redirect work is the main reason a domain change can take days even when the database import takes minutes.
Using a migration plugin
A migration plugin can replace several manual export and import steps with an export-and-import workflow. The All-in-One WP Migration listing claims that its process updates URLs and handles serialized data, and it recommends 301 redirects for every changed URL. Those are the vendor’s claims, so validate the result on your own installation rather than assuming a plugin removes the need for testing.
Plugin-based transfers still require backups, destination-server preparation, URL checks, permalink verification, and functional testing. A plugin can shorten repetitive work, but it cannot decide whether an old page should redirect to a specific new page, whether a form integration still authenticates, or whether obsolete content should be removed.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #3
Platform changes and redesigns: plan in phases
Moving from WordPress to another CMS is a rebuild as well as a migration. The reported ranges are 1–2 weeks for a simple site, 2–4 weeks for a mid-size business site with a blog, and 4–8 weeks for a large site or store. A separate agency estimate for WordPress-to-Webflow projects gives 3–4 weeks for 20–50 pages, 4–8 weeks for 50–200 pages, and 8–16 weeks or more for 200+ pages with integrations. Because the publishers and dates were not identified, use these only as broad scheduling bands.
Discovery and inventory
List URLs, templates, taxonomies, media, forms, memberships, ecommerce functions, analytics, search features, and external integrations. Mark each item as migrate, rebuild, redirect, or retire.
Content and design rebuild
Recreate templates and responsive layouts, convert content into the destination platform’s fields, and check images, embeds, metadata, and navigation. This is where inconsistent source content creates extra editorial work.
Recommended Free Tools
Integration and form testing
Recreate conditional logic, email delivery, payment or CRM connections, and authentication. Undocumented forms are a frequent source of late discoveries; inventory them before promising a launch date.
Redirect and launch testing
Map every retained URL, install 301 redirects, test representative old links, and run a pre-launch crawl. Keep the old site available long enough to diagnose missed redirects and integration failures.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to create a defensible estimate for your site
Start with the smallest plausible case, then add explicit risk allowances instead of multiplying a generic “hours per page” number.
- Choose the scenario: same host and URL, new host, new domain, or a platform rebuild.
- Count assets: pages, posts, media, custom post types, database size, forms, and integrations.
- Grade content quality: clean and consistent, or inconsistent and requiring editorial decisions.
- Estimate URL work: count changed paths and identify pages without an obvious one-to-one destination.
- Reserve testing time: include desktop and mobile checks, logins, forms, search, media, redirects, and analytics.
- Add elapsed-time contingency: include DNS propagation of up to 72 hours when the domain’s DNS changes.
- Define acceptance criteria: specify which URLs, functions, and integrations must pass before the old site can be retired.
A useful schedule separates hands-on work from elapsed waiting time. For example, a four-hour file transfer does not mean the migration is finished if DNS is still propagating or redirect testing has not been completed.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, 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 minuteCommon causes of overruns and how to avoid them
Replacing .htaccess without saving custom rules
Custom rewrites and redirects can disappear when the file is replaced. Save the existing rules first, then restore and test them after the new site is live.
Changing GUIDs during a URL replacement
Do not include the guid column in a search-and-replace operation. The official WordPress guidance specifically says never to change GUID values.
Assuming a 404 during testing means the move failed
The documented new-domain workflow expects a 404 after changing the address in Settings > General. Continue with the file upload, database import, and remaining URL replacement steps before judging the result.
Leaving redirects until launch day
Redirect mapping can grow dramatically when old content has inconsistent paths. Start the map during discovery, review each destination, and test it before the DNS change.
Treating MultiSite as a single-site copy
The single-install instructions do not apply to WordPress MultiSite. MultiSite requires manual database editing, so obtain a network-specific plan and allow additional testing rather than applying the ordinary single-site sequence.
Bottom line
Budget hours for a clean host move, up to a couple of days for a complex installation, and weeks for a domain-changing rebuild or a move to another platform. Add up to 72 hours of DNS propagation when relevant. The most reliable estimate comes from your own inventory of URLs, content quality, plugins, forms, integrations, and redirect requirements—not from page count alone.
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.
