What is included in the move?
Separate website hosting, domain registration, DNS management, mailboxes and external storage. They may be operated by different providers and need different decisions.
Before a website move
Know what can change while the site is moving.
These questions help turn “move the website” into a plan that accounts for the work still arriving.
What does the site receive?
List orders, inquiries, account changes, uploads and background updates. Explain when a write pause would be practical and what would happen to visitors during it.
How will the destination be tested?
Ask for a protected rehearsal and representative customer tasks. Include the saved form or order, permissions and scheduled work. Avoid tests that contact real customers or charge real payments unintentionally.
What happens if the move must stop?
A restored old copy can be incomplete once new records exist at the destination. Ask how those records would be reconciled, who approves recovery and what downtime is expected.
Which addresses must stay useful?
Keep important old page addresses if possible. Where they change, prepare a destination map and check links, canonical addresses and sitemaps after release.
When can the old host be closed?
Only after the agreed acceptance and retention checks. The new application also needs working backups and a named operator. Do not let an approaching renewal replace that decision.
You can start without a complete server inventory.
Send the site address, known providers and the reason for the move. Prepare the initial inquiry.