POWOKEClient area

POWOKE / Deployment handbook

How to Make Website Server Migration Reversible: Zero-Downtime Cutover Guide

Changing DNS is only one step of a server migration. Follow this reversible website cutover playbook covering dependency inventory, staging validation, TTL reduction, preventing split-brain database writes, HTTPS checks, and rollback paths.

01

Inventory state and dependencies

Record runtime versions, extensions, scheduled jobs, databases, uploads and external callbacks. Confirm licenses and connectivity in the destination environment. Verify a complete backup and retain the old configuration.

02

Rehearse before moving traffic

Copy data and validate through a test hostname or a local hosts override. Check certificates, administration, uploads, email and callbacks. Prevent both environments from running the same queues or scheduled jobs.

03

Plan the handover of writes

Adjust DNS TTL ahead of time without assuming all clients will refresh immediately. Define the order for pausing writes, final synchronization and resuming writes. Database dual writing needs a designed consistency strategy.

04

Use explicit rollback criteria

Observe errors, response times and transaction consistency after cutover. Retain the old environment during the observation period. If the new system has accepted writes, reconcile that data before rollback; changing DNS back alone can lose business records.

Deployment handbook