How to Move a WordPress Site from a Subdomain to the Main Domain

Moving a WordPress site from a subdomain — dev.example.com or staging.example.com — to the main domain example.com looks like it should be simpler than a full domain migration, since technically you’re often staying on the same hosting account. In practice it has its own sharp edges, mainly because the subdomain and the main domain frequently share the same hosting environment in ways that create conflicts a completely separate migration wouldn’t have.

If example.com already has something live on it — even a simple placeholder page — you’re not migrating into empty space, you’re replacing an existing installation, which means a careless restore can destroy whatever is currently there. And because the subdomain and root domain often live in related folders on the same hosting account, file path conflicts and permission issues come up more often here than in a migration between genuinely separate servers.

Export the subdomain’s database and files exactly as you would for any migration. Before touching the main domain, back up whatever currently exists there too, even if it’s “just” a placeholder — you want a way back if something goes wrong. Import the subdomain’s database into the location the main domain uses, upload the files to the main domain’s root directory, and then do the URL replacement from the subdomain to the root domain, with the same serialized-data caution that applies to any URL change.

If the subdomain was set up as a WordPress installation in a subfolder that happens to sit inside the main domain’s file structure (a common hosting configuration), moving files without checking for this first can leave orphaned duplicate files behind, or in worse cases, an installation that’s technically accessible from two different addresses at once. Worth a clean look at your hosting file structure before starting, not after.

Quick Restore treats a subdomain-to-root-domain move the same way it treats any staging-to-production migration — back up on the subdomain, restore at the root domain address, with the confirmation-before-overwrite step specifically protecting you from accidentally destroying whatever currently lives on the main domain without realizing it. The URL rewrite from subdomain to root domain runs through the same serialization-safe process as any other domain change, so this isn’t a separate, more fragile code path than a standard migration.

Update any DNS or hosting-level redirect that was pointing traffic at the subdomain, decide whether the old subdomain should now 301-redirect to the new root domain URLs (usually yes, if the subdomain had any inbound links or search visibility of its own), and double check internal links within the site itself — menus and hardcoded links built while the site lived on the subdomain sometimes reference that subdomain directly rather than a relative path.