Help for owners
I need to move my app or website to a new server
Short answer
A server move works when everything the app uses is listed first: code, database, files, scheduled tasks, email, certificates and the domain settings. The new server is built and tested alongside the old one, and the switch happens last. Do not cancel the old hosting or change DNS yourself until the new one is proven.
Does this sound like your situation?
- My host is closing, raising its limits or I have outgrown shared hosting.
- The server is old and nobody dares touch it.
- I want my own server but I only know the site works today.
- My developer left and I do not know what is on the server.
- I cannot afford the site to be down while it moves.
Why does this happen?
The app has outgrown where it lives
Shared hosting has limits on memory, processes and scheduled tasks. A growing app hits them, and the symptoms look like random slowness or errors.
The old server is out of date
An old operating system or language version no longer gets fixes, and upgrading it in place risks breaking the app.
Nobody knows everything the server does
Over time a server collects scheduled tasks, email settings, certificates, hidden files and settings that never made it into any document. These are what go missing in a move.
The data keeps changing during the move
If orders keep arriving while the database is copied, the copy is out of date the moment it finishes. A plan is needed for the last changes.
Domain and email are tied to the old server
The website's address points to the old server, and email, certificates and third-party allow-lists often do too. They must be moved with it.
Technical detail: The site looks fine in a browser but its SSL chain is incomplete
What can I do about it today?
- Keep the old server runningDo not cancel the old hosting, delete anything or switch it off. It is your fallback.
- List the accounts and loginsHosting, domain registrar, DNS, email and any paid service. Check each is in your company's name and that you can log in.
- Write down what depends on the sitePayments, emails, apps, partners and reports that connect to it. Anything that uses its address or IP needs attention.
- Pick a quiet time and tell peopleChoose a day with the lowest orders or bookings, and warn staff and key customers.
- Take a full backup before anything startsAsk your host or developer for a copy of the files and database, and keep it somewhere you control.
When should I bring someone in?
- Nobody on your side knows what the server contains.
- The app takes payments or bookings and cannot go offline.
- The old server is failing, or the host has set a closing date.
How do I handle it?
- Inventory the old serverI list the code, database, files, scheduled tasks, email, certificates and settings, so nothing is found missing afterwards.
- Build and test the new server alongsideThe new server is set up with a backup before production changes, and the app is tested there with a copy of the data while the old one keeps serving customers.
- Plan the switchI choose the order of steps, the moment the data is copied for the last time and how to handle changes made in between.
- Switch and keep a way backI change the domain settings, check the main flows and keep the old server untouched until the new one has proven itself, so there is a tested rollback.
- Hand over the documentationYou receive a plain list of what runs where and who holds each login.
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 my site go down during the move?
The new server is built and tested while the old one keeps running, so the visible interruption can be short. I cannot promise zero downtime, because it depends on the app and how the data changes.
Will my search ranking suffer?
A move that keeps addresses and content the same normally does not change what search engines see, but rankings are decided by search engines.
Can I move to a different country or provider?
Yes. I check where your customers are and what your data rules require before choosing.
How was this page made?
I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.