Help for owners
My hosting company is shutting down and I have to move my site
Short answer
Start with a full copy of the files and databases, then list everything tied to the old host: the domain's DNS, email, certificates and scheduled jobs. Lower the DNS cache time before the switch so changes spread sooner, and keep the old account until the new site is confirmed working.
Does this sound like your situation?
- I received an email saying the hosting service is ending on a set date.
- The control panel shows a notice that my plan will be closed.
- I do not know where my domain is registered, or whether it is with the same company.
- Email for my business runs on the same hosting account.
- The person who built the site is not available.
Why does this happen?
Hosting, domain and email are often bundled
One company can supply the hosting, the domain registration and the mailboxes. When the host closes, all three need a new home, not just the website.
Files are only part of the site
A site also has a database, configuration, scheduled jobs, certificates and sometimes software versions the new host does not offer.
DNS caching decides how fast the switch spreads
Resolvers keep a DNS record for as long as its TTL says. Amazon's documentation advises using a short value, such as 300 seconds, first when changing a domain already in use, and raising it after you confirm the new settings are correct.
Confirmed by docs.aws.amazon.com
The deadline leaves little room for mistakes
Rushing the final days is when the database is copied without the latest orders, or DNS is changed before the new site is ready.
What can I do about it today?
- Read the closing notice for the exact dateNote the last day the service runs, and whether data is deleted straight after or kept for a short time.
- Download or request a full copy nowFiles, databases and mailbox contents. Store them somewhere you control, outside the hosting account.
- Find out where the domain is registeredIf the domain is with the same closing company, ask how it can be moved elsewhere. Do not let it lapse.
- List what runs on the accountWebsite, email, subdomains, forms, scheduled jobs, certificates. Everything on the list needs a destination.
- Do not cancel or close the old account yourselfLeave it as the fallback until the new site and email have been checked.
- Choose the new host after you have the listThe list shows what the new host must support.
When should I bring someone in?
- The deadline is close and no complete copy exists yet.
- Business email runs on the same account.
- The site takes orders or payments.
How do I handle it?
- Inventory everything on the old accountSites, databases, mail, DNS, certificates, cron jobs and software versions, written into one checklist.
- Build the new place and test it privatelyI copy the site and data to the new host and test it before any public change.
- Lower the DNS cache time earlyWell before the switch, so the change takes effect quickly.
- Switch at a quiet hour, with a fresh data copyThe final database copy is taken just before the switch, and the old site is kept as a fallback.
- Check email, forms and certificates after the moveEach item on the checklist is ticked off before the old account is closed.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Will the site go down during the move?
It does not have to. The new site is built and tested alongside the old one, and traffic is switched when it is ready. I cannot promise zero interruption because DNS caches belong to third parties.
Do I lose my domain when the host closes?
Not automatically, but check who the registrar is. If it is the closing company, arrange the domain's move before the deadline.
What about my email?
It needs its own plan. See the page on moving a site without losing email.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.