Choose a WordPress migration method around site conditions and recovery
Moving hosting while keeping the domain requires different work from changing the domain or URL structure. Update frequency, size, complex features, sensitive data, and destination limits also affect the safe method. First check these four points.
Will URLs change?
If only hosting changes, keep content and URLs and switch the destination. If the domain or directory changes, plan an old-to-new URL mapping, permanent redirects, canonicals, sitemaps, and Search Console.
Does the site fit server limits and available capacity?
Measure WordPress files, uploads, the database, and backups separately. Insufficient PHP upload limits, execution time, disk space, file capacity, or database permissions can interrupt imports.
Can updates be paused?
Orders, registrations, bookings, comments, and form submissions continue to create changes after the first copy. Decide the maintenance window, final synchronization method, user notice, and owners.
Who handles credentials and data?
Check credentials for the server, SFTP, database, DNS, and WordPress administration. When sending data to an external migration service, review internal rules, personal data, contracts, retention, and deletion policies.
Having a backup is not the same as being able to restore it
Do not keep the only backup inside a migration plugin. Save files and the database somewhere separate from the old server. Restore at least once in a test environment and verify important functions including administration, images, forms, login, and orders. Do not begin production cutover with an untested backup alone.
How to choose among five WordPress migration plugins
Choose by method and constraints rather than popularity or overall ranking. Free and paid features, supported capacity, external storage, and destination requirements change; check each official page and your environment before proceeding.
Duplicator
For cloning with an archive and installer
Packages the site for deployment to the destination. It can suit cloning a configuration, including destinations without an existing WordPress installation. Check size, exclusions, and server execution requirements first.
Caution: Large archives consume space and execution time during creation, transfer, and extraction. Test on an empty destination or isolated staging area to avoid leaving partial files after failure.
View the official WordPress.org listingAll-in-One WP Migration
For a mainly dashboard-based export and import
Exports a dedicated file from the source and imports it into WordPress on the destination. The workflow is largely dashboard-based, but WordPress and the plugin must be prepared at the destination.
Caution: Import size depends on PHP, hosting, and extension conditions. Do not stop after export; test the destination import and operation too.
View the official WordPress.org listingUpdraftPlus
For reusing routine backup and restoration procedures during migration
Focuses on file and database backup and restoration. It can suit sites that want to improve routine backups while preparing to migrate.
Caution: Free and paid coverage varies by migration, cloning, and storage destination. Verify the complete backup set, encryption, external storage, and restore procedure against operating requirements.
View the official WordPress.org listingWP Migrate Lite
For administrators who understand database and URL replacement
An administrator-oriented option for database search, replacement, and export. It can suit a domain or path change when you want to review which values are replaced.
Caution: WordPress data includes serialized values. Simple text replacement in SQL can corrupt data; preview, back up, and verify the scope, and do not apply replacements you do not understand to production.
View the official WordPress.org listingMigrate Guru
For supported host-to-host moves through an external service
Performs migration through an external service. It can be considered for large sites or host-to-host moves when reducing load on the server is important. Requirements include preparing WordPress at the destination.
Caution: The official page lists unsupported cases, including local environments and certain multisite conversions. Check whether sending data to the external service complies with your policies and contracts.
View the official WordPress.org listingSix preparations before migration
Researching during production work increases downtime and mistakes. Document the source, destination, and DNS separately so operators and reviewers share the same plan.
Inventory the site and surrounding services
Inventory WordPress core, themes, plugins, uploads, database, PHP and database versions, cron, Basic authentication, CDN, WAF, external storage, outgoing email, analytics, and payment or booking integrations. Check whether the DNS zone and email share a provider.
Check capacity, permissions, and compatibility
Check that destination PHP, database, HTTPS, extensions, write permissions, upload limits, maximum execution time, and free space fit the site. Check WordPress's official recommended environment and the specific requirements of each theme and plugin separately (official recommendations checked November 3, 2026).
Create and restore an independent backup
Capture WordPress files and the database at the same point in time and store them outside the old server. Record date, scope, method, encryption, location, and restoration owner, then restore in a test environment. Mailboxes and DNS may not be included in WordPress backups.
Set the write freeze and communication plan
Decide when to pause orders and posts, who may access administration, user notices, incident contacts, and the final decision-maker. If updates cannot stop, choose a method or specialist that can handle incremental synchronization.
Plan DNS and old-environment retention
Record authoritative DNS, current TTL, A, AAAA, CNAME, MX, and TXT records, and any CDN or proxy. Do not cancel the old contract immediately; allow time for rollback and email checks.
Write success and stop conditions
Define success conditions for important URLs returning 200, administration login, images, form delivery, orders and payments, email, scheduled tasks, SSL, and measurement. Also make stop conditions measurable by counts or actions.

