Key takeaways
- A WordPress site is files plus a database. Copying one of those is not a move.
- Mail and DNS sit outside that backup. They can fail while the pages still look fine.
- Keep the old hosting plan until the live name shows the copy. The upload finishing is not that moment.
A florist in West Hartford exported a zip of WordPress files on Friday and pointed the name at the new account before lunch. Monday the homepage was a fresh install. The photos were on the new disk. The hours, the wedding packages, and the contact form were still in a database on the old host. The shop phone still rang. The form did not.
That is the usual miss. People treat a move like a file copy. WordPress keeps the pages in a database too.
| Same domain, new host | New domain as well | |
|---|---|---|
| What has to copy | Files and the database | Files and the database, plus every stored URL |
| What WordPress.org says | Home and Site URLs can stay. If the database still works, the files are often enough. | Old URLs stay inside the database. A blunt search-replace can break serialized theme and widget data. |
| DNS | The cutover. Visitors follow the name to the new disk. | Same job, and the name itself is new. |
| Not in the WordPress backup. MX can keep working if mail lives elsewhere. | Still not in the WordPress backup. | |
| When to drop the old plan | After the live name shows the copy, not after the upload finishes. | Same. |
Whether you are moving WordPress to a new server or to a different location on your server, you don’t need to reinstall.
WordPress.org, Migrating WordPress
What WordPress.org says you are moving
The handbook is blunt. Back up the WordPress directory, the images, the plugins, and the database. You are not starting over. You are moving two piles that have to land together.
On Settings, General there are two URL fields: WordPress Address and Site Address. One is where the software lives. The other is the address people type. If you keep the same domain, those fields often stay put. If you change the domain, the old address is still sitting in posts, options, and widgets. WordPress.org warns that a raw search-replace across the whole database can break serialized data, because some themes store the length of the old URL next to the URL itself.
That is why a site can “move” and still load mixed: new theme, old image URLs, a form that posts to a host that no longer answers. The files arrived. The database did not, or it arrived with the old name baked in.
The click-by-click sequence lives in that handbook. We are not reprinting it. If you want a local copy before anyone touches DNS, that is what a WordPress backup is for. If you want a copy you can break without taking the shop offline, that is what a staging site is for.
The domain is not the site
The name and the files are two products. We already covered that in a domain name is not a website. A move does not change the split. Pointing the name is the last cut, not the first copy.
If the files and database are on the new host and the name still points at the old one, customers keep seeing last week’s site. If the name moves first and the database is missing, they see a blank install, a parking page, or an error. Either way the florist looks closed online while the cooler is full.
Keep the registrar login in an account the business controls. A designer can hold the WordPress admin. They should not be the only person who can move the name.
Mail is a different product
A WordPress backup does not include the mailbox. Estimates, invoices, and “is the cake ready” threads live on MX records, or on Google Workspace, or on Microsoft 365. None of that is a row in the WordPress database.
An auto shop in Bristol copied the site, then changed nameservers as if mail lived in the same box as the homepage. The pages came up. The estimates bounced. The shop found out from a customer, not from a green checkmark on the hosting screen.
If mail already lives outside hosting, leave it there
If the shop already reads mail in Google or Microsoft, the MX records usually should not follow a hosting nameserver change. The website can move. The inbox can stay. Mixing those two on purpose is a second project, with its own cutover. Do not treat it as a free extra of the WordPress copy.
Same name versus a new name
Keeping shopname.com and changing hosts is the smaller job. WordPress.org says that if the Home and Site URLs stay the same, you are mostly moving files and a database. The hard part is still the list above: both piles, mail, and not canceling the old plan early.
Changing the name at the same time is a different job. Every stored URL has to be updated without breaking serialized data. Redirects have to exist for the old address. Search Console, Google Business Profile, and printed vans still point at last year’s string until you change them. That is not a hosting failure. It is two moves booked on one Friday.
If the current site is a rented builder login, there may be no files to copy. We covered that in you do not own that website. WordPress on a host you pick can leave. A builder that will not export the design cannot.
What should already be true before anyone points the name
You can log into the old host, the registrar, and WordPress today, not last year. You have a copy of the files and the database that is not only on the old server. You know whether mail lives with the website or somewhere else. You have a way to look at the copy before the public does, even if that is a staging site rather than a guess after DNS.
SSL has to exist on the new host before the name arrives. Browsers will not be polite about a missing certificate. Forms, checkout, and admin logins are where that shows up first. The homepage can look fine while a booking page throws a warning.
Then leave the old plan running. DNS caches. Some phones still hit the old disk on Tuesday. Canceling Friday night to “save a week” is how the only remaining copy disappears while you are still comparing the two sites.
What we host, and what we will not pretend
On WordPress hosting the WordPress Basic plan starts at $2.99 a month and renews at $7.99. You get 10 GB, one WordPress site, two mailboxes, SSL, staging, and backups on the plan. That is us, on shared US infrastructure, with tickets and email answered by a person in Connecticut. We do not watch the site at 3:00 AM.
A move can land here. It still needs both piles, a decision about mail, and the old account left on until the live name matches. Do not pick a host because the first month is cheap. We already wrote that in compare hosting on the renewal price. Pick one where the files can leave later, because this will not be the last time the shop moves.
If the name is already yours and you need a host the files can leave, start on WordPress hosting or open the client area.
