Traffic switch
Test the destination with the intended hostname, TLS settings, scheduled jobs and email routing. Set a final sync or a short write freeze and record its time. Prevent both environments from sending the same scheduled notifications.
Can writes be reconciled if the cutover is reversed?
Use a labelled test on either side of the cutover and record which environment received it. Two successful confirmation pages do not prove the receiving team sees both records.
Acceptance evidence · New host intake
Check the site from outside the new host and reconcile requests around the cutover. If traffic must return to the old server, first account for writes already accepted by the new one. Keep the old environment available until reconciliation is complete.
Plan the final sync with DigiWeb using the functions that accept new data