Change the foundation.
Keep the continuity.

Know what is connected.

Record domain ownership, current registrar, nameservers and all DNS records. Inventory the website, databases, scheduled jobs, mailboxes, aliases and external senders. Identify who can approve changes and who will verify the result.

Make the destination ready.

Confirm the provider’s current service scope and resource needs. Back up website files, databases and mail where applicable, then check that the backup can be used. Test the application at the destination before directing customers to it.

Change a controlled part of the path.

Agree the change window and rollback conditions. Review DNS TTLs in advance, while allowing for caches that may retain older information. Preserve required mail and verification records when changing web hosting or nameservers.

For email, confirm MX, authorised sending routes, DKIM keys and DMARC alignment. Test incoming and outgoing mail with the affected applications and people, then review delivery evidence.

Check the real user journey.

Test secure website access, forms, database functions and expected redirects. Check mail send and receive, device configuration, certificate renewal and scheduled tasks. Keep the old service available for the agreed transition period until acceptance and recovery arrangements are clear.

Bring a non-sensitive outline first.

Describe what is moving, the desired outcome and the people responsible. Detailed exports and credentials belong only in an agreed secure handover.