Temporary Domain Website Migration Guide
A temporary domain lets you restore and test a site before the production DNS change. This is useful when the final domain still points to the old server, when a CDN is origin-locked, or when the destination is a fresh WordPress install that is not publicly live yet.
When to use a temporary domain
- The client cannot point DNS until the new site is verified.
- The destination host gives you a preview URL or server hostname.
- You need to test PHP, database, plugins, uploads, checkout, or forms first.
- Cloudflare, Sucuri, or another proxy needs a controlled cutover window.
WordPress temporary-domain flow
Run the migration to the temporary destination URL first. After files and tables restore cleanly, use serialized-safe WordPress replacement from the old domain to the temporary domain for staging tests. At launch, run the final replacement from temporary domain to production domain, clear caches, and verify redirects.
What to verify before DNS cutover
Check wp-admin login, homepage, inner pages, media, forms, checkout, search, cron behavior, permalink settings, SSL certificate readiness, and CDN bypass rules. Keep the old server untouched until post-cutover checks pass.