Eight steps for a safe WordPress server migration
Button names differ by plugin and host, but the safe sequence is shared. Keep evidence for each stage and do not advance until checks are complete.
- 1
Share the work plan and write freeze
Share the work schedule, scope, owners, contacts, success and stop conditions, and recovery procedure. Decide when to pause posts, orders, registrations, and other operations that create changes; record the state immediately before starting.
- The freeze start time and affected actions are documented
- Administrative access is restricted to operators
- 2
Capture files and database from the same point in time
Capture WordPress files and the database at the same point in time. Record hashes or file sizes and copy them to separate storage. Prepare an independent recovery path such as host backups or manual extraction in addition to the plugin export.
- wp-content, wp-config.php, and the database were checked
- The backup can be read from storage outside the old server
- 3
Prepare an isolated destination
Configure PHP, the database, SSL, and permissions. Use a test URL, hosts configuration, or staging environment to test without changing public DNS. Do not rely on noindex alone; use authentication or access controls where needed to prevent public exposure.
- It will not accidentally be published at the production URL
- Temporary migration credentials are controlled
- 4
Perform a test migration
Follow the plugin's official instructions for archive creation, export, restoration, or external-service migration. Save logs, warnings, excluded files, and replacement results. Do not ignore errors. For domain changes, use replacement that handles serialized data.
- An owner reviewed errors and warnings
- Excluded data was moved by a separate procedure
- 5
Test URLs and critical functions
Check representative posts, categories, search, 404s, administration, images, forms, login, payments, bookings, email, cron, and APIs, not just the homepage. Test after clearing caches and while logged out.
- Key journeys were checked on desktop and mobile
- Forms and orders were verified through to the receiving side
- 6
Apply final changes before cutover
If the initial copy was made before the write freeze, apply posts, orders, members, comments, and uploads added between that copy and the freeze. Replacing the entire database can lose staging configuration or new production data, so choose an incremental method suited to the site. Stop if you cannot decide safely.
- The beginning and end of the synchronization interval are recorded
- Counts and latest records were compared with the source
- 7
Switch DNS or the destination
Change the actual destination through DNS records, CDN, load balancer, or other planned controls. Keep the old environment running and identify which environment responds using headers, a dedicated verification file, or server logs. DNS propagation differs by user.
- A, AAAA, and CNAME records were updated as intended
- Email records such as MX and TXT were not changed unintentionally
- 8
Verify and monitor after launch
Check from multiple networks and major browsers; monitor 5xx, PHP errors, 404s, certificates, mixed content, forms, email, orders, login, cron, and analytics. If healthy, lift the write freeze and retain the old environment for the planned period.
- Reviewers are assigned immediately after launch, several hours later, and the next day
- The old environment's cancellation date is after validation

Rollback when migration fails
Plan recovery before an incident: stop conditions, the old environment's state, the DNS target, backup location, and recovery owner. You may need to stop user impact before investigating the cause.
Stop cutover under these conditions
- Administration is inaccessible or fatal errors or 5xx responses persist
- Key transactions such as orders, payments, registrations, bookings, or inquiries fail
- Important data such as order counts, member counts, or latest posts differs between source and destination
- SSL, DNS, email, authentication, or external API problems cannot be resolved within the planned window
- Images or files are widely missing, URLs are incorrectly replaced, or permission errors are widespread
- Recovery 01
Stop changes and new submissions
Place the destination in maintenance mode to stop new posts, orders, and registrations. Preserve the incident time, symptoms, prior actions, and logs; do not repeatedly retry without a plan.
- Recovery 02
Return to the old environment or a recent snapshot
If the old environment is healthy, switch traffic back to it. If restoration is needed, pair files and database from the same point in time. Reverting only one can leave inconsistent references.
- Recovery 03
Check the destination and caches
Check DNS, CDN, browser, and server caches, and identify which environment users actually reach. Reverting DNS does not immediately return every user to the old environment.
- Recovery 04
Reconcile transactions and replan
Reconcile orders and inquiries from the incident using logs, payment providers, and received email. Record cause, impact, recovery time, and potentially lost data; schedule another cutover after fixing and retesting.
Rolling back DNS is not instantaneous. Caches and TTLs cause users to reach both environments. Keep writes paused and identify the destination to prevent diverging data.
SEO checks for server migration
A server move alone does not guarantee improved or maintained rankings. Keep content accessible to users and search engines and reduce crawl errors and duplicates.
A move without URL changes
Preserve existing URLs, content, title, canonical, robots, sitemap, structured data, and HTTP statuses as far as possible. Remove staging noindex and access restrictions from production and compare important URLs before and after.
A move with domain or URL changes
Map old URLs to corresponding new URLs and use permanent redirects to relevant destinations. Do not redirect everything to the homepage. Update internal links, canonical, hreflang, and sitemaps to the new URLs; monitor Search Console and logs.
Google recommends avoiding several major changes at once
Google's site-move guidance recommends preparing and thoroughly testing the new site, mapping old to new URLs, using permanent redirects, and monitoring a move with URL changes. It also recommends avoiding simultaneous domain, CMS, and design changes. Rankings can fluctuate temporarily; inspect crawling, indexing, and server logs rather than repeatedly reverting settings based only on short-term changes.
Provider screenshots from the previous article
Five screenshots from the existing article remain as historical references. They show provider announcements and campaigns around August 1, 2025, not migration procedures. They cannot establish current pricing, benefits, migration capabilities, or terms.
Show five historical provider screenshots





Post-migration checklist
A working homepage alone does not mean migration is complete. Verify important user tasks and routine operational processes, and record results and reviewers.
Pages and administration
- The homepage, posts, pages, categories, search, and 404 pages work as expected
- You can log in, publish, upload images, and make updates
- Images, PDFs, CSS, and JavaScript have no 404 or permission errors
- Layouts work on desktop and mobile in major browsers
Transactions and notifications
- Inquiry forms reach the recipient and send automatic replies
- Login, registration, and password reset complete successfully
- Orders, payments, bookings, inventory, and notifications match actual workflows
- cron, queues, webhooks, and external APIs run as planned
SSL, DNS, and email
- The certificate is valid and HTTP redirects to HTTPS as intended
- No mixed content, redirect loops, or www inconsistencies
- A, AAAA, CNAME, MX, and TXT records were compared with the pre-migration record
- Incoming and outgoing email, SPF, DKIM, and DMARC impacts were checked
SEO, monitoring, and recovery
- robots, noindex, canonical URLs, sitemaps, and structured data were checked
- HTTP statuses and redirect destinations for important URLs were reviewed
- 5xx, 404, PHP errors, load, and backups can be monitored
- The old environment, backups, and recovery procedures are retained and cancellation criteria are met
Official sources consulted
The following official pages were checked on July 24, 2026 for WordPress migration, backup, requirements, Google's site-move guidance, and plugin descriptions. Provider claims about performance and size are used to assess compatibility and limitations, not reproduced as guarantees.
- WordPress Developer Resources: Migrating WordPress
- WordPress.org Documentation: WordPress Backups
- WordPress.org: Requirements
- Google Search Central: Site Moves and Migrations
- WordPress.org: Duplicator
- WordPress.org: All-in-One WP Migration
- WordPress.org: UpdraftPlus
- WordPress.org: WP Migrate Lite
- WordPress.org: Migrate Guru
Frequently asked questions about WordPress server migration
Can a WordPress migration plugin guarantee zero downtime?
No. DNS propagation, final changes, caches, and external services can leave both environments in use. Sites with continuing updates need a separate design such as a brief write freeze, incremental synchronization, or load balancing. Decide acceptable downtime before choosing a method.
Can a large site be moved with free plugins alone?
Size alone does not decide. File count, PHP limits, execution time, available space, database, external storage, multisite, and changes during migration all matter. If a complete test restore cannot be finished, consider host migration assistance or a specialist.
Can I cancel the old server immediately after migration?
Do not cancel immediately. Retain it for an agreed period after checking contract dates and costs, to handle mixed DNS, late-discovered failures, email, backups, and rollback. Cancel only after stable operation and separate storage of needed data.
Will changing domains always lower search rankings?
Not necessarily, though Google notes that rankings may fluctuate temporarily during a site move. Prepare URL mapping, permanent redirects, internal links, canonical URLs, sitemaps, Search Console, and log monitoring. Avoid simultaneous major CMS and design changes so causes are easier to isolate.
When should I seek help instead of migrating myself?
Consider a specialist if you cannot complete a restore test, pause order or member updates, identify DNS and email ownership, handle multisite or custom systems, or tolerate a major business impact from failure. Agree on scope, downtime, recovery, fees, and responsibilities in writing before work begins.
Related guides for before and after migration
Choose a migration method you can reliably reverse, not just the fastest one
Before choosing a WordPress migration tool, consider URL changes, size, changes during the move, compatibility, confidentiality, and acceptable downtime. Restore an independent backup, test in isolation, and define success and rollback conditions before cutover. A plugin is a way to execute the plan, not a guarantee of safety.
Editorial and verification approach
Finite Field Editorial Team
We edit our WordPress, server, and website production guides so readers can check their own conditions and stop unsafe work. We prioritize official sources and avoid unverified claims about failure-free migrations, preserved rankings, or limited-time prices.
For migrations you cannot perform yourself or where failure has a high impact
Discuss your WordPress migration and website development
If you cannot restore backups, do not understand DNS or email, cannot pause order or member data, or cannot build the site yourself, tell us your current URL, host, desired timing, and concerns. Finite Field can scope discovery, migration planning, site production, and post-launch checks.
Discuss server migration and website developmentWe will assess the request and explain feasibility, scope, expected downtime, and any fees in advance. We do not guarantee zero downtime or maintained search rankings.