KNOWLEDGE / GUIDE
Plan a website move
Inventory dependencies, test the destination and keep a fallback before changing DNS.
Map what must move
List websites, databases, uploads, domains, DNS records, mailboxes, scheduled jobs and external integrations. Record who controls each account and whether the destination supports the application’s runtime and database requirements.
Agree the scope and protect the source
Ask support to confirm whether assistance is available, what it covers and any applicable charges. Create a current, recoverable backup and retain access to the old service. Agree how changes made during the move will be handled.
Test before switching traffic
Use a suitable preview method to check pages, forms, uploads, sign-in, application configuration and integrations at the destination. Handle personal data carefully and remove temporary test access afterward.
Switch deliberately and verify
Only make the agreed DNS changes when the destination is ready. Check the website and, where relevant, incoming and outgoing email after the change. Keep the old environment and a verified backup until you are satisfied the move is complete; the necessary overlap depends on your situation.
Further reading
These external guides describe the underlying tools. Available features and procedures can differ by provider.
For help with your own service, contact HostingLawn support.
