Preparing a server migration
A migration is a coordinated application and data change. Moving files alone may miss databases, scheduled tasks, certificates, runtime versions or external integrations. Prepare a tested destination before changing production traffic.
Build the migration plan
- Inventory applications, databases, software versions, licences, DNS, mail flow, background jobs and external dependencies.
- Agree data-transfer methods and a final synchronisation window that prevents conflicting writes on two servers.
- Test the destination using an appropriate preview method before changing public DNS or routing.
- Document the cutover owner, validation checklist, rollback criteria and how long the old environment will be retained securely.
Include current resource use, dataset size and acceptable downtime in your request. Where a source server is compromised, recovery should use verified clean software and reviewed data rather than copying the old executable environment wholesale. Migration work and its scope must be agreed.
