WordPress Migration Guide: How to Migrate Your Site in 2026

You know your WordPress site well enough to know a migration can go wrong in dozens of small ways. A missed database URL breaks images, one tracking script fails to transfer, and your reporting develops a hole you do not notice until the next campaign review.

So the goal is not simply to get WordPress onto another server. You need to move the site while preserving its content, functionality, SEO signals, integrations, and data.

This guide gives you the full WordPress migration process for 2026, including backups, plugin and manual migration methods, DNS cutover, common errors, SEO preservation, and post-migration checks.

Key takeaways

• You can migrate a WordPress site with a migration plugin, manually through FTP and database transfer, or through a managed hosting service. Plugin-based migration is the simplest route for most sites, while manual migration gives you more control over large or complex setups.
• A successful migration starts before you move anything. Back up your database and files, document plugins and integrations, prepare the destination server, configure SSL, and lower your DNS TTL before the cutover.
• Preserving URLs, redirects, metadata, schema, internal links, and tracking is critical to protecting SEO. After the move, verify these elements in Google Search Console and your analytics setup rather than assuming everything transferred correctly.
• Keep your old server live while DNS propagates and you test the new site. Check forms, navigation, media, redirects, analytics, SSL, and key landing pages before shutting down the original environment.
• Migration does not end at DNS cutover. Your site still needs ongoing technical SEO checks, performance monitoring, content updates, and optimization after it goes live.
• Ploy offers a different route from a traditional WordPress migration. Ploy Web can slurp the rendered site into an editable first pass, preserve its visible structure and brand foundation for review, then support technical SEO, Core Web Vitals, and Answer Engine Optimization work after launch. WordPress databases, plugins, accounts, and app data require separate migration planning.

Why your WordPress migration strategy needs an upgrade in 2026

The problem with one-time migrations

WordPress migration guides focus on the transfer: exporting the database, downloading the files, uploading to the new server, and updating DNS. But your site’s real work is just starting.

Search engines need time to re-crawl and re-index your content. AI answer engines like ChatGPT, Perplexity, and Google’s AI Overviews pull information from structured data and schema markup that often breaks during migration. Buying intent shifts while your team spends weeks fixing post-migration issues instead of shipping campaigns.

The ongoing work compounds quickly:

• Broken internal links from serialized data issues
• Missing images because URL replacement missed edge cases
• Analytics gaps from incorrectly configured tracking codes
• SEO drops from changed permalink structures without redirects
• Forms that stopped working because plugin settings did not transfer

Each issue requires a separate fix. Each fix requires a different tool. The migration that was supposed to take a weekend stretches into weeks of cleanup.

What changes in 2026

AI answer engines now influence how potential customers find your business. A site that ranks well in traditional search may not appear in AI-generated answers if the content lacks proper schema markup, direct-answer formatting, and citation-ready structure.

Answer Engine Optimization requires ongoing work: structuring pages for AI citation, monitoring how your brand appears across ChatGPT, Perplexity, Gemini, Claude, and Google AI Overviews, and updating content as AI models evolve. Traditional migrations do not account for this work because they treat the site as a static asset.

Ploy treats the site as a growth engine. After migration, Ploy Web continuously monitors AEO performance, drafts improvements, and recommends updates based on how AI answer engines interact with your content.

Planning your WordPress migration: Essential steps for a smooth transition

Pre-migration checklist

Successful migrations depend on preparation. Before touching any files:

Audit your current site

• Document all plugins, themes, and custom code
• Export Google Search Console data for ranking baseline
• Screenshot current analytics setup and goals
• List all forms, integrations, and third-party connections
• Identify pages with highest organic traffic

Create redundant backups

• Full database export via phpMyAdmin
• Complete file system backup including wp-content
• Store backups in at least two locations (local and cloud)
• Test backup restoration on a staging environment

Prepare the destination

• Verify PHP version matches between servers (same major version)
• Confirm adequate disk space for files and database
• Set up SSL certificate before migration
• Create database and user credentials

Reduce DNS propagation time

• Lower TTL to 300 seconds at least 48 hours before migration
• Document current DNS records for rollback
• Plan migration during low-traffic window

Understanding migration methods

Three primary approaches exist, each with different tradeoffs:

Plugin-based migration works for many sites. Install a migration plugin, create a package, upload to the new server, and run the installer. Plugins can handle URL replacement and serialized data, but upload limits vary by plugin version, license, server configuration, and hosting plan. Check the current limits before choosing a method.

Manual migration gives you full control. Export the database via phpMyAdmin, download files via FTP, upload to the new server, import the database, and manually run search-replace commands. This approach requires more technical skill but handles edge cases that plugins miss.

Managed migration offloads the work to hosting providers. Many hosts offer free migration services when you sign up, but you depend on their timeline and process.

Mastering WordPress migration: Tools and techniques for 2026

Plugin-based migration step by step

This process applies to most plugin-based migrations and generally saves significant time compared to manual methods:

Step 1: Prepare the source site (30 minutes)

• Update WordPress core, plugins, and themes
• Disable caching plugins (WP Super Cache, W3 Total Cache)
• Disable security plugins (Wordfence, Sucuri)
• Delete spam comments and post revisions to reduce database size

Step 2: Export from source (15-45 minutes)

• Install migration plugin
• Create export package (generates .wpress or .zip file)
• Download package to local machine or note cloud storage location

Step 3: Prepare destination (15 minutes)

• Install fresh WordPress on new server
• Install same migration plugin
• Verify PHP memory limit and upload size (increase if needed)

Step 4: Import to destination (20-60 minutes)

• Upload package via plugin interface or FTP
• Run import wizard
• Wait for completion (larger sites take longer)

Step 5: Post-import configuration (15 minutes)

• Re-save permalinks (Settings > Permalinks > Save Changes twice)
• Reactivate caching and security plugins
• Test homepage, key landing pages, and forms
• Verify SSL certificate shows correctly

Step 6: DNS cutover (0-48 hours propagation)

• Update A record or nameservers at domain registrar
• Monitor propagation via DNS checker tools
• Keep old server active for 7-14 days as safety net

Manual migration for advanced users

Manual migration provides more control when plugins fail or for complex server configurations:

Export database via phpMyAdmin (10 minutes)

• Access phpMyAdmin on source server
• Select your WordPress database
• Export using Quick method, SQL format
• Download the .sql file

Download files via FTP (30-120 minutes)

• Connect to source server using FileZilla or similar
• Download entire /wp-content/ folder (themes, plugins, uploads)
• Download wp-config.php for reference
• Time depends on file size and connection speed

Create database on destination (5 minutes)

• Access hosting control panel
• Create new MySQL database
• Create database user with full privileges
• Note database name, username, password, and host

Import database (10-30 minutes)

• Access phpMyAdmin on destination server
• Select new database
• Import the .sql file
• Wait for completion

Upload files via FTP (30-120 minutes)

• Connect to destination server
• Upload /wp-content/ folder to WordPress directory
• Overwrite existing folders

Update wp-config.php (5 minutes)

• Edit wp-config.php on destination
• Update DB_NAME, DB_USER, DB_PASSWORD, DB_HOST
• Save and upload

Run URL replacement (10 minutes)

• Install Better Search Replace plugin, or
• Use WP-CLI: wp search-replace 'oldsite.com' 'newsite.com' --skip-columns=guid
• This handles serialized data correctly

Common migration errors and fixes

Most migration issues fall into predictable categories with known solutions:

Most 404 errors after migration resolve by re-saving permalinks twice. This step regenerates the .htaccess file with correct rewrite rules. Most guides mention it once in passing. It should be the first thing you try when pages return 404.

Moving your WordPress site: Domain, hosting, and infrastructure considerations

Domain transfer vs. DNS update

Two scenarios require different approaches:

• Same domain, new host: Update DNS records to point to the new server’s IP address. The domain stays at your current registrar. Only the A record (or nameservers) changes.
• New domain: Requires URL replacement throughout the database plus 301 redirects from every old URL to its new equivalent. This is significantly more complex and carries higher SEO risk.

DNS propagation best practices

DNS changes do not take effect instantly. Propagation takes 2-48 hours depending on TTL settings and geographic location. During this window, some visitors see the old site while others see the new one.

Minimize propagation impact:

• Lower TTL to 300 seconds at least 48 hours before migration
• Make DNS change during lowest traffic period
• Keep old server running until propagation completes
• Use DNS propagation checker to monitor global status

SSL certificate configuration

SSL must be configured before DNS cutover to avoid security warnings:

• Install SSL certificate on new server before migration
• Update WordPress settings to use https:// URLs
• Run search-replace to update any hardcoded http:// URLs in database
• Verify SSL shows correctly via browser padlock icon

Infrastructure requirements for post-migration performance

Your hosting environment affects site speed, which affects both user experience and search rankings. Key factors:

• PHP version: Match or upgrade PHP version (7.4 to 8.x improves performance)
• Memory limits: Ensure adequate PHP memory_limit (256MB minimum for most sites)
• Server location: Choose server location closest to primary audience
• CDN integration: Configure CDN before DNS cutover for immediate performance benefits

Ploy’s hosting includes managed SSL, edge delivery, and custom-domain support. Teams still verify DNS, redirects, certificates, analytics, and production routes during cutover, while Ploy handles the underlying hosting layer.

Post-migration checklist: Ensuring your WordPress site works harder for you

Immediate verification (first 24 hours)

Complete these checks before declaring migration successful:

Functionality testing

• Homepage loads correctly with proper styling
• Navigation menus link to correct pages
• Contact forms submit and send notifications
• E-commerce checkout processes (if applicable)
• Search function returns results
• User login and registration works

Content verification

• Sample blog posts display with images
• Media files load (check Network tab in browser dev tools)
• Custom post types appear correctly
• Widgets and sidebars display as expected

Technical checks

• SSL certificate shows valid in browser
• Redirects work (www to non-www or vice versa)
• robots.txt accessible and contains correct directives
• XML sitemap generates and is accessible

SEO preservation (first week)

SEO preservation requires active monitoring, not passive hope. Incorrect migration can significantly impact rankings if technical elements break:

Verify SEO plugin data

• Yoast, RankMath, or All in One SEO settings transferred
• Meta titles and descriptions appear correctly
• Schema markup generates properly
• Canonical URLs point to correct domain

Search Console actions

• Add and verify new property (if domain changed)
• Submit updated XML sitemap
• Monitor crawl errors daily for first two weeks
• Check Index Coverage report for excluded pages

Redirect verification

• 301 redirects active for any URL structure changes
• No redirect chains (redirect A > B > C should be A > C)
• Check for soft 404s (pages returning 200 but showing error content)

Analytics and tracking recovery

Tracking gaps during migration create blind spots in your data. Verify these connections:

• Google Analytics 4 tracking code firing on all pages
• Google Search Console verification tag present
• Lead capture tracking for forms, purchases, sign-ups
• Third-party pixels (Facebook, LinkedIn, etc.) loading correctly
• Heat mapping tools reconnected

Ploy’s built-in analytics combine server-side and client-side tracking. This captures visitors that browser-based analytics miss, including those with ad blockers or JavaScript disabled. You do not need to verify multiple tracking codes because analytics are native to the platform.

Answer Engine Optimization after migration

Traditional SEO checks do not cover how AI answer engines interact with your content. Post-migration AEO verification includes:

• Schema markup validates without errors
• FAQ content structures display correctly
• Direct-answer formatting preserved in key pages
• Brand mentions appearing in AI-generated responses

Ploy’s AEO monitoring tracks how your brand appears across ChatGPT, Perplexity, Gemini, Claude, and Google AI Overviews. The platform automatically structures pages for AI citation and monitors changes over time.

Streamlining WordPress migration with automated workflows

The ongoing work of manual migration

Every WordPress migration creates ongoing work:

• Database backups need scheduling
• Plugin updates require testing
• Security patches need monitoring
• Performance optimization needs regular audits
• SEO improvements require manual implementation

This ongoing burden compounds across every site you manage. Agencies handling 20 client sites spend more time on maintenance than strategy.

How Ploybooks automate post-migration work

Ploybooks are pre-built growth strategies executed by specialized AI employees. Each Ploybook runs an entire workflow, not just an individual task. For post-migration scenarios:

• SEO and AEO Audits: Automatically audit technical SEO, Core Web Vitals, and Answer Engine Optimization. Receive recommendations with one-click implementation.
• GSC Keyword Optimization: Connect to Google Search Console and automatically identify optimization opportunities based on actual search data.
• Content Page Building: Generate new pages that stay on brand without rebuilding design systems from scratch.
• Comparison and Alternatives Pages: Create comparison pages designed for AI citation, structured for how modern search works.

The difference from traditional automation: Ploybooks run continuously. They respond to triggers, act on opportunities Ploy identifies, and draft improvements automatically. You review and approve. Ploy handles execution.

From one-time migration to continuous optimization

Traditional migration treats your website as a static asset. Migrate it, maintain it, redesign it in three years.

Ploy treats your website as a growth engine that keeps working after launch. Instead of periodic maintenance projects, Ploy Web continuously:

• Monitors technical SEO and Core Web Vitals
• Tracks Answer Engine Optimization performance
• Identifies internal linking opportunities
• Drafts content improvements based on search demand
• Recommends new pages based on competitor activity

Migration becomes the starting point, not the finish line.

Ensuring data integrity: Backup strategies before and after migration

Pre-migration backup requirements

Backup failures cause more migration disasters than any other single factor. Complete backup strategy includes:

Database backup

• Export via phpMyAdmin or WP-CLI
• Verify export completed without truncation
• Store in multiple locations

File system backup

• Complete /wp-content/ folder
• Include wp-config.php
• Capture .htaccess file

Off-site storage

• Cloud storage (Google Drive, Dropbox, S3)
• Local machine copy
• Never rely solely on server-based backups

Validation

• Test restore on staging environment
• Verify database import completes
• Confirm media files accessible

Choosing backup solutions

Post-migration backup schedule

After migration, establish ongoing backup routines:

• Daily database backups (automated)
• Weekly full-site backups
• Before any major changes (plugin updates, theme changes)
• Retain at least 30 days of backup history
• Test restoration quarterly

Why Ploy is the ultimate post-migration growth platform for WordPress sites

The limitation of traditional migration

Traditional WordPress migration solves the transfer problem. Files move. Database imports. DNS updates. But the underlying workflow does not change:

• You still need separate tools for SEO, analytics, and optimization
• You still wait on engineering tickets for landing page changes
• You still manage disconnected dashboards across multiple vendors
• You still run periodic audits instead of continuous improvement

The migration succeeds, but the ongoing work remains.

How Ploy eliminates the migration workflow

Ploy Web can slurp the rendered marketing site into an editable first pass that preserves its visible structure, components, design patterns, and brand voice for review. WordPress databases, plugins, accounts, ecommerce records, and other dynamic systems still need explicit migration or replacement plans.

But the real difference is what happens next:

Continuous optimization replaces periodic audits

Ploy Web monitors technical SEO, Core Web Vitals, AEO, internal linking, and content freshness automatically. It drafts improvements and recommends updates based on search demand, competitor activity, and visitor behavior. You review. Ploy handles execution.

One platform replaces disconnected tools

Instead of managing separate vendors for websites, analytics, visitor identification, CRM sync, and SEO tools, Ploy brings those capabilities together. Ploy Web, Ploy Grow, and Ploy Ads share context. Insights discovered in one engine create opportunities in another.

Visitor identification turns traffic into pipeline

Visitor de-anonymization identifies companies already researching your business. Ploy enriches them with firmographic data, scores buying intent, and syncs qualified accounts into CRM systems like HubSpot and Attio. You do not wait for form submissions to know who is evaluating your product.

From WordPress migration to AI growth platform

If you’re evaluating WordPress migration, you face two choices:

• Option 1: Migrate WordPress to new hosting. Maintain the same workflow. Manage the same disconnected tools. Run the same periodic optimization projects. Accept the same ongoing burden.
• Option 2: Migrate to Ploy. Start with a site that continuously improves itself. Identify visitors. Optimize for AI answer engines. Connect every insight to pipeline generation. Eliminate the work that slows growth.

If your goal is simply moving WordPress files to a faster server, traditional migration works fine. If your goal is building a growth engine that keeps working after launch, Ploy offers a different path.

For teams exploring this transition, the WordPress alternatives guide covers how Ploy compares to traditional CMS platforms. The website migration page explains the slurp process in detail.

Frequently asked questions

What happens to my SEO rankings during a WordPress migration?

Search performance may fluctuate while search engines re-crawl and re-index the migrated site. The impact depends on how well you preserve URL structure, redirects, metadata, internal links, schema, content, and page performance. Monitor Google Search Console closely after launch and investigate crawl errors, indexing changes, and landing-page traffic against the pre-migration baseline.

How do I handle a large WordPress site (10GB+) that exceeds plugin upload limits?

Large sites may need a host-assisted transfer, a migration tool whose current limits fit the package, a split database-and-files move, or a server-to-server transfer when both environments support it. Choose the method based on package size, permissions, available rollback support, maintenance-window constraints, and the team’s ability to validate the result.

Can I migrate WordPress without any downtime?

A low-downtime migration is possible with careful planning. Build and test the destination before DNS cutover, lower TTL in advance when appropriate, keep a rollback path, and account for caches that may continue sending visitors to either environment for a period. Sites with orders, accounts, or frequently changing data need a synchronization or maintenance-window plan to avoid split writes.

What is the difference between migrating WordPress and rebuilding on a new platform?

A traditional migration aims to transfer the WordPress installation, database, theme, plugins, media, and configuration. A rebuild creates a new implementation using the old site as a reference. Rebuilding can fix structural issues and reduce technical debt, but requires more planning and validation. Ploy’s slurp feature offers a different starting point for marketing pages: it creates an editable first pass from the rendered site, while WordPress databases, plugins, accounts, and other dynamic data remain separate migration workstreams.

How long should I keep my old WordPress server running after migration?

Keep the old server available until the destination has passed traffic, content, media, forms, integrations, scheduled tasks, SSL, redirect, analytics, and rollback checks. The retention window should reflect site complexity and business risk. Sites with ecommerce, accounts, or frequent data changes generally need a more conservative cutover and rollback plan.

What post-migration monitoring should I prioritize in the first month?

Focus on three areas. First, crawl health: monitor Google Search Console for crawl errors, indexing changes, and mobile issues. Second, traffic patterns: compare landing-page and organic traffic against the pre-migration baseline. Third, conversion paths: verify forms, ecommerce checkout, accounts, and lead capture. Set alert thresholds that fit the site’s normal volatility and keep the review cadence higher until performance stabilizes.