What this means
What this means
Good migration notes reduce delays and prevent support from guessing about DNS, email, databases, or ownership.
Before you start
Before you start
Prepare safe access paths, not passwords in public notes. Confirm who owns the domain, who can approve downtime, and which services must remain online.
Step-by-step guidance
Step-by-step guidance
- Write down the current host, panel type, domain, and service owner.
- List websites, databases, mailboxes, aliases, DNS records, SSL state, and backups.
- Mark what must not change, especially MX records and active production DNS.
- Share screenshots or exported DNS records where useful, without secrets.
- Submit the request and wait for support to confirm the migration path.
What CM Cloud support will review
What CM Cloud support will review
Support reviews completeness, missing access, DNS/email risk, data size, expected downtime, backup state, and rollback expectations.
What is not automated yet
What is not automated yet
Preparing details does not grant access, start transfer, change DNS, or move customer data.
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
Create a migration support request with one domain/service per request when possible.