1. Make an inventory
List domains, websites, databases, mailboxes, scheduled jobs and external integrations. Record the software versions, data sizes and services that depend on fixed IP addresses or DNS records.
2. Agree scope and access
Tell the NETUV team what needs to move and identify who controls your current hosting, domain and DNS. Share credentials only through an agreed secure channel. Confirm which tasks are included and which require separate work.
3. Protect the source
Take appropriate backups before the migration and verify that they can be read. Keep a copy of the current DNS configuration and document a rollback approach. Avoid cancelling the existing service before the new one is validated.
4. Test the new environment
Check key pages, forms, authentication, database operations and scheduled tasks. For email, test mailbox access, sending, receiving and the intended domain authentication records. Confirm the application works before sending production traffic to it.
5. Schedule the cutover
Choose a suitable change window and tell the people affected. Coordinate final data synchronisation and DNS changes. Cached DNS records may continue to send some users to the old service during the transition.
6. Verify, monitor and close
Check the new environment after the switch, monitor errors and confirm that new data reaches the right system. Retain the old service and backups for an agreed period before decommissioning.