Shared server guidance

Migration and cutover planning

Prepare dependencies, transfers, database consistency, DNS changes and safe server retirement.

10 practical answersClear prerequisites and verification

Filter these questions

10 guides

What should I inventory before migrating a server?

Build a server migration inventory covering applications, databases, scheduled jobs, identities, certificates and external network dependencies.

Estimate server migration capacity and timing from live workload, data volume, change rate, transfer performance and final consistency steps.

Preview a scoped Linux server file migration with rsync dry-run, inspect proposed changes and confirm source and destination paths safely.

Plan a consistent server database migration with a supported transfer method, controlled writers, catch-up checks and application validation.

Plan a server DNS cutover with authoritative-zone checks, TTL timing, IPv4 and IPv6 records, rollback values and protection against split writes.

Test a replacement web server with curl resolve overrides while retaining the real hostname, TLS validation and unchanged public DNS records.

Plan HTTPS certificate readiness and renewal during server migration, including validation routes, private-key handling and old endpoint overlap.

Plan a server email migration covering mailboxes, identities, DNS, mail-flow policies, client access and the final synchronisation window.

Define server migration rollback criteria, decision deadlines and data-write boundaries before cutover so recovery decisions are controlled.

Retire an old server only after dependency checks, data reconciliation, recovery acceptance and confirmed service termination arrangements.