What this means
What this means
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
Before you start
Confirm DNS TTL, current nameservers, business hours, email usage, backup state, and what success looks like after cutover.
Step-by-step guidance
Step-by-step guidance
- 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 CM Cloud support will review
What CM Cloud support will review
Support reviews timing, DNS propagation, customer impact, monitoring checks, rollback steps, and whether old service should remain active temporarily.
What is not automated yet
What is not automated yet
This guide does not perform cutover, mutate DNS, change Cloudflare, transfer registrar control, or deactivate old hosting.
Safety note
Safety note
Reading this article does not capture payment, provision infrastructure, register or transfer domains, change DNS, write Cloudflare or WHMCS, call providers, start workers, create retries, or enable live execution.
Safe next action
Safe next action
Ask support to schedule cutover only after preview, rollback, and verification steps are clear.