When is it safe to decommission the old server after migration?
Decommission the old server after the migration has passed its acceptance period and no required dependency still uses it. The decision includes data, credentials, DNS, licences and billing. A quiet web-access log alone does not establish that the machine is no longer needed.
Before you start
- The migration acceptance record, dependency inventory and approved retention requirements.
Instructions
1. Confirm the replacement is complete
Check application behaviour through normal busy and scheduled-job periods. Reconcile final database and file changes, verify monitoring and recovery arrangements, and review incoming connections to the old host. Account for cached DNS, integrations using fixed IPs and external systems that may connect infrequently.
2. Retire access and dependencies
Move or revoke old service credentials, SSH trust, API registrations and licences using the appropriate process. Remove the old server from deployment and monitoring targets when the replacement is established. Keep required incident and operational records under the approved retention policy.
3. Coordinate final service termination
Confirm the service identifier, authorised end date and provider process for data removal or hardware retirement. Verify required retained data is accessible elsewhere before destructive actions. Request cancellation through the confirmed commercial route and check the returned service and billing state; stopping the machine does not cancel it.
Check the result
- No active dependency or required data relies on the old machine.
- Access, operational inventory and commercial status reflect the approved retirement.
Troubleshooting
- A delayed integration fails after shutdown
- Use the dependency inventory and connection evidence to identify the remaining consumer. Restore only the authorised minimum path if needed, then move that dependency and repeat acceptance checks.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.