POWOKEClient areaInventory 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.
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.
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.
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.