What this covers
Cutover is the moment users start reaching the new hosting, WordPress, email, VPS, or app target. It must be planned, verified, and reversible where possible.
Before you start
Confirm DNS TTL, current nameservers, business hours, email usage, backup state, and what success looks like after cutover.
How to do it
- Freeze risky content changes before the cutover window.
- Take or confirm a backup and snapshot where applicable.
- Apply the reviewed DNS or routing change only after approval.
- Verify homepage, login, forms, email, SSL, and service health.
- Keep rollback instructions ready until the site has been stable.
What our team checks
Support reviews timing, DNS propagation, customer impact, monitoring checks, rollback steps, and whether old service should remain active temporarily.
Next step
Ask support to schedule cutover only after preview, rollback, and verification steps are clear.