What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A straightforward WordPress move that keeps the same domain can often be completed in a few hours. A host change may require additional verification and DNS propagation, while a domain change, redesign or move to another content-management system is normally planned in weeks. The exact duration depends less on the raw number of pages than on database complexity, media, plugins, integrations, redirect work and how cleanly the existing content is organized.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
There is no official WordPress time estimate. WordPress.org documents the technical sequence, but the hour and week ranges below come from undated, unnamed vendor and agency articles and should be treated as planning ranges rather than guaranteed benchmarks.
As an Amazon Associate I earn from qualifying purchases.
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 matchTypical WordPress migration timelines
| Move type | Planning range | What the range includes | Evidence and caveat |
|---|---|---|---|
| Same host, same URL | About 1–4 hours for a straightforward site | Copying files and the database, checking configuration, testing and restoring rewrites | Figure reported by an unnamed WordPress blog; publication year and publisher were not identified |
| Same platform, larger or more complex site | Several hours to a day or two | More media, larger databases, complicated plugins, forms, integrations and a longer validation cycle | Undated, unidentified vendor-blog estimate; not a measured standard |
| DNS change after a host move | Propagation can take up to 72 hours worldwide | Resolvers and visitors gradually learning the new DNS records | Undated, unidentified guide; the upper bound is not a promise that every domain will take this long |
| WordPress to another platform, simple site | 1–2 weeks | Content mapping, template work, imports, redirects, testing and launch | Undated estimate from an agency whose name and publication date were not visible |
| WordPress to another platform, mid-size business site with a blog | 2–4 weeks | More templates, editorial content, integrations and redirect rules | Same unidentified agency estimate; use only as a rough planning bracket |
| Large site or store moving platforms | 4–8 weeks | High content volume, commerce or account flows, integrations, migration scripts and extended QA | Same unidentified agency estimate; actual schedules vary substantially |
| 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 | Rebuilding layouts, importing or recreating content, mapping URLs and testing integrations | Undated agency figures specifically for WordPress-to-Webflow projects, not an official WordPress benchmark |
The official WordPress.org moving guide and WordPress Developer Documentation describe what to do, but neither publishes a duration. Treat the table as a scheduling aid, then measure your own site before committing to a launch date.
What kind of migration are you planning?
Same host and same URL
This is usually a file-and-database copy. Because the domain and hosting environment remain unchanged, there is no public URL replacement and often no DNS work. The main risks are an incomplete upload, incorrect database credentials, missing uploads or a plugin that behaves differently after the copy.
#1 Best Overall
New host, same URL
The WordPress installation moves to another server while visitors continue using the same domain. You still need to point the domain’s DNS to the new host and verify certificates, email records, cron jobs, caching and server-level rewrites. Visitors may reach old and new servers during propagation, so keep the old site available until validation is complete.
New domain or changed URL
This adds a URL-replacement project. Internal links, image paths, canonical references, feeds, XML sitemaps and hard-coded settings can contain the old address. Every public URL that changes needs an intentional destination and, where appropriate, a permanent redirect.
Platform change or redesign
Moving from WordPress to another CMS, or rebuilding templates while changing information architecture, is not just a hosting transfer. Content must be transformed, layouts recreated, forms and integrations reconnected, and every important URL tested. That is why platform moves are measured in weeks rather than a single maintenance window.
The official manual procedure
Same host and same URL
- Make a complete backup of the WordPress files and database before touching the live installation.
- Copy the files and database to the target location. If the database name, user or password changes, edit
wp-config.phpso WordPress can connect to the new database. - For a pre-launch test, temporarily change the
siteurlandhomevalues in thewp_optionstable as described by WordPress.org. Use a controlled test hostname or other isolated method so search engines and visitors do not index the test address. - If the site uses custom permalinks or rewrite rules, disable the existing
.htaccessrules during the move and plan to recreate them after the new copy is live. - Log in, check representative posts and pages, test media and forms, then reconfigure permalinks when the site is ready.
New host and new domain or URL
- Back up the old files and export the old database.
- In the old WordPress dashboard, open Settings > General and change the WordPress Address and Site Address to the new URL. WordPress.org notes that a 404 after this change is expected during the process.
- Download the files and export the database again after the URL change, following the sequence in the official guide.
- On the new server, point
wp-config.phpto the new database name, user, password and host, then upload the files and import the database. - Replace remaining old URLs in the database. The official guide suggests Better Search Replace in the dashboard or the WP-CLI
search-replacecommand. Exclude theguidcolumn: WordPress.org explicitly says never to change GUID values. - Restore any custom rewrite or redirect rules that you saved before replacing
.htaccess. - Visit Settings > Permalinks and save the existing structure once, which regenerates rewrite rules. Confirm under Settings > General that both address fields show the intended URL.
These steps describe a single-site installation. WordPress Multisite does not use the same simple procedure; its network tables and domain mappings require manual database edits, so schedule specialist review rather than applying a single-site checklist unchanged.
Manual copy or migration plugin?
| Approach | Strengths | Risks and checks | Best fit |
|---|---|---|---|
| Manual files and database | Direct control over backups, SQL, configuration and server settings; works when you need to inspect or transform data | Easy to omit uploads, serialized data, rewrite rules or environment-specific settings; requires a tested rollback | Developers, unusual hosting environments, Multisite work and migrations requiring custom scripts |
| Export/import plugin | Packages an export and import workflow and can automate URL updates and serialized-data handling | Available storage, execution time, PHP limits, extension compatibility and the plugin’s own restore process must be tested | Common single-site moves where the source and destination can run the same WordPress version and plugin |
The All-in-One WP Migration listing describes an export-and-import workflow that updates URLs and handles serialized data, and it recommends a 301 redirect for every changed URL. Those are the vendor’s claims; verify the result on a staging copy and keep an independent file and database backup.
What determines the schedule
Content quality beats page count
A large number of clean, consistently structured pages can be easier to move than a smaller archive full of exceptions. One agency example says 300 messy pages took longer than 3,000 clean pages. The practical audit is to identify custom post types, inconsistent shortcodes, missing featured images, obsolete attachments and pages that should be merged or retired before migration.
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 →Database and media volume
Database export and import time grows with tables, revisions, transients and plugin data. The wp-content/uploads directory can be much larger than the database, especially on a media-heavy site. Count both, check the destination’s disk quota and test transfer and restore speeds rather than estimating from page count alone.
Plugins, forms and integrations
Every plugin that stores settings, custom tables, scheduled tasks or serialized options adds a test case. Forms, analytics, advertising tags, search, memberships, payment services, email delivery and external APIs may need new credentials or webhook URLs. An agency-reported example involved 47 undocumented Gravity Forms with conditional logic; it is an anecdote, but it illustrates why an inventory can change the schedule.
Redirect-map size
Changing slugs or information architecture creates mapping work. One reported project grew from 200 to 1,800 redirect rows. Build the map from the old URL list, not memory, and mark each destination as tested, redirected or intentionally retired.
Access and environment constraints
Waiting for hosting access, DNS control, database credentials, SSL issuance, staging approval or a content freeze can take longer than copying files. Confirm who can change DNS, who can approve downtime and how a rollback will be performed before selecting a launch date.
SEO, redirects and URL integrity
A host-only move that keeps every URL normally needs no URL migration, but it still needs crawl testing. A domain or permalink change requires a one-to-one redirect plan. Skipped redirects are cited as a common cause of permanent ranking loss, so do not treat them as an optional cleanup task.
- Export the old site’s indexable URLs, including posts, pages, categories, media that receives search traffic and important feeds.
- Assign a final destination for every changed URL. Redirect equivalent content with a permanent 301; send removed content to the closest useful replacement rather than a generic homepage.
- Update internal links, canonical tags, XML sitemaps, structured-data URLs, Open Graph metadata and hard-coded references.
- After launch, test samples from each template and every high-value redirect, then watch server logs and crawl reports for 404s and redirect chains.
DNS and cutover planning
DNS propagation is separate from the file transfer. Once the authoritative record changes, different networks can continue using cached answers for different periods. An undated guide gives up to 72 hours as an upper planning bound. Keep the old host online, synchronized and capable of serving the site during that window; do not cancel it immediately after changing the record.
Rank #4
Lowering a record’s TTL shortly before a move may reduce cache duration for resolvers that honor the new value, but it cannot force every resolver to refresh instantly. Confirm the new host serves the correct certificate, redirects, robots rules and application before changing DNS, and test from more than one network after the change.
A practical migration runbook
- Inventory: record domains, subdomains, databases, uploads, plugins, themes, forms, cron jobs, integrations, email services and custom rewrite rules.
- Measure: record database size, uploads size, URL count, redirect count and the largest or most fragile integrations. This produces a site-specific estimate instead of relying on page count.
- Back up and rehearse: create independent file and database backups, restore them on staging and document rollback steps.
- Prepare the destination: match the required PHP, database, web-server, SSL and scheduled-task settings; install the intended WordPress version and extensions.
- Freeze or synchronize content: choose a final content cutoff, or plan a last database and uploads sync immediately before launch so new posts, comments and form entries are not lost.
- Validate staging: check login, publishing, media, search, forms, email, analytics, payment or membership flows, responsive templates, redirects and error logs.
- Cut over: perform the final copy, apply URL replacements if needed, restore rewrites, save permalinks and switch DNS or the reverse proxy.
- Monitor: keep the old environment available, test critical URLs from external networks and review 404s, logs, uptime, forms and search-console crawl errors before declaring the migration complete.
Common delays and recovery steps
The imported site shows database errors
Recheck the database name, user, password and host in wp-config.php. Confirm that the user has privileges on the imported database and that the destination server supports the database version and required PHP extensions.
Images or downloads return 404
Compare the uploaded wp-content/uploads tree with the source backup, verify file ownership and permissions, and check whether old absolute URLs remain in attachment metadata or post content. Re-run a careful search-and-replace while excluding the guid column.
Permalinks produce 404 pages
Restore the intended .htaccess or server rewrite configuration, then save the permalink settings once. If the host uses a different web server, translate Apache rules to that server’s format instead of copying them unchanged.
Best Value
Forms, cron jobs or external services stop working
Test each integration with production-like credentials, regenerate webhook or API endpoints when the domain changed, and confirm scheduled tasks are running on the new server. Keep a written list of every integration so an undocumented dependency does not surface after the old host is closed.
Visitors still see the old site
Check authoritative DNS, resolver caches and the old host’s access logs. During propagation, this can be normal. Keep both environments consistent and avoid making one-sided content edits until traffic has converged on the destination.
How to estimate your own migration
Start with the scenario table, then add work for each complication you can verify. A realistic estimate should answer these questions:
- Is the domain staying exactly the same, or will any URL, slug or protocol change?
- How large are the database and uploads, and has a full restore been timed?
- How many plugins, custom post types, forms, scheduled jobs and third-party integrations need testing?
- Do you have a complete old-URL export and a reviewed redirect map?
- Is the site Multisite, multilingual, membership-based, transactional or otherwise dependent on custom database tables?
- Who controls DNS, SSL, hosting access and final launch approval?
- How long must the old environment remain available for rollback and DNS convergence?
If the answers are mostly simple, reserve a maintenance window measured in hours and allow extra time for DNS and verification. If the move changes platform, templates or information architecture, plan in weekly phases for discovery, build, import, redirects, testing and launch rather than promising a single-day cutover.
Bottom line
WordPress itself does not publish a standard migration duration. A same-URL copy is commonly planned as a few-hour operation, with complex sites extending into a day or two; a DNS change can remain visible on different networks for up to 72 hours. Domain changes and platform rebuilds take weeks because URL mapping, integrations, content quality and testing—not the act of copying files—determine the real workload.
Free tools Windows power users keep installed
One-click scans. No signup required.
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.
