Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Migration

WordPress migration validation: test the new host before changing DNS

Published August 2026 · 2 min read · Updated 2026-09-05

WordPress migration validation is the final proof that the destination behaves like the source before and after DNS cutover. Files and a database import are only the transport step; runtime versions, URL handling, mail, cron, cache, certificates, and changing user data determine whether the move is actually safe.

Test the destination before DNS

Use a temporary hostname or hosts-file override to load the real destination while public users still reach the source. Compare important pages, admin login, media, PHP version/extensions, database connectivity, permalinks, plugin features, and error logs.

Fix destination-specific absolute paths or environment configuration before cutover.

Identify data that changes during the migration

Orders, comments, users, form submissions, uploads, memberships, and scheduled jobs can change after the initial database copy. Choose a maintenance window, replication/sync method, or final delta copy appropriate to the site.

Do not rely on DNS TTL to prevent lost writes.

Validate external dependencies

Check SMTP/email, payment sandbox/credentials, APIs, webhooks, cron, DNS records, redirects, SSL, analytics, search verification, and any source-IP allowlists. A new server IP can affect providers even when WordPress itself works.

Keep source logs available during the cutover for comparison.

Monitor after DNS and retain rollback

Verify multiple resolvers, real user paths, new writes, cron, mail, and logs. Keep the source intact until traffic has converged and the new database is unquestionably authoritative.

  • Private-test destination.
  • Plan changing-data sync.
  • Check external integrations.
  • Retain source through convergence.

Next step

Validate a WordPress destination, changing data, mail, cron, certificates and external services before cutover, then keep the source available for rollback.

Explore DotMoose WordPress hosting

Keep reading

Related guides.

Do I need web hosting for WordPress? What WordPress actually needs

Self-hosted WordPress needs web hosting, but it does not require a specially branded WordPress plan. Compare WordPress.com, regular shared hosting, WordPress hosting and VPS options.

Read the guide

How to move web hosting without downtime

Move a website and database with destination testing, final synchronization, controlled DNS cutover, and rollback while preserving separate mail routing.

Read the guide

PHP timeout troubleshooting: PHP, PHP-FPM or the web server?

Find which PHP timeout fired, check the right configuration, and distinguish PHP execution limits, PHP-FPM termination and nginx FastCGI read timeouts.

Read the guide

More wordpress guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